From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@denx.de>, Biju Das <biju.das.jz@bp.renesas.com>
Cc: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: Inserting patch into history was Re: [PATCH v2 5.10.y-cip 15/15] clk: renesas: r9a07g044: Mark IA55_CLK and DMAC_ACLK critical
Date: Mon, 10 Jan 2022 20:18:55 +0100 [thread overview]
Message-ID: <54372c9e-b214-c562-ff7b-eb830bf55db7@siemens.com> (raw)
In-Reply-To: <20220110183329.GC3396@duo.ucw.cz>
On 10.01.22 19:33, Pavel Machek wrote:
> Hi!
>
>> Is it possible to rearrange this patch before [1] and after [2]?
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-5.10.y-cip&id=dcbef66029571fbada7522b2db0790e5ff054c66
>>
>> [2]https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-5.10.y-cip&id=e2568c0c7de565a5688544907422ca470844df87
>>
>
> Wow.
>
> It means changing history. We usually try to avoid that, as it will
> cause problems for people using git head. But we did not yet do a
> release with those commits, so it is not completely out of question.
>
> How important is that? At the very least I'll need to know that rest
> of the kernel team is okay with it.
>
> commit e2568c0c7de565a5688544907422ca470844df87
> Author: Biju Das <biju.das.jz@bp.renesas.com>
> Date: Mon Dec 20 13:31:30 2021 +0000
>
> commit dcbef66029571fbada7522b2db0790e5ff054c66
> Author: Biju Das <biju.das.jz@bp.renesas.com>
> Date: Thu Dec 16 12:54:46 2021 +0000
>
> clk: renesas: rzg2l: Fix clk status function
>
> Best regards,
> Pavel
Patch application in unfortunate order is a very common issue in
upstream: dependencies are missed, patches take different routes through
different maintainer trees, bugs get fixed only after the patch was
applied. In none of these cases, a maintainer did a force-push so far
(to my best knowledge), why should CIP do that?
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-01-10 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:53 [PATCH v2 5.10.y-cip 00/15] Add ADC/CANFD/IIC support for RZ/G2L Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 01/15] i2c: riic: Add RZ/G2L support Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 02/15] arm64: defconfig: Enable RIIC Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 03/15] dt-bindings: iio: adc: Add binding documentation for Renesas RZ/G2L A/D converter Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 04/15] iio: adc: Add driver " Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 05/15] iio: adc: rzg2l_adc: Fix -EBUSY timeout error return Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 06/15] iio: adc: rzg2l_adc: add missing clk_disable_unprepare() in rzg2l_adc_pm_runtime_resume() Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 07/15] clk: renesas: r9a07g044: Add SSIF-2 clock and reset entries Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 08/15] clk: renesas: r9a07g044: Add clock and reset entries for ADC Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 09/15] arm64: dts: renesas: r9a07g044: Add ADC node Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 10/15] arm64: defconfig: Enable RZG2L_ADC Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 11/15] arm64: dts: renesas: rzg2l-smarc: Enable I2C{0,1,3} support Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 12/15] arm64: dts: renesas: rzg2l-smarc-som: Move extal and memory nodes to SOM DTSI Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 13/15] arm64: dts: renesas: rzg2l-smarc-som: Enable ADC on SMARC platform Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 14/15] arm64: dts: renesas: rzg2l-smarc: Enable CANFD Lad Prabhakar
2022-01-10 11:53 ` [PATCH v2 5.10.y-cip 15/15] clk: renesas: r9a07g044: Mark IA55_CLK and DMAC_ACLK critical Lad Prabhakar
2022-01-10 14:16 ` Biju Das
2022-01-10 18:33 ` Inserting patch into history was " Pavel Machek
2022-01-10 19:17 ` Biju Das
2022-01-11 11:46 ` Pavel Machek
2022-01-10 19:18 ` Jan Kiszka [this message]
2022-01-10 18:38 ` [PATCH v2 5.10.y-cip 00/15] Add ADC/CANFD/IIC support for RZ/G2L Pavel Machek
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=54372c9e-b214-c562-ff7b-eb830bf55db7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.