From: Conor Dooley <conor.dooley@microchip.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<stable@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<sashal@kernel.org>, <william.qiu@starfivetech.com>,
<emil.renner.berthing@canonical.com>,
<xingyu.wu@starfivetech.com>, <walker.chen@starfivetech.com>,
<robh@kernel.org>, <hal.feng@starfivetech.com>, <kernel@esmil.dk>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <richardcochran@gmail.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 6.6 1/4] riscv: dts: starfive: add assigned-clock* to limit frquency
Date: Thu, 12 Sep 2024 08:31:46 +0100 [thread overview]
Message-ID: <20240912-sketch-research-ad02c157cbf3@wendy> (raw)
In-Reply-To: <DBEFAD22C49AAFC6+58debc20-5281-4ae7-a418-a4b232be9458@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
On Thu, Sep 12, 2024 at 10:38:20AM +0800, WangYuli wrote:
>
> On 2024/9/9 19:17, Conor Dooley wrote:
> > [6.6] in the subject and Sasha/Greg/stable list on CC, so I figure it is
> > for stable, yeah. Only one of these patches is a "fix", and not really a
> > functional one, so I would like to know why this stuff is being
> > backported. I think under some definition of "new device IDs and quirks"
> > it could be suitable, but it'd be a looser definition than I personally
> > agree with!
> These submissions will help to ensure a more stable behavior for the RISC-V
> devices involved on the Linux-6.6.y kernel,
I'll accept that argument for the first patch, but the three that are
adding support for audio devices on the platform cannot really be
described as making behaviour more stable. I don't hugely object to
these being backported, but I would like a more accurate justification
for it being done - even if that is just that "we are using this board
with 6.6 and would like audio to work, which these 3 simple patches
allow it to do".
> and as far as I can tell,they
> won't introduce any new issues (please correct me if I'm wrong).
I don't know. Does this first patch require a driver change for the
mmc driver to work correctly?
> > Oh, and also, the 4 patches aren't threaded - you should fix that
>
> I apologize for my ignorance about the correct procedure...
>
> For instance,for these four commits,I first used 'git format-patch -4' to
> create four consecutive .patch files,and then used 'git send-email
> --annotate --cover-letter --thread ./*.patch' to send them,but the result
> wasn't as expected...
>
> I'm not sure where the problem lies...
I'm not sure, I don't send patches using that method. Usually I output
my patches to a directory and call git send-email using the path to that
directory.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-12 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:46 [PATCH 6.6 1/4] riscv: dts: starfive: add assigned-clock* to limit frquency WangYuli
2024-09-09 10:17 ` Conor Dooley
2024-09-09 10:38 ` Krzysztof Kozlowski
2024-09-09 11:17 ` Conor Dooley
2024-09-12 2:38 ` WangYuli
2024-09-12 7:31 ` Conor Dooley [this message]
2024-09-09 17:04 ` Greg KH
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=20240912-sketch-research-ad02c157cbf3@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=walker.chen@starfivetech.com \
--cc=wangyuli@uniontech.com \
--cc=william.qiu@starfivetech.com \
--cc=xingyu.wu@starfivetech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox