From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: ChiYuan Huang <u0084500@gmail.com>, Rob Herring <robh@kernel.org>
Cc: matthias.bgg@gmail.com, devicetree@vger.kernel.org,
cy_huang@richtek.com, linux-mediatek@lists.infradead.org,
alice_chen@richtek.com, robh+dt@kernel.org, lee@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
chiaen_wu@richtek.com
Subject: Re: [PATCH v2] dt-bindings: mfd: mt6370: fix the indentation in the example
Date: Thu, 15 Sep 2022 16:25:45 +0100 [thread overview]
Message-ID: <bb932677-d7b5-a39f-ebb9-4a64812591a1@linaro.org> (raw)
In-Reply-To: <CADiBU3_6dXf1TUv9f7HbFfrqsfMUmT1Ejve6+O6OGnmTtxzpEQ@mail.gmail.com>
On 15/09/2022 14:56, ChiYuan Huang wrote:
>>
>> Please add Acked-by/Reviewed-by tags when posting new versions. However,
>> there's no need to repost patches *only* to add the tags. The upstream
>> maintainer will do that for acks received on the version they apply.
>>
>> If a tag was not added on purpose, please state why and what changed.
>>
> I'm not sure about the rule.
> AngeloGioacchino said I need to add the 'Fixes' tag.
> I think it might be important.
> And I immediately submit the v2 patch and add the 'fixes' tag.
> So patch v3 and add 'Acked-by' tag?
https://lore.kernel.org/all/20220914150620.GA2221443-robh@kernel.org/
https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-15 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 12:18 cy_huang
2022-09-15 13:43 ` Rob Herring
2022-09-15 13:56 ` ChiYuan Huang
2022-09-15 15:25 ` Krzysztof Kozlowski [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=bb932677-d7b5-a39f-ebb9-4a64812591a1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alice_chen@richtek.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=u0084500@gmail.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
all inboxes | Powered by JetHome®