From: Maxime Ripard <mripard@kernel.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
linux-media@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
lakml <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] media: dt-bindings: media: Fixup Allwinner A10 CSI binding
Date: Mon, 7 Oct 2019 12:48:35 +0200 [thread overview]
Message-ID: <20191007104835.v6iqpoolqtajryik@gilmour> (raw)
In-Reply-To: <CAP245DXT=HL+m-LqoC25EBnOaPmF1pUW0fEZp6EZB-MdgOJoWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
On Mon, Oct 07, 2019 at 03:45:29PM +0530, Amit Kucheria wrote:
> On Mon, Oct 7, 2019 at 3:35 PM Maxime Ripard <mripard@kernel.org> wrote:
> >
> > On Sat, Oct 05, 2019 at 04:15:57PM +0530, Amit Kucheria wrote:
> > > On Thu, Oct 3, 2019 at 5:22 PM Maxime Ripard <mripard@kernel.org> wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Thu, Oct 03, 2019 at 04:52:24PM +0530, Amit Kucheria wrote:
> > > > > This new binding fails dt_binding_check due to a typo. Fix it up.
> > > > >
> > > > > linux.git/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-csi.yaml: $id: path/filename 'arm/allwinner,sun4i-a10-csi.yaml' doesn't match actual filename
> > > > > linux.git/Documentation/devicetree/bindings/Makefile:12: recipe for target 'Documentation/devicetree/bindings/media/allwinner,sun4i-a10-csi.example.dts' failed
> > > > > make[2]: *** [Documentation/devicetree/bindings/media/allwinner,sun4i-a10-csi.example.dts] Error 1
> > > > > make[2]: *** Waiting for unfinished jobs....
> > > > > linux.git/Makefile:1284: recipe for target 'dt_binding_check' failed
> > > > > make[1]: *** [dt_binding_check] Error 2
> > > > >
> > > > > Fixes: c5e8f4ccd7750 ("media: dt-bindings: media: Add Allwinner A10 CSI binding")
> > > > > Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> > > >
> > > > Thanks for your patch.
> > > >
> > > > It has already been submitted though:
> > > > https://lore.kernel.org/linux-arm-kernel/1568808060-17516-1-git-send-email-pragnesh.patel@sifive.com/
> > > >
> > > > I'm not sure why it hasn't been applied yet though :/
> > >
> > > Perhaps a Fixes tag will allow more attention to it?
> >
> > I've added a fixes tag and merged it through the sunxi tree.
> >
> > Sorry for the time it took, and thanks for sending that fix!
>
> Will it get merged for -rc2?
-rc2 was released yesterday, so we're a bit late for that, but it's
going to be in next tomorrow.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-10-07 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 11:22 [PATCH] media: dt-bindings: media: Fixup Allwinner A10 CSI binding Amit Kucheria
2019-10-03 11:51 ` Maxime Ripard
2019-10-05 10:45 ` Amit Kucheria
2019-10-07 10:05 ` Maxime Ripard
2019-10-07 10:15 ` Amit Kucheria
2019-10-07 10:48 ` Maxime Ripard [this message]
2019-10-22 16:17 ` Rob Herring
2019-10-23 6:51 ` Maxime Ripard
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=20191007104835.v6iqpoolqtajryik@gilmour \
--to=mripard@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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).