devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Fabrice Gasnier <fabrice.gasnier@st.com>,
	robh+dt@kernel.org, alexandre.torgue@st.com,
	mark.rutland@arm.com, mcoquelin.stm32@gmail.com, lars@metafoo.de,
	knaack.h@gmx.de, pmeerw@pmeerw.net, olivier.moysan@st.com,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: adc: stm32-adc: fix id relative path
Date: Sat, 4 Apr 2020 15:21:32 +0100	[thread overview]
Message-ID: <20200404152132.62382a66@archlinux> (raw)
In-Reply-To: <20200330232115.GA17380@bogus>

On Mon, 30 Mar 2020 17:21:15 -0600
Rob Herring <robh@kernel.org> wrote:

> On Thu, 19 Mar 2020 19:18:27 +0100, Fabrice Gasnier wrote:
> > Fix id relative path that shouldn't contain 'bindings', as pointed out
> > when submitting st,stm32-dac bindings conversion to json-schema [1].
> > [1] https://patchwork.ozlabs.org/patch/1257568/
> > 
> > Fixes: a8cf1723c4b7 ("dt-bindings: iio: adc: stm32-adc: convert bindings to json-schema")
> > 
> > Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
> > ---
> >  Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >   
> 
> Reviewed-by: Rob Herring <robh@kernel.org>

Applied to the fixes-togreg branch of iio.git
I will hopefully send a pull request for this around the time
the merge window closes.

Thanks,

Jonathan.

      reply	other threads:[~2020-04-04 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 18:18 [PATCH] dt-bindings: iio: adc: stm32-adc: fix id relative path Fabrice Gasnier
2020-03-30 23:21 ` Rob Herring
2020-04-04 14:21   ` Jonathan Cameron [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=20200404152132.62382a66@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrice.gasnier@st.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=olivier.moysan@st.com \
    --cc=pmeerw@pmeerw.net \
    --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 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).