From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 update for 2.6.36
Date: Fri, 13 Aug 2010 17:09:42 -0400 [thread overview]
Message-ID: <E1Ok1VW-0003Hx-QA@tytso-glaptop> (raw)
Hi Linus,
No other late-breaking bug reports/regressions have turned up, and since
I want to get this fixed before -rc1 gets released, please pull:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
I fixed the compile warning basically as you suggested, but with a
better name and with the comments moved to the inline function where
they would make more sense.
Thanks,
- Ted
Theodore Ts'o (1):
ext4: clean up compiler warning in start_this_handle()
fs/jbd2/transaction.c | 46 +++++++++++++++++++++++++++-------------------
1 files changed, 27 insertions(+), 19 deletions(-)
next reply other threads:[~2010-08-13 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 21:09 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-06 4:23 [GIT PULL] ext4 update for 2.6.36 Theodore Ts'o
2010-08-07 20:17 ` Linus Torvalds
2010-08-09 21:48 ` Ted Ts'o
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=E1Ok1VW-0003Hx-QA@tytso-glaptop \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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