Re: [PATCH 1/2] SUNRPC: gss_alloc_msg - choose _either_ a v0 message or a v1 message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 28, 2013 at 10:59:45PM +0000, Myklebust, Trond wrote:
> > -----Original Message-----
> > From: Myklebust, Trond
> > Sent: Monday, October 28, 2013 6:57 PM
> > To: linux-nfs@xxxxxxxxxxxxxxx; Bruce Fields
> > Cc: stable@xxxxxxxxxxxxxxx
> > Subject: [PATCH 1/2] SUNRPC: gss_alloc_msg - choose _either_ a v0 message
> > or a v1 message
> > 
> > Add the missing 'break' to ensure that we don't corrupt a legacy 'v0' type
> > message by appending the 'v1'.
> > 
> > Cc: Bruce Fields <bfields@xxxxxxxxxxxx>
> > Cc: stable@xxxxxxxxxxxxxxx
> > Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
> > ---
> 
> I did not intend to send this to stable@vger.kernel .org before it has hit upstream...

Don't worry, as you were just cc: stable@ with your normal patch
submission process, I can tell that this isn't to be applied now, it's
part of the development process.  So don't feel bad at all, lots of
other subsystems do it, and it doesn't bother me at all, no need to
filter it away.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]