linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: vigneshr@ti.com, lpieralisi@kernel.org, robh@kernel.org,
	kw@linux.com, bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes
Date: Thu, 24 Nov 2022 10:26:18 +0100	[thread overview]
Message-ID: <1eb8a559-8cef-1093-0ff3-bfbfeceff60f@kernel.org> (raw)
In-Reply-To: <Y38kJ0nEBf+Mztpe@ubuntu>

On 24/11/2022 08:58, Matt Ranostay wrote:
> On Wed, Nov 23, 2022 at 05:04:15PM +0100, Krzysztof Kozlowski wrote:
>> On 15/11/2022 16:03, Matt Ranostay wrote:
>>> Add num-lanes schema checks based on compatible string on available
>>> lanes for that platform.
>>>
>>> Signed-off-by: Matt Ranostay <mranostay@ti.com>
>>> ---
>>>  .../bindings/pci/ti,j721e-pci-ep.yaml         | 28 +++++++++++++++++--
>>>  .../bindings/pci/ti,j721e-pci-host.yaml       | 28 +++++++++++++++++--
>>>  2 files changed, 50 insertions(+), 6 deletions(-)
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC.  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.
>>
>> You miss not only people but also lists, meaning this will not be
>> automatically tested.
>>
> 
> Noted. Reran script with --git as well and it picked up a few additional people
> to Cc.

No need for --git. Just run it normally and Cc all folks listed as
reviewer, maintainer/supporter and all the lists. That's one simple
command: scripts/get_maintainer.pl ./*.patch
(which can be easily automated and combined with git send-email / bash
aliases or scripts).

So don't add some unusual or random addresses, just add the *required*
addresses.


Best regards,
Krzysztof


  reply	other threads:[~2022-11-24  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 15:03 [PATCH v6 0/5] PCI: add 4x lane support for pci-j721e controllers Matt Ranostay
2022-11-15 15:03 ` [PATCH v6 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes Matt Ranostay
2022-11-23 16:04   ` Krzysztof Kozlowski
2022-11-24  7:58     ` Matt Ranostay
2022-11-24  9:26       ` Krzysztof Kozlowski [this message]
2022-11-15 15:03 ` [PATCH v6 2/5] PCI: j721e: Add per platform maximum lane settings Matt Ranostay
2022-11-15 15:03 ` [PATCH v6 3/5] PCI: j721e: Add PCIe 4x lane selection support Matt Ranostay
2022-11-15 15:03 ` [PATCH v6 4/5] dt-bindings: PCI: ti,j721e-pci-*: add j784s4-pci-* compatible strings Matt Ranostay
2022-11-23 16:04   ` Krzysztof Kozlowski
2022-11-15 15:03 ` [PATCH v6 5/5] PCI: j721e: add j784s4 PCIe configuration Matt Ranostay
2022-11-15 15:37 ` [PATCH v6 0/5] PCI: add 4x lane support for pci-j721e controllers Bjorn Helgaas
2022-11-23  5:51   ` Matt Ranostay

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=1eb8a559-8cef-1093-0ff3-bfbfeceff60f@kernel.org \
    --to=krzk@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mranostay@ti.com \
    --cc=robh@kernel.org \
    --cc=vigneshr@ti.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).