From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 2/4] soc: drivers for 7.3
Date: Wed, 19 Aug 2026 13:11:12 +0200 [thread overview]
Message-ID: <e7d5b920-80d9-4d76-b92f-03494081eb9d@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=wh8khg-Odf9cg2jWe1jvSviTwGgKG9vUDzYNdMzgmxDhQ@mail.gmail.com>
On Wed, Aug 19, 2026, at 04:46, Linus Torvalds wrote:
> On Tue, 18 Aug 2026 at 14:17, Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> .mailmap | 6 +-
>> Documentation/ABI/testing/debugfs-vfio | 26 +
>> .../ABI/testing/sysfs-bus-pci-drivers-xhci_hcd | 2 +-
> [...]
>> tools/virtio/linux/mod_devicetable.h | 14 +
>> tools/virtio/linux/virtio_features.h | 79 ++
>> 2565 files changed, 15693 insertions(+), 8154 deletions(-)
>
> Well, that diffstat was just garbage. The real one looks something like this:
>
> 121 files changed, 4566 insertions(+), 1492 deletions(-)
>
...
>
> I don't actually require that kind of better pull request, but it
> would make your PRs look nicer.
Thanks for letting me know, I really should have caught this
while sending the pull request. I was fairly sure that I had
not introduced any backmerges or octopus merges myself, so
I didn't pay enough attention when preparing the pull requests.
What what I can tell, the thing that tripped me up was commit
980a8bfe7bae ("Merge branches 'for-next/scmi/fixes' and
'for-next/ffa/fixes'"), which I pulled in as part of a normal
downstream branch.
Arnd
next prev parent reply other threads:[~2026-08-19 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 21:16 [GIT PULL 2/4] soc: drivers for 7.3 Arnd Bergmann
2026-08-19 2:46 ` Linus Torvalds
2026-08-19 11:11 ` Arnd Bergmann [this message]
2026-08-19 2:58 ` 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=e7d5b920-80d9-4d76-b92f-03494081eb9d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@lists.linux.dev \
--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