From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>
Cc: "Neil Armstrong" <neil.armstrong@linaro.org>,
"Olof Johansson" <olof@lixom.net>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 03/18] soc: amlogic: Move power-domain drivers to the genpd dir
Date: Mon, 10 Jul 2023 14:45:12 +0200 [thread overview]
Message-ID: <2ef84fb8-b5eb-4c9a-b8a1-0c5f33e7f572@app.fastmail.com> (raw)
In-Reply-To: <CAPDyKFoRtEXTGQkNzGza-sS_j1ajGmjtCTaoPB7PXVDE2bS0tQ@mail.gmail.com>
On Mon, Jul 10, 2023, at 14:37, Ulf Hansson wrote:
> On Sun, 9 Jul 2023 at 04:21, Bjorn Andersson <andersson@kernel.org> wrote:
>> On Fri, Jul 07, 2023 at 05:27:39PM +0200, Ulf Hansson wrote:
>
> If I understand correctly, you are suggesting that each platform
> maintainer should merge the immutable branch with patch1 - and that I
> should send the patches (based on the immutable branch) to each of the
> platform maintainers to manage. Instead of one pull request with
> everything directly to Arnd, right?
>
> This still means that Arnd will have to resolve the conflicts as the
> pull requests arrive in his inbox.
>
> Although, I guess what you are looking for is less work for the soc/
> maintainers, which seems reasonable. Although, in that case, I might
> as well share an immutable branch with the complete series, rather
> than just patch1. That should help Arnd too, I think.
>
> Again, let's leave the call to Arnd on what to do.
I think it's much easier for me to pick up a single branch with
all of your patches. For platform maintainers, other changes can
go one of two ways:
- send a normal pull requests with changes against the same
files, and have me take care of any conflicts where they
arise. Since most of the changes are just simple file moves
rather than changing file contents, 'git mergetool' handles
these fine is most cases
- If there is a non-obvious merge, the entire genpd branch
can be shared as an immutable branch, with patches for
a particular platform rebased on top of that branch.
Arnd
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-07-10 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230707140434.723349-1-ulf.hansson@linaro.org>
2023-07-07 14:04 ` Ulf Hansson
2023-07-07 14:42 ` Neil Armstrong
2023-07-07 14:54 ` Ulf Hansson
2023-07-07 15:12 ` neil.armstrong
2023-07-07 15:27 ` Ulf Hansson
2023-07-09 2:25 ` Bjorn Andersson
2023-07-10 12:37 ` Ulf Hansson
2023-07-10 12:45 ` Arnd Bergmann [this message]
2023-07-13 0:48 ` Bjorn Andersson
2023-07-13 9:50 ` Ulf Hansson
2023-07-14 3:10 ` Bjorn Andersson
2023-07-07 19:04 ` Arnd Bergmann
2023-07-07 18:25 ` Martin Blumenstingl
2023-07-11 6:38 ` Ulf Hansson
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=2ef84fb8-b5eb-4c9a-b8a1-0c5f33e7f572@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andersson@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=olof@lixom.net \
--cc=ulf.hansson@linaro.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®