From: Steen Hegelund <steen.hegelund@microchip.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars Povlsen <lars.povlsen@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
<UNGLinuxDriver@microchip.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: microchip: add missing cache properties
Date: Wed, 17 May 2023 13:38:39 +0200 [thread overview]
Message-ID: <7772a5981d9a3d46056a53997162d1d75d22a701.camel@microchip.com> (raw)
In-Reply-To: <151169f7-dcdb-47f1-9616-67c3c388a233@linaro.org>
Hi Krzysztof,
I would love to do that, but I am not familiar with the procedure, so maybe you
could help me out?
This is my understanding of what I need to do:
Clone the upstream repo listed in MAINTAINERS:
git clone git@github.com:microchip-ung/linux-upstream.git
cd linux-upstream
git checkout sparx5-next
Fetch the latest mainline tag from upstream:
git fetch git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git tag\
v6.4-rc2 --no-tags
Rebase the current branch on top of that tag:
git rebase v6.4-rc2
Use b4 to fetch and apply the mail thread patch series:
b4 shazam -tsl 20230421223155.115339-1-krzysztof.kozlowski@linaro.org
Tag the current work for inclusion in the next kernel version with a decription:
git tag -s sparx5-dt-6.5
Push work that to the public repo:
git push origin sparx5-dt-6.5
Create a pull request (to stdout) to be included in an email to the maintainers:
git request-pull v6.4-rc2 origin sparx5-dt-6.5
Send this PR to the maintainers and CC co-maintainers.
Is this the correct procedure?
Who should I send the PR email to (is there a list somewhere)?
BR
Steen
On Tue, 2023-05-16 at 18:30 +0200, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On 22/04/2023 00:31, Krzysztof Kozlowski wrote:
> > As all level 2 and level 3 caches are unified, add required
> > cache-unified and cache-level properties to fix warnings like:
> >
> > sparx5_pcb125.dtb: l2-cache0: 'cache-level' is a required property
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> > ---
>
> Anyone from Microchip picking this up?
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-05-17 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:31 [PATCH] arm64: dts: microchip: add missing cache properties Krzysztof Kozlowski
2023-05-16 16:30 ` Krzysztof Kozlowski
2023-05-17 11:38 ` Steen Hegelund [this message]
2023-05-17 12:10 ` Krzysztof Kozlowski
2023-05-17 12:37 ` Conor Dooley
2023-05-17 12:46 ` Steen Hegelund
2023-05-17 12:58 ` Conor Dooley
2023-05-17 15:22 ` Nicolas Ferre
2023-05-17 12:23 ` Krzysztof Kozlowski
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=7772a5981d9a3d46056a53997162d1d75d22a701.camel@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).