From: Radu Rendec <rrendec@redhat.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Daniel Tsai" <danielsftsai@google.com>,
"Marek Behún" <kabel@kernel.org>,
"Krishna Chaitanya Chundru" <quic_krichai@quicinc.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Brian Masney" <bmasney@redhat.com>,
"Eric Chanudet" <echanude@redhat.com>,
"Alessandro Carminati" <acarmina@redhat.com>,
"Jared Kangas" <jkangas@redhat.com>,
"Jon Hunter" <jonathanh@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] fixup! genirq: Add interrupt redirection infrastructure
Date: Mon, 12 Jan 2026 15:24:56 -0500 [thread overview]
Message-ID: <2105d279ce5df15bc15e29a5e21ab3c5b6e440a1.camel@redhat.com> (raw)
In-Reply-To: <87fr8bg6lv.ffs@tglx>
Hello, Thomas!
On Sun, 2026-01-11 at 22:52 +0100, Thomas Gleixner wrote:
> Thanks for taking care of this, but this is not really the way how it
> works.
>
> $subject: fixup!.... is neither a valid nor a useful subject line.
>
> $subject is documented to be a concise summary of the change at hand, so
> in this case this should be something like:
>
> [PATCH] genirq: Update effective affinity for redirected interrupts
>
> [snip]
>
> It also lacks a 'Fixes:' tag as the code is already merged, no?
>
>
> [snip]
Apologies, and thanks a lot for taking the time to provide such
detailed feedback!
I mistakenly assumed the original commit could still be *amended*, and
the format I used was a (failed) attempt at asking that. I didn't
realize the commit was immutable once included in the tip tree, and
didn't pay much attention to the commit message because I thought it
would be discarded anyway while amending.
In my defense, $subject: "fixup! <original commit subject>" is a format
recognized by `git rebase` and used on some subsystems to fix already
accepted patches *before* they are merged upstream. It just doesn't
apply here. Lesson learned!
I will re-send it using the standard format for fixing a commit that's
already merged, and follow all the suggestions you made.
--
Best regards,
Radu
prev parent reply other threads:[~2026-01-12 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 17:52 Radu Rendec
2026-01-11 21:52 ` Thomas Gleixner
2026-01-12 20:24 ` Radu Rendec [this message]
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=2105d279ce5df15bc15e29a5e21ab3c5b6e440a1.camel@redhat.com \
--to=rrendec@redhat.com \
--cc=acarmina@redhat.com \
--cc=bhelgaas@google.com \
--cc=bmasney@redhat.com \
--cc=danielsftsai@google.com \
--cc=echanude@redhat.com \
--cc=jingoohan1@gmail.com \
--cc=jkangas@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=kabel@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=robh@kernel.org \
--cc=tglx@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®