From: "Steve French" <smfrench@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: remove some of cifs hard to read ifdefs
Date: Tue, 12 Feb 2008 15:25:49 -0600 [thread overview]
Message-ID: <524f69650802121325k1d9e88c4ndcf41962923dd337@mail.gmail.com> (raw)
On Feb 7, 2008 12:25 PM, Christoph Hellwig <hch@infradead.org> wrote:
> and while I'm at it a lot of the non-DFS additions to cifs aren't quite
> up to standards for kernel code either, lots of useless braces, wierd
> coding style and ifdef mania.
The useless braces should be removed now. The "ifdef mania" should be
cut by about a quarter by the following patch (following up on the
patch idea posted late last week):
http://git.kernel.org/?p=linux/kernel/git/sfrench/cifs-2.6.git;a=commitdiff;h=90c81e0b0eda214196cbe4340facbce8cc797ee7
--
Thanks,
Steve
next reply other threads:[~2008-02-12 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 21:25 Steve French [this message]
2008-02-13 7:05 ` remove some of cifs hard to read ifdefs Christoph Hellwig
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524f69650802121325k1d9e88c4ndcf41962923dd337@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).