From: Huang Rui <ray.huang@amd.com>
To: Ken Xue <Ken.Xue@amd.com>, Alan Stern <stern@rowland.harvard.edu>
Cc: "Huang, Shane" <Shane.Huang@amd.com>,
"Yu, Xiangliang" <Xiangliang.Yu@amd.com>,
"aaron.lu@intel.com" <aaron.lu@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"JBottomley@Odin.com" <JBottomley@Odin.com>,
SPG_Linux_Kernel <SPG_Linux_Kernel@amd.com>
Subject: Re: [PATCH]SCSI:Refine the way to fix NULL pointer dereference in runtime PM
Date: Wed, 9 Sep 2015 17:33:45 +0800 [thread overview]
Message-ID: <20150909093344.GA9459@hr-slim.amd.com> (raw)
In-Reply-To: <1441788007.5845.77.camel@kxue-X58A-UD3R>
On Wed, Sep 09, 2015 at 04:40:07PM +0800, Ken Xue wrote:
> On Wed, 2015-09-09 at 16:30 +0800, Huang Rui wrote:
> > On Wed, Sep 09, 2015 at 03:02:11PM +0800, Ken Xue wrote:
> > > From 844ebfcecad7ddaf7206e0474c600b0146b4ef21 Mon Sep 17 00:00:00 2001
> > > From: Ken Xue <Ken.Xue@amd.com>
> > > Date: Wed, 9 Sep 2015 14:55:21 +0800
> > > Subject: [PATCH] SCSI:Refine the way to fix NULL pointer dereference in
> > > runtime PM
> > >
> > > There was a patch about Bugzilla #101371.
> >
> > Which Bugzilla? I guess you should put a link or oops message of NULL
> > pointer dereference here. Then other guys can know detail infomation
> > of this fix.
> >
> You can find out previous patch with commit ID 49718f.
> You also can find log with below link
> https://bugzilla.kernel.org/show_bug.cgi?id=101371
>
I see. So maybe we would better mark the commit ID. :)
Alan, could you please take a look?
Thanks,
Rui
next prev parent reply other threads:[~2015-09-09 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 7:02 [PATCH]SCSI:Refine the way to fix NULL pointer dereference in runtime PM Ken Xue
2015-09-09 8:30 ` Huang Rui
2015-09-09 8:40 ` Ken Xue
2015-09-09 9:33 ` Huang Rui [this message]
2015-09-09 15:41 ` Alan Stern
2015-09-10 2:23 ` [PATCH 1/2]Revert "SCSI: Fix NULL pointer dereference in runtime PM" Ken Xue
2015-11-27 3:01 ` Xue, Ken
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=20150909093344.GA9459@hr-slim.amd.com \
--to=ray.huang@amd.com \
--cc=JBottomley@Odin.com \
--cc=Ken.Xue@amd.com \
--cc=SPG_Linux_Kernel@amd.com \
--cc=Shane.Huang@amd.com \
--cc=Xiangliang.Yu@amd.com \
--cc=aaron.lu@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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