Bart Van Assche <Bart.VanAssche@xxxxxxx> 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@xxxxxxxxxxxxxxxx> > Date: Wed Aug 16 15:26:43 2017 +1000 > $ git show next-20170817 | head -3 > tag next-20170817 > Tagger: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> > 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
