devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Pavel Löbl" <pavel@loebl.cz>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: arm: sunxi: Add Banana Pi P2 Zero v1.1
Date: Mon, 27 Nov 2023 12:22:38 -0600	[thread overview]
Message-ID: <20231127182238.GA2068488-robh@kernel.org> (raw)
In-Reply-To: <20231120231017.614b9d61@alena.lan>

On Mon, Nov 20, 2023 at 11:10:17PM +0100, Pavel Löbl wrote:
> On Mon, 20 Nov 2023 10:16:55 +0100
> Krzysztof Kozlowski <krzk@kernel.org> wrote:
> 
> > On 18/11/2023 12:14, Pavel Löbl wrote:
> > > Document binding for Banana Pi P2 Zero v1.1.
> > > 
> > > Signed-off-by: Pavel Löbl <pavel@loebl.cz>
> > > ---
> > >  Documentation/devicetree/bindings/arm/sunxi.yaml | 6 ++++++  
> > 
> > Please use scripts/get_maintainers.pl to get a list of necessary
> > people and lists to CC (and consider --no-git-fallback argument). It
> > might happen, that command when run on an older kernel, gives you
> > outdated entries. Therefore please be sure you base your patches on
> > recent Linux kernel.
> That's what I did using next-20231117 kernel source, without
> --no-git-fallback argument though. The output seemed a bit long so I
> have not included every line in CC. So you are saying I should address
> more people next time?

You should use --no-git-fallback.

> Also it's not clear to me what should go to Cc: and what should go to
> To: when submitting. Looking at the list there does not seem to be a
> rule.

As Krzysztof said, doesn't matter, but I put people in To and lists in 
Cc. Setting up tocmd/cccmd with --nol and --nom options will do that 
automatically. Or you could put who should apply the patch in To 
(allwinner maintainers) and everyone else in Cc. But that takes manual 
work, so I don't do that.

Rob

  parent reply	other threads:[~2023-11-27 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 11:14 [PATCH 1/3] ARM: dts: sunxi: remove duplicated entries in makefile Pavel Löbl
2023-11-18 11:14 ` [PATCH 2/3] dt-bindings: arm: sunxi: Add Banana Pi P2 Zero v1.1 Pavel Löbl
2023-11-20  9:16   ` Krzysztof Kozlowski
2023-11-20 22:10     ` Pavel Löbl
2023-11-21  7:01       ` Krzysztof Kozlowski
2023-11-27 18:22       ` Rob Herring [this message]
2023-11-18 11:14 ` [PATCH 3/3] ARM: dts: sun8i: h2+: add support for Banana Pi P2 Zero board Pavel Löbl
2023-11-20  9:18   ` Krzysztof Kozlowski
2023-11-20 22:10     ` Pavel Löbl
2023-11-21  7:01       ` Krzysztof Kozlowski
2023-11-18 22:32 ` [PATCH 1/3] ARM: dts: sunxi: remove duplicated entries in makefile Jernej Škrabec

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=20231127182238.GA2068488-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk@kernel.org \
    --cc=pavel@loebl.cz \
    --cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).