From: Dan Carpenter <dan.carpenter@oracle.com>
To: Rupesh Gujare <rgujare@ozmodevices.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix bug where kfree is called twice.
Date: Thu, 26 Apr 2012 09:38:58 +0300 [thread overview]
Message-ID: <20120426063858.GC6447@mwanda> (raw)
In-Reply-To: <1335394498-5046-1-git-send-email-rgujare@ozmodevices.com>
It's a good patch and it fixes a bug, but could you resend with
the subject:
[PATCH] Staging: ozwpan: Fix bug where kfree is called twice.
We don't like to put a lot of bureaucracy infront of people
submitting actual bugfixes. But you guys are the new maintainers
and you're going to need to know all this stuff eventually. Also
could you give us a hint how likely the users are to hit this?
Should this go into 3.4 or only 3.5?
regards,
dan carpenter
next prev parent reply other threads:[~2012-04-26 6:36 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 [this message]
2012-04-26 8:44 ` Rupesh Gujare
2012-04-26 11:54 ` Dan Carpenter
2012-04-26 17:09 ` Rupesh Gujare
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=20120426063858.GC6447@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgujare@ozmodevices.com \
/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