All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Adam Ford-BE <aford@beaconembedded.com>
Subject: Re: [PATCH V5] dt-bindings: soc: imx: Add binding doc for spba bus
Date: Sat, 20 Nov 2021 18:13:57 +0800	[thread overview]
Message-ID: <20211120101354.GA31998@dragon> (raw)
In-Reply-To: <CAHCN7xJK-iMMNMOtJCn9a2T2Jox=3LK3ANPGgZAC645wJw=3JQ@mail.gmail.com>

On Wed, Nov 03, 2021 at 09:36:59AM -0500, Adam Ford wrote:
> On Sat, Oct 16, 2021 at 3:11 PM Adam Ford <aford173@gmail.com> wrote:
> >
> > On Thu, Apr 1, 2021 at 4:19 PM Adam Ford <aford173@gmail.com> wrote:
> > >
> > > On Mon, Nov 30, 2020 at 4:02 PM Rob Herring <robh@kernel.org> wrote:
> > > >
> > > > On Wed, 18 Nov 2020 17:04:14 -0600, Adam Ford wrote:
> > > > > Add binding doc for fsl,spba-bus.
> > > > >
> > > > > Signed-off-by: Adam Ford <aford173@gmail.com>
> > > > > ---
> > > > > make dt_binding_check -j8 |grep spba
> > > > >   DTEX    Documentation/devicetree/bindings/bus/fsl,spba-bus.example.dts
> > > > >   DTC     Documentation/devicetree/bindings/bus/fsl,spba-bus.example.dt.yaml
> > > > >   CHECK   Documentation/devicetree/bindings/bus/fsl,spba-bus.example.dt.yaml
> > > > >
> > > > > V5:  Rebase on 5.10-rc2 to be able to check yaml
> > > > >      Add Reg entry
> > > > >
> > > > > V4:  Remove an accidental makefile change
> > > > >      Move type:object under additional properties
> > > > >
> > > > > V3:  Rebase sample from aips-bus example
> > > > >      Split off from series adding i.MX8M Nano functions to reduce noise
> > > > >
> > > > > V2:  Attempted to update yaml from feedback
> > > > >
> > > >
> > > > Applied, thanks!
> > >
> > > Rob,
> > >
> > > I am not seeing this anywhere.  Can you tell me where this was
> > > applied?  It's not appearing in Linux-next
> >
> > Rob,
> >
> > Patchwork shows this has been accepted [1], however I don't see that
> > it's still applied.
> >
> >
> > [1] https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201118230414.121316-1-aford173@gmail.com/
> >
> > Can you apply it?  It looks like building the device tree is throwing
> > messages because this is missing.
> >
> 
> Shawn,
> 
> Since you're the maintainer for the IMX stuff, can I update the
> MAINTAINERS file to add this yaml file under the IMX section?  When
> building device trees, it throws a bunch of splat because this patch
> was never applied, and checkpatch is showing it wants a maintainer.

checkpatch warning on maintainer shouldn't be a problem.  We don't
really want to bloat IMX entry in MAINTAINERS.

Shawn

      reply	other threads:[~2021-11-20 10:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 23:04 [PATCH V5] dt-bindings: soc: imx: Add binding doc for spba bus Adam Ford
2020-11-26 13:50 ` Adam Ford
2020-11-30 22:02 ` Rob Herring
2021-04-01 21:19   ` Adam Ford
2021-10-16 20:11     ` Adam Ford
2021-11-03 14:36       ` Adam Ford
2021-11-20 10:13         ` Shawn Guo [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=20211120101354.GA31998@dragon \
    --to=shawnguo@kernel.org \
    --cc=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.