From: Greg KH <gregkh@linuxfoundation.org>
To: Long Li <longli@exchange.microsoft.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Haiyang Zhang <haiyangz@microsoft.com>,
"James E . J . Bottomley" <JBottomley@odin.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
devel@linuxdriverproject.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] scsi: storvsc: missing error code in storvsc_probe()
Date: Fri, 9 Feb 2018 09:01:18 +0100 [thread overview]
Message-ID: <20180209080118.GA19045@kroah.com> (raw)
In-Reply-To: <20180208235040.5803-1-longli@exchange.microsoft.com>
On Thu, Feb 08, 2018 at 04:50:40PM -0700, Long Li wrote:
> From: Long Li <longli@microsoft.com>
No, Dan wrote the first patch here, don't change the authorship of a
patch :(
Now fixed up by hand...
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Long Li <longli@exchange.microsoft.com>
Cc: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"James E . J . Bottomley" <JBottomley@odin.com>,
devel@linuxdriverproject.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] scsi: storvsc: missing error code in storvsc_probe()
Date: Fri, 9 Feb 2018 09:01:18 +0100 [thread overview]
Message-ID: <20180209080118.GA19045@kroah.com> (raw)
In-Reply-To: <20180208235040.5803-1-longli@exchange.microsoft.com>
On Thu, Feb 08, 2018 at 04:50:40PM -0700, Long Li wrote:
> From: Long Li <longli@microsoft.com>
No, Dan wrote the first patch here, don't change the authorship of a
patch :(
Now fixed up by hand...
next prev parent reply other threads:[~2018-02-09 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 23:50 [PATCH] scsi: storvsc: missing error code in storvsc_probe() Long Li
2018-02-08 23:50 ` Long Li
2018-02-09 8:01 ` Greg KH [this message]
2018-02-09 8:01 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 10:40 Dan Carpenter
2018-01-16 10:40 ` Dan Carpenter
2018-01-16 14:36 ` Cathy Avery
2018-01-16 14:36 ` Cathy Avery
2018-01-16 15:10 ` KY Srinivasan
2018-01-17 6:18 ` Martin K. Petersen
2018-01-17 6:18 ` Martin K. Petersen
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=20180209080118.GA19045@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=JBottomley@odin.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@exchange.microsoft.com \
--cc=martin.petersen@oracle.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.