From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Updates pushed out
Date: Tue, 06 Jan 2009 09:25:42 -0500 [thread overview]
Message-ID: <1231251942.4290.153.camel@think.oraclecorp.com> (raw)
Hello everyone,
I'm pushing out fixes for most of the issues brought up in code review
for merging into mainline. Soon the unstable trees will be updated to
2.6.28
One of the commits is quite large, fixing almost all of the
checkpatch.pl warnings and errors. Most of them were one of these 3:
while(x) -> while (x)
printk() -> printk(KERN_FOO)
printk(... %Lu, some_u64) -> printk(... %llu, (unsigned long
long)some_u64)
There were other bits and pieces, but please run your patches through
checkpatch.pl before you send them from now on.
-chris
reply other threads:[~2009-01-06 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1231251942.4290.153.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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