From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <maz@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the tip tree
Date: Fri, 26 Jul 2024 14:04:05 +0200 [thread overview]
Message-ID: <871q3gwea2.ffs@tglx> (raw)
In-Reply-To: <8734o05q2w.wl-maz@kernel.org>
On Tue, Jul 23 2024 at 12:02, Marc Zyngier wrote:
> On Sun, 21 Jul 2024 23:31:53 +0100,
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> - Target SHA1 does not exist
>>
>> Maybe you meant
>>
>> Fixes: b5712bf89b4b ("irqchip/gic-v3-its: Provide MSI parent for PCI/MSI[-X]")
>
> Odd.
>
> The SHA1 in the commit messages do match the Thomas' devmsi-arm-v4-2
> tag as of last Thursday. I guess the patches have been rebased on top
> of tip branch and not merged.
>
> The whole thing is now in Linus tree, so it is too late to do anything
> about it, unfortunately.
Yes. My bad. I missed to fixup the tags when I pulled over the whole
pile to tip irq/msi.
next prev parent reply other threads:[~2024-07-26 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 22:31 linux-next: Fixes tags need some work in the tip tree Stephen Rothwell
2024-07-23 11:02 ` Marc Zyngier
2024-07-26 12:04 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-08 2:16 Stephen Rothwell
2021-03-08 8:38 ` Ingo Molnar
2020-01-15 20:03 Stephen Rothwell
2019-11-05 11:18 Stephen Rothwell
2019-11-05 11:52 ` Thomas Gleixner
2019-10-22 20:16 Stephen Rothwell
2019-10-22 20:30 ` Thomas Hellstrom
2019-10-23 10:16 ` Ingo Molnar
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=871q3gwea2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).