From: Rupesh Gujare <rgujare@ozmodevices.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: <devel@driverdev.osuosl.org>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix bug where kfree is called twice.
Date: Thu, 26 Apr 2012 18:09:15 +0100 [thread overview]
Message-ID: <4F99813B.1010806@ozmodevices.com> (raw)
In-Reply-To: <20120426115459.GE6447@mwanda>
Hi Greg,
> Everything goes into linux-next first. That should have been put in
> the changelog. "We are seeing occasional crashes under load" or
> whatever... It's Greg's call and all, but generally it can't hurt to
> ask nicely if you want stuff merged it into 3.4 as well. ;)
Is it possible to queue it up for 3.4 as well ?
--
Regards,
Rupesh Gujare
next prev parent reply other threads:[~2012-04-26 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 22:54 [PATCH] Fix bug where kfree is called twice Rupesh Gujare
2012-04-26 6:38 ` Dan Carpenter
2012-04-26 8:44 ` Rupesh Gujare
2012-04-26 11:54 ` Dan Carpenter
2012-04-26 17:09 ` Rupesh Gujare [this message]
2012-04-26 19:48 ` Greg KH
2012-04-26 20:42 ` Rupesh Gujare
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=4F99813B.1010806@ozmodevices.com \
--to=rgujare@ozmodevices.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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