[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1519356093.4819.28.camel@HansenPartnership.com>
Date: Thu, 22 Feb 2018 22:21:33 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] SCSI fixes for 4.16-rc2
On Thu, 2018-02-22 at 16:37 -0800, Linus Torvalds wrote:
> On Thu, Feb 22, 2018 at 11:28 AM, James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> >
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-
> > fixes
>
> When I pull that, I get something completely different from what you
> claim I should get. Much bigger, and a lot more commits.
>
> Hmm?
>
> Dropped.
OK, I see the problem, but I don't currently have an explanation for
how it happened. The scsi-fixes tag somehow became attached to a push
of the misc tree for the next merge window instead of the fixes branch.
I've reset it to where it should be
commit 1bc5ad3a6acdcf56f83272f2de1cd2389ea9e9e2
Author: Manish Rangankar <manish.rangankar@...ium.com>
Date: Sun Feb 11 22:48:41 2018 -0800
scsi: qla4xxx: skip error recovery in case of register disconnect.
So it should all be correct if you re-pull.
I suppose it's good that the checks and balances of changelog +
diffstat caught this; I'll poke about in my current preparation scripts
to see if I can find out what went wrong.
James
Powered by blists - more mailing lists