On Fri, Feb 04, 2011 at 12:20:59PM +0530, Desai, Kashyap wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:greg@xxxxxxxxx] > > Sent: Thursday, February 03, 2011 10:50 PM > > To: Desai, Kashyap > > Cc: linux-scsi@xxxxxxxxxxxxxxx; James.Bottomley@xxxxxxxxxxxxxxxxxxxxx; > > Prakash, Sathya; Moore, Eric; stable@xxxxxxxxxx > > Subject: Re: [stable] [PATCH 04/06] mptfusion: mptctl_release is > > required in mptctl.c > > > > On Thu, Feb 03, 2011 at 03:33:00PM +0530, Kashyap, Desai wrote: > > > > > > Added missing release callback for file_operations mptctl_fops. > > > Without release callback there will be never freed. It remains on > > > mptctl's eent list even after the file is closed and released. > > > > > > Relavent RHEL bugzilla is 660871 > > > > > > Signed-off-by: Kashyap Desai <kashyap.desai@xxxxxxx> > > > --- > > > > <snip> > > > > This is NOT the way to get patches into a stable kernel release. > > Please > > read the file, Documentation/stable_kernel_rules.txt for how to do it > > properly. > > > Greg, Thanks for the redirecting to correct process. I understood that > I have to add "CC: stable@xxxxxxxxxx " in header of the patch itself > instead of CCing stable@xxxxxxxxxx from email client. > Do I need to resend those patches? To get these into a stable release? I don't know, that's up to the subsystem maintainer if he is going to be willing to edit the patch and add that line himself. I'd defer and resend it to make sure it gets there. good luck, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
