From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Marshall Zhan <marshall.zhan.wiwynn@gmail.com>,
Delphine CC Chiu <delphine_cc_chiu@wiwynn.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH v2] arm: dts: aspeed: yosemite4: add gpio name for uart mux sel
Date: Tue, 20 May 2025 09:53:44 +0930 [thread overview]
Message-ID: <ac008c13719e2c91d7d377cd7a6151393934d854.camel@codeconstruct.com.au> (raw)
In-Reply-To: <7a5f60e9-376c-440e-a369-5c8d5e10c72a@kernel.org>
Hi Marshall,
On Mon, 2025-05-19 at 08:10 +0200, Krzysztof Kozlowski wrote:
> On 19/05/2025 04:48, Delphine CC Chiu wrote:
> > WIWYNN PROPRIETARY
> > This email (and any attachments) contains proprietary or confidential information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or distribution of this email or the content of this email is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this email immediately.
>
>
> We cannot test proprietary patches. Start working with the community in
> the open.
The kernel.org mailing list docs elaborate a little on Krzysztof's
point:
https://subspace.kernel.org/etiquette.html#do-not-include-confidentiality-disclaimers
(It's worth reading the rest of the page too).
Cheers,
Andrew
prev parent reply other threads:[~2025-05-20 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 2:48 Delphine CC Chiu
2025-05-19 6:10 ` Krzysztof Kozlowski
2025-05-20 0:23 ` Andrew Jeffery [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=ac008c13719e2c91d7d377cd7a6151393934d854.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=delphine_cc_chiu@wiwynn.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marshall.zhan.wiwynn@gmail.com \
--cc=patrick@stwcx.xyz \
--cc=robh@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
all inboxes | Powered by JetHome®