From: Steve French <smfrench@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Fwd: VFS: trivial: fix comment on s_maxbytes value warning check
Date: Sun, 3 Apr 2011 14:40:45 -0500 [thread overview]
Message-ID: <BANLkTik+5ppWXD5kmrdayxVZ3GTECt048g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikvs4-uie3MF0HrEpd6hYU0FxgK3w@mail.gmail.com>
Forgot to cc the list
---------- Forwarded message ----------
From: Steve French <smfrench@gmail.com>
Date: Sun, Apr 3, 2011 at 2:40 PM
Subject: RE: VFS: trivial: fix comment on s_maxbytes value warning check
To: Jeff Layton <jlayton@redhat.com>
Jeff
I don't see your patch to fs/super.c "VFS: trivial: fix comment on
s_maxbytes value warning check" in mainline yet but it is in your tree
and looks fine.
http://git.kernel.org/?p=linux/kernel/git/jlayton/linux.git;a=commitdiff;h=3652e266b9af0ef79172b61b8f5fc55e4a8ae531
I put that in my cifs-2.6.git tree - do you want me to keep it there
or do you prefer that that go in independently of the cifs merge?
--
Thanks,
Steve
--
Thanks,
Steve
next parent reply other threads:[~2011-04-03 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikvs4-uie3MF0HrEpd6hYU0FxgK3w@mail.gmail.com>
2011-04-03 19:40 ` Steve French [this message]
2011-04-08 12:52 ` VFS: trivial: fix comment on s_maxbytes value warning check Jeff Layton
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=BANLkTik+5ppWXD5kmrdayxVZ3GTECt048g@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).