From: Michael Ellerman <mpe@ellerman.id.au>
To: Bart Van Assche <Bart.VanAssche@wdc.com>,
"martin.petersen\@oracle.com" <martin.petersen@oracle.com>
Cc: "jthumshirn\@suse.de" <jthumshirn@suse.de>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"hch\@lst.de" <hch@lst.de>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"brking\@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"abdhalee\@linux.vnet.ibm.com" <abdhalee@linux.vnet.ibm.com>,
"hare\@suse.com" <hare@suse.com>,
"jejb\@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>
Subject: Re: [PATCH] Revert "scsi-mq: Always unprepare before requeuing a request"
Date: Fri, 18 Aug 2017 22:06:32 +1000 [thread overview]
Message-ID: <87wp61ozav.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1502983764.2615.3.camel@wdc.com>
Bart Van Assche <Bart.VanAssche@wdc.com> writes:
> On Wed, 2017-08-16 at 22:51 -0400, Martin K. Petersen wrote:
>> > When I checked earlier today the ipr patch was not yet in linux-next
>>
>> That's weird. They were both committed two weeks ago.
>>
>> They appear to be in there now, though:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/scsi?ofs=50
>
> Hello Martin,
>
> As far as I can see commit 270065e92c31 ("scsi-mq: Always unprepare before
> requeuing a request") was yesterday in linux-next but not the ipr fix
> (commit b0e17a9b0df2 ("scsi: ipr: Fix scsi-mq lockdep issue")). The
> ipr fix is in today's linux-next but was not in linux-next yesterday (the
> Australian time zone applies to the linux-next date labels):
> $ git tag --contains 270065e92c31
> next-20170816
> $ git tag --contains b0e17a9b0df2
> next-20170817
> $ git show next-20170816 | head -3
> tag next-20170816
> Tagger: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed Aug 16 15:26:43 2017 +1000
> $ git show next-20170817 | head -3
> tag next-20170817
> Tagger: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu Aug 17 16:34:30 2017 +1000
>
> I think this means that the ipr fix went upstream before it ended up in
> linux-next.
It was in linux-next, but as a different commit. I don't know why.
$ git log -1 --format=oneline next-20170816 drivers/scsi/ipr.c
48b580cacfae123471f8cd43ca81b0e53c9cf702 scsi: ipr: Fix scsi-mq lockdep issue
$ git tag --contains 48b580cacfae123471f8cd43ca81b0e53c9cf702
next-20170809
next-20170810
next-20170811
next-20170815
next-20170816
cheers
next prev parent reply other threads:[~2017-08-18 12:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:43 [PATCH] Revert "scsi-mq: Always unprepare before requeuing a request" Bart Van Assche
2017-08-17 0:11 ` Martin K. Petersen
2017-08-17 0:41 ` Damien Le Moal
2017-08-17 0:45 ` Damien Le Moal
2017-08-17 0:52 ` Martin K. Petersen
2017-08-17 1:29 ` Bart Van Assche
2017-08-17 2:00 ` Martin K. Petersen
2017-08-17 2:41 ` Bart Van Assche
2017-08-17 2:51 ` Martin K. Petersen
2017-08-17 15:29 ` Bart Van Assche
2017-08-17 16:45 ` Martin K. Petersen
2017-08-17 17:40 ` Brian King
2017-08-17 17:48 ` Martin K. Petersen
2017-08-18 12:06 ` Michael Ellerman [this message]
2017-08-17 0:46 ` 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=87wp61ozav.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Bart.VanAssche@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox