[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20080610141058.cacc4fa8.akpm@linux-foundation.org>
Date: Tue, 10 Jun 2008 14:10:58 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Steve French" <smfrench@...il.com>
Cc: jlayton@...hat.com, marcin.slusarz@...il.com,
linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: Fwd: [patch (for 2.6.26?) 1/1] cifs: fix oops on mount when
CONFIG_CIFS_DFS_UPCALL is enabled
On Tue, 10 Jun 2008 12:14:26 -0500
"Steve French" <smfrench@...il.com> wrote:
> From: "Steve French" <smfrench@...il.com>
argh. smfrench@...il.com == sfrench@...ibm.com == sfrench@...ba.org.
This always bugs me because I never know which is preferred, most
reliable, least likely to get mangled, etc.
> To: "Jeff Layton" <jlayton@...hat.com>, marcin.slusarz@...il.com, "Andrew Morton" <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.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@...nel.org in my next batch.
> ---------- Forwarded message ----------
> From: Steve French <smfrench@...il.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@...ux-foundation.org
> Cc: sfrench@...ibm.com, marcin.slusarz@...il.com, sfrench@...ba.org,
> stable@...nel.org
>
> ACK
Please don't top-post. It really does make it hard to keep things
vaguely coherent?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists