From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string
Date: Mon, 1 May 2023 14:09:02 +0200 [thread overview]
Message-ID: <03806421-73ac-0d82-f1cb-e54c2e8f27e9@linaro.org> (raw)
In-Reply-To: <878re8741n.fsf@tarshish>
On 01/05/2023 12:01, Baruch Siach wrote:
> Hi Krzysztof,
>
> On Mon, May 01 2023, Krzysztof Kozlowski wrote:
>> On 25/04/2023 10:31, Baruch Siach wrote:
>>> On Mon, Apr 24 2023, Baruch Siach wrote:
>>>> Only arm,primecell is documented as compatible string for Primecell
>>>> peripherals. Current code agrees with that.
>>>
>>> Once again my patches do not show up in patchwork. But they do show in
>>> lore:
>>>
>>> https://lore.kernel.org/linux-devicetree/9e137548c4e76e0d8deef6d49460cb37897934ca.1682333574.git.baruch@tkos.co.il/
>>
>> You used subject prefix which targets Doc subsystem, but did not Cc Doc
>> maintainers (get_maintainers do not print them). If you target Rob's
>> Patchwork, probably you need to fix subject prefix. There is no "dt" prefix.
>
> Thanks for the tip.
>
> All previous commits touching Documentation/devicetree/usage-model.rst
> use 'docs' for subject prefix, including one from Rob. I followed this
> example.
Hm, I see Rob and others indeed used "dt:". I guess Rob's filters might
need some updates?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-01 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:52 [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Baruch Siach
2023-04-24 10:52 ` [PATCH v2 2/2] docs: zh_CN/devicetree: sync usage-model fix Baruch Siach
2023-04-27 13:28 ` Yanteng Si
2023-04-25 8:31 ` [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Baruch Siach
2023-05-01 9:53 ` Krzysztof Kozlowski
2023-05-01 10:01 ` Baruch Siach
2023-05-01 12:09 ` Krzysztof Kozlowski [this message]
2023-05-09 8:36 ` Baruch Siach
2023-06-08 13:31 ` Rob Herring
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=03806421-73ac-0d82-f1cb-e54c2e8f27e9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexs@kernel.org \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=siyanteng@loongson.cn \
/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).