From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM SoC fixes for 6.9, part 3
Date: Wed, 08 May 2024 21:52:32 +0200 [thread overview]
Message-ID: <9c7ff142-214a-4329-b288-00f260ba50e3@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=whbpyM=Vgb8cM_aoRtZf7GDWq7Wa-cJ=J0DpVkfnd1PBg@mail.gmail.com>
On Wed, May 8, 2024, at 19:22, Linus Torvalds wrote:
> On Tue, 7 May 2024 at 23:00, Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> ARM SoC fixes for 6.9, part 3
>
> Hmm. Some of this already came in in "part 2", and your diffstat is
> wrong as a result.
>
> You seem to have done the mtk-soc merge again:
>
>> Arnd Bergmann (3):
>> Merge tag 'mtk-soc-fixes-for-v6.9' of https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux into for-next
>
> and this part of the diffstat:
>
>> drivers/soc/mediatek/Kconfig | 1 +
>> drivers/soc/mediatek/mtk-svs.c | 7 +++++--
>
> doesn't show up for me because I already had it from your
> soc-fixes-6.9-2 pull request.
>
> I've pulled this, but am a bit confused about how you missed your own
> previous pull..
I'm still not sure either what happened exactly, but I do see
that this is a pull request that I ended up pulling manually
using 'git pull' instead of using 'b4' because it had a malformed
URL, and that confused the rest of the tooling I normally
have in place to avoid this.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-08 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 6:00 [GIT PULL] ARM SoC fixes for 6.9, part 3 Arnd Bergmann
2024-05-08 17:22 ` Linus Torvalds
2024-05-08 19:52 ` Arnd Bergmann [this message]
2024-05-08 17:24 ` 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=9c7ff142-214a-4329-b288-00f260ba50e3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@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 read-only IMAP folder(s) and NNTP newsgroup(s).