linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Aswath Govindraju <a-govindraju@ti.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	PCI <linux-pci@vger.kernel.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH v2] dt-bindings: PCI: ti,j721e: Add device id for J721S2
Date: Thu, 27 Jan 2022 12:25:24 -0600	[thread overview]
Message-ID: <CAL_Jsq+9aDzexJUaTPCY=SChqC1Ek1xL0qj-CorGjvXk=Sn20w@mail.gmail.com> (raw)
In-Reply-To: <20220127152333.GA101708@bhelgaas>

On Thu, Jan 27, 2022 at 9:24 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> [+cc Lorenzo, initial post
> https://lore.kernel.org/r/20211130035608.13492-1-a-govindraju@ti.com]
>
> On Tue, Jan 25, 2022 at 12:06:16PM +0530, Aswath Govindraju wrote:
> > On 30/11/21 9:26 am, Aswath Govindraju wrote:
> > > Document the device id of J721S2 SoC.
> > >
> > > Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> > > ---
> > >
> >
> > May I know if this patch can be picked up?
>
> "git log Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml"
> says most changes to this file have been applied by Lorenzo, so I cc'd
> him.

I can take it if there's not other pending changes to this file for 5.18?

Rob

      reply	other threads:[~2022-01-27 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30  3:56 [PATCH v2] dt-bindings: PCI: ti,j721e: Add device id for J721S2 Aswath Govindraju
2021-12-07 21:14 ` Rob Herring
2022-01-25  6:36 ` Aswath Govindraju
2022-01-27 15:23   ` Bjorn Helgaas
2022-01-27 18:25     ` Rob Herring [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='CAL_Jsq+9aDzexJUaTPCY=SChqC1Ek1xL0qj-CorGjvXk=Sn20w@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=a-govindraju@ti.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nm@ti.com \
    --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).