From: Dan Carpenter <error27@gmail.com>
To: "Bounine, Alexandre" <Alexandre.Bounine@idt.com>
Cc: Matt Porter <mporter@kernel.crashing.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] rapidio: potential null deref on failure path
Date: Mon, 21 Mar 2011 18:52:21 +0300 [thread overview]
Message-ID: <20110321153609.GR2008@bicker> (raw)
In-Reply-To: <0CE8B6BE3C4AD74AB97D9D29BD24E55201A5897F@CORPEXCH1.na.ads.idt.com>
On Mon, Mar 21, 2011 at 08:15:33AM -0700, Bounine, Alexandre wrote:
> In this case I agree.
> Do you want me to move this patch up or you have your own path for it?
>
Could you take it, please?
regards,
dan carpenter
next prev parent reply other threads:[~2011-03-21 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 4:40 [patch] rapidio: potential null deref on failure path Dan Carpenter
2011-03-21 12:49 ` Bounine, Alexandre
2011-03-21 14:59 ` Dan Carpenter
2011-03-21 15:15 ` Bounine, Alexandre
2011-03-21 15:52 ` Dan Carpenter [this message]
2011-03-21 16:05 ` Bounine, Alexandre
2011-03-21 18:34 ` Bounine, Alexandre
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=20110321153609.GR2008@bicker \
--to=error27@gmail.com \
--cc=Alexandre.Bounine@idt.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).