From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 5.6+ merge window
Date: Fri, 05 Jun 2020 14:41:48 -0700 [thread overview]
Message-ID: <1591393308.4728.100.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wjy8sMqjft6ALTo28UECex84uiYEo=BJbLUJ_CHrPmOEQ@mail.gmail.com>
On Fri, 2020-06-05 at 14:25 -0700, Linus Torvalds wrote:
> On Fri, Jun 5, 2020 at 2:18 PM James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > Um, no, shuffles feet ... I actually tagged the wrong branch:
>
> Ok, now I see the changes, but I see more than you reported.
>
> These seem to be new compared to your pull request:
>
> Al Viro (4):
> scsi: hpsa: Lift {BIG_,}IOCTL_Command_struct copy{in,out} into
> hpsa_ioctl()
> scsi: hpsa: Don't bother with vmalloc for
> BIG_IOCTL_Command_struct
> scsi: hpsa: Get rid of compat_alloc_user_space()
> scsi: hpsa: hpsa_ioctl(): Tidy up a bit
>
> Can Guo (1):
> scsi: ufs: Don't update urgent bkops level when toggling auto
> bkops
>
> Stanley Chu (1):
> scsi: ufs: Remove redundant urgent_bkop_lvl initialization
>
> They don't look alarming, but I don't like how I don't see what you
> _claim_ I should see.
>
> Hmm?
Ah right, my MO is to do the first push and then start gathering for
the second. pushing the tag again picked up the new stuff I've been
gathering. Let me rewind the tag back to where it was for the original
push and then try again.
Done. You should now see no stray additional patches on the scsi-misc
tag.
Sorry again, I believe I've actually fully verified the diffstat
matches this time ... (famous last words ..)
James
next prev parent reply other threads:[~2020-06-05 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 4:55 [GIT PULL] first round of SCSI updates for the 5.6+ merge window James Bottomley
2020-06-05 21:11 ` Linus Torvalds
2020-06-05 21:18 ` James Bottomley
2020-06-05 21:25 ` Linus Torvalds
2020-06-05 21:41 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 16:06 James Bottomley
2020-04-03 0:40 ` pr-tracker-bot
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=1591393308.4728.100.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).