From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
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.15+ merge window
Date: Fri, 14 Jan 2022 14:46:01 +0100 [thread overview]
Message-ID: <CAHk-=wjx_q9Aa=o5kiiSpCC_4U+H2D1=H3umFOwVMUbFmdQjGA@mail.gmail.com> (raw)
In-Reply-To: <31f8716fbb4f1e2a332b2b3e3243a170e8b01145.camel@HansenPartnership.com>
On Thu, Jan 13, 2022 at 9:22 PM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> Adrian Hunter (4):
> scsi: ufs: ufs-pci: Add support for Intel ADL
> scsi: ufs: Let devices remain runtime suspended during system suspend
> scsi: ufs: core: Fix another task management completion race
> scsi: ufs: core: Fix task management completion timeout race
[...]
You seem to have forgotten to fetch my upstream tree, so your shortlog
(or diffstat) doesn't seem to take the various fixes pulls you did for
5.16 into account.
The only actual new commit I got from Adrian was
Adrian Hunter (1):
scsi: ufs: Let devices remain runtime suspended during system suspend
and the same for other fixes..
Not a big deal, but when the shortlog and diffstat don't match what I
get, I waste time figuring out why. So please do a "git fetch linus"
or whatever so that git can take all your previous pulls into
account..
Linus
next prev parent reply other threads:[~2022-01-14 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 20:22 [GIT PULL] first round of SCSI updates for the 5.15+ merge window James Bottomley
2022-01-14 13:46 ` Linus Torvalds [this message]
2022-01-14 17:39 ` James Bottomley
2022-01-14 14:39 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-03-24 19:24 James Bottomley
2022-03-25 2:47 ` pr-tracker-bot
2021-11-05 12:14 James Bottomley
2021-11-05 12:37 ` Steffen Maier
2021-11-05 12:43 ` James Bottomley
2021-11-05 12:53 ` Steffen Maier
2021-11-05 16:08 ` 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='CAHk-=wjx_q9Aa=o5kiiSpCC_4U+H2D1=H3umFOwVMUbFmdQjGA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).