From: Tejun Heo <tj@kernel.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Dan Carpenter <error27@gmail.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] libsas: dereferencing variable before check
Date: Thu, 13 May 2010 16:37:50 +0200 [thread overview]
Message-ID: <4BEC0EBE.7000404@kernel.org> (raw)
In-Reply-To: <1273761114.4353.122.camel@mulgrave.site>
Hello,
On 05/13/2010 04:31 PM, James Bottomley wrote:
>> Ooh.. right.
>>
>> Asked-by: Tejun Heo <tj@kernel.org>
That was my first mail from android and of course I typed Asked
instead of Acked. :-)
> Well, oops, yes. Two patches to fix one bug is a bit overboard, I
> think, plus some code rearrangement to fix the locality of the problem
> and ensure it doesn't happen again might be useful. What about this.
Yeap, as long as the silly bug is fixed.
Thank you.
--
tejun
next prev parent reply other threads:[~2010-05-13 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 22:56 [patch] libsas: dereferencing variable before check Dan Carpenter
2010-05-12 23:08 ` Tejun Heo
2010-05-13 14:31 ` James Bottomley
2010-05-13 14:37 ` Tejun Heo [this message]
2010-05-13 18:42 ` Dan Carpenter
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=4BEC0EBE.7000404@kernel.org \
--to=tj@kernel.org \
--cc=James.Bottomley@suse.de \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).