From: Ingo Molnar <mingo@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Biju Das <biju.das.jz@bp.renesas.com>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Maulik Shah <quic_mkshah@quicinc.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [GIT PULL] irqchip fixes for 6.6, take #1
Date: Fri, 29 Sep 2023 23:05:51 +0200 [thread overview]
Message-ID: <ZRc8L+fJAqHuWEg+@gmail.com> (raw)
In-Reply-To: <CAMuHMdU7WuV6moiRWuChFzBr1n5pGxuEMeuoA1YWYw4v8QAN1w@mail.gmail.com>
* Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Ingo,
>
> On Thu, Sep 28, 2023 at 11:17 PM Ingo Molnar <mingo@kernel.org> wrote:
> > So the tags should be something like:
> >
> > Fixes: 397ad94668c1 ("arm64: dts: qcom: sm8150: Add pdc interrupt controller node")
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> > Link: https://lore.kernel.org/r/20230905-topic-sm8x50-upstream-pdc-ver-v4-2-fc633c7df84b@linaro.org
> >
> > Ie. we generally sort the tags not chronologically (or whatever the original idea
> > was), but group them topically, sort the groups by importance, and only within
> > the group is there chronological order.
>
> The tags should represent the order of the hand-off chain:
>
> https://elixir.bootlin.com/linux/v6.6-rc1/source/Documentation/process/submitting-patches.rst#L449
>
> and chronological history:
>
> https://elixir.bootlin.com/linux/v6.6-rc1/source/Documentation/process/submitting-patches.rst#L493
That chronological requirement is only for the SOB chain itself.
To quote Documentation/process/submitting-patches.rst:
Standard sign-off procedure applies, i.e. the ordering of Signed-off-by: tags should
reflect the chronological history of the patch insofar as possible,
which is exactly what I wrote above:
> > > only within the group is there chronological order.
^^^^^^^^^^^^^^^^^^^^^
In fact it would be crazy to require that all the tags are chronological,
in the random order they arrived, which the commits I pointed out appeared to be.
Thanks,
Ingo
prev parent reply other threads:[~2023-09-29 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 9:41 [GIT PULL] irqchip fixes for 6.6, take #1 Marc Zyngier
2023-09-28 21:10 ` [tip: irq/urgent] Merge tag 'irqchip-fixes-6.6-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent tip-bot2 for Thomas Gleixner
2023-09-28 21:12 ` [GIT PULL] irqchip fixes for 6.6, take #1 Ingo Molnar
2023-09-28 21:17 ` Ingo Molnar
2023-09-29 12:31 ` Geert Uytterhoeven
2023-09-29 21:05 ` Ingo Molnar [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=ZRc8L+fJAqHuWEg+@gmail.com \
--to=mingo@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert@linux-m68k.org \
--cc=konrad.dybcio@linaro.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=quic_mkshah@quicinc.com \
--cc=tglx@linutronix.de \
/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