From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] Coding Style changes
Date: Sun, 4 Oct 2015 09:21:20 +0100 [thread overview]
Message-ID: <5610E180.7060001@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Hello All,
Unless anyone has any objection/has already done the work etc I'm going
to make a start on getting sch_cake.c passing linux 'checkpatch'.
Hopefully will get some time today between shows I'm mixing and will
continue 'fiddling' (as my wife calls it) during the week 'till done.
I'll start on spacing issues, then deal with the resulting long lines
and so on.
Kevin
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next reply other threads:[~2015-10-04 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 8:21 Kevin Darbyshire-Bryant [this message]
2015-10-04 18:36 ` Stephen Hemminger
2015-10-04 19:42 ` Dave Taht
2015-10-04 20:00 ` Kevin Darbyshire-Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5610E180.7060001@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox