From: Andrew Morton <akpm@linux-foundation.org>
To: "Steve French" <smfrench@gmail.com>
Cc: jlayton@redhat.com, marcin.slusarz@gmail.com,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Fwd: [patch (for 2.6.26?) 1/1] cifs: fix oops on mount when CONFIG_CIFS_DFS_UPCALL is enabled
Date: Tue, 10 Jun 2008 14:10:58 -0700 [thread overview]
Message-ID: <20080610141058.cacc4fa8.akpm@linux-foundation.org> (raw)
In-Reply-To: <524f69650806101014r6a068a7dvacb7fba58a230a63@mail.gmail.com>
On Tue, 10 Jun 2008 12:14:26 -0500
"Steve French" <smfrench@gmail.com> wrote:
> From: "Steve French" <smfrench@gmail.com>
argh. smfrench@gmail.com == sfrench@us.ibm.com == sfrench@samba.org.
This always bugs me because I never know which is preferred, most
reliable, least likely to get mangled, etc.
> To: "Jeff Layton" <jlayton@redhat.com>, marcin.slusarz@gmail.com, "Andrew Morton" <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org>
> Subject: Fwd: [patch (for 2.6.26?) 1/1] cifs: fix oops on mount when CONFIG_CIFS_DFS_UPCALL is enabled
> Date: Tue, 10 Jun 2008 12:14:26 -0500
>
> I don't have the original note (ie patch without whitespace mangled by
> the mailers) that I can ack to Linus on this but would like it merged
> into mainline as an individual patch (my cifs-2.6.git tree has
> additional patches in it that I don't want to merged into
> linux-2.6.git yet).
>
I'll send this on to Linus and stable@kernel.org in my next batch.
> ---------- Forwarded message ----------
> From: Steve French <smfrench@gmail.com>
> Date: Tue, Jun 10, 2008 at 11:47 AM
> Subject: Re: [patch (for 2.6.26?) 1/1] cifs: fix oops on mount when
> CONFIG_CIFS_DFS_UPCALL is enabled
> To: akpm@linux-foundation.org
> Cc: sfrench@us.ibm.com, marcin.slusarz@gmail.com, sfrench@samba.org,
> stable@kernel.org
>
> ACK
Please don't top-post. It really does make it hard to keep things
vaguely coherent?
prev parent reply other threads:[~2008-06-10 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806092348.m59NmsZd015641@imap1.linux-foundation.org>
[not found] ` <524f69650806100947g4392b44es12b800e39a406d75@mail.gmail.com>
2008-06-10 17:14 ` Fwd: [patch (for 2.6.26?) 1/1] cifs: fix oops on mount when CONFIG_CIFS_DFS_UPCALL is enabled Steve French
2008-06-10 21:10 ` Andrew Morton [this message]
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=20080610141058.cacc4fa8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=smfrench@gmail.com \
--cc=stable@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