From: Sean Young <sean@mess.org>
To: Christian Hewitt <christianshewitt@gmail.com>,
Zhang Ning <zhangn1985@qq.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
narmstrong@baylibre.com, martin.blumenstingl@googlemail.com,
linux-amlogic@lists.infradead.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [v7 3/4] dt-bindings: arm: amlogic: add MagicBox M16S bindings
Date: Fri, 29 Jul 2022 09:42:03 +0100 [thread overview]
Message-ID: <YuOdWyF2yJVhh415@gofer.mess.org> (raw)
In-Reply-To: <tencent_F809BC863B83870BBEB1EF76499B3969B607@qq.com>
On Thu, Jul 28, 2022 at 07:48:57AM +0800, Zhang Ning wrote:
> Christian Hewitt told me to split to 2 patches, 1st for manufactor, 2nd
> for device, how to handle your Acked-by?
>
> btw, he also said I'm wrong in handle Sean's Signed-of-by, still don't
> know how to do in next version. Should I just not send this patch?
Christian can you explain *on list* what is wrong with handling my
Signed-off-by? As far as I can see Ning has done the right thing.
Please keep the conversation on list so we're all in the loop.
Sean
next prev parent reply other threads:[~2022-07-29 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220726143649.142574-1-zhangn1985@qq.com>
[not found] ` <tencent_A962A641C180EEC2680CA53DDD6643BA6E05@qq.com>
2022-07-27 7:06 ` [v7 3/4] dt-bindings: arm: amlogic: add MagicBox M16S bindings Krzysztof Kozlowski
[not found] ` <tencent_27A429274A1A0E0C082FA6C700DA856DDA09@qq.com>
2022-07-27 15:26 ` Krzysztof Kozlowski
2022-07-27 15:27 ` Krzysztof Kozlowski
[not found] ` <tencent_F809BC863B83870BBEB1EF76499B3969B607@qq.com>
2022-07-28 1:21 ` Christian Hewitt
2022-07-28 7:01 ` Krzysztof Kozlowski
2022-07-29 8:42 ` Sean Young [this message]
2022-07-29 9:06 ` Christian Hewitt
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=YuOdWyF2yJVhh415@gofer.mess.org \
--to=sean@mess.org \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=zhangn1985@qq.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;
as well as URLs for NNTP newsgroup(s).