From: Fabio Estevam <festevam@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
Lucas Stach <l.stach@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] arm64: dts: imx8mp: Fix SDMA2/3 clocks
Date: Thu, 17 Aug 2023 08:38:29 -0300 [thread overview]
Message-ID: <CAOMZO5AxmSEF2=G_jNnFkvA4SbAr28W78UtpaOmWQ-fn86P9Fw@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7xL2BA0+Z5GhrvuS0j+s6WOLVScaC9DQ1+AxHYjY6DwAAA@mail.gmail.com>
Hi Adam,
On Wed, Aug 16, 2023 at 12:34 AM Adam Ford <aford173@gmail.com> wrote:
> I tried to do that with the fixes tag below. Do you want me to
> re-submit the patches with this changed? I was hoping to avoid
> referencing the same patch and hash twice in the same commit message.
IMHO there is no problem at all by referencing the same commit hash twice.
In fact, it makes it clearer as to what exactly you are referencing.
Please re-submit it, thanks.
prev parent reply other threads:[~2023-08-17 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 23:11 [PATCH V2 1/2] arm64: dts: imx8mp: Fix SDMA2/3 clocks Adam Ford
2023-08-15 23:11 ` [PATCH V2 2/2] arm64: dts: imx8mp-beacon-kit: Fix audio_pll2 clock Adam Ford
2023-08-16 1:58 ` Fabio Estevam
2023-08-16 1:57 ` [PATCH V2 1/2] arm64: dts: imx8mp: Fix SDMA2/3 clocks Fabio Estevam
2023-08-16 3:33 ` Adam Ford
2023-08-17 11:38 ` Fabio Estevam [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='CAOMZO5AxmSEF2=G_jNnFkvA4SbAr28W78UtpaOmWQ-fn86P9Fw@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).