From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: James Hogan <jhogan@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/8] MIPS: mscc: add ocelot dtsi
Date: Tue, 27 Feb 2018 16:47:54 +0100 [thread overview]
Message-ID: <20180227154754.GA15333@piout.net> (raw)
In-Reply-To: <20180214165743.GD3986@saruman>
On 14/02/2018 at 16:57:43 +0000, James Hogan wrote:
> On Tue, Jan 16, 2018 at 11:12:37AM +0100, Alexandre Belloni wrote:
> > Add a device tree include file for the Microsemi Ocelot SoC.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> May I suggest Cc'ing the DT folk on this patch.
>
I can do that but I think that while they care about the bindings
themselves, they usually don't review the device trees.
So I wouldn't expect any review from Rob on such a patch, especially
since he reviewed the bndings.
> > diff --git a/arch/mips/boot/dts/mscc/Makefile b/arch/mips/boot/dts/mscc/Makefile
> > new file mode 100644
> > index 000000000000..f0a155a74e02
> > --- /dev/null
> > +++ b/arch/mips/boot/dts/mscc/Makefile
> > @@ -0,0 +1,4 @@
> > +obj-y += $(patsubst %.dtb, %.dtb.o, $(dtb-y))
> > +
> > +# Force kbuild to make empty built-in.o if necessary
> > +obj- += dummy.o
>
> I don't think you need this since f7adc3124da0 ("kbuild: create
> built-in.o automatically if parent directory wants it"). It was removed
> from other places in bf070bb0e6c6 ("kbuild: remove all dummy assignments
> to obj-").
>
> Cheers
> James
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-27 15:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 10:12 [PATCH v3 0/8] MIPS: add support for the Microsemi MIPS SoCs Alexandre Belloni
2018-01-16 10:12 ` [PATCH v3 1/8] dt-bindings: mips: Add bindings for Microsemi SoCs Alexandre Belloni
2018-01-19 19:23 ` Rob Herring
2018-02-14 16:38 ` James Hogan
2018-01-16 10:12 ` [PATCH v3 2/8] dt-bindings: power: reset: Document ocelot-reset binding Alexandre Belloni
2018-01-20 0:34 ` Rob Herring
2018-02-08 22:32 ` Sebastian Reichel
2018-01-16 10:12 ` [PATCH v3 3/8] power: reset: Add a driver for the Microsemi Ocelot reset Alexandre Belloni
2018-02-08 22:32 ` Sebastian Reichel
2018-01-16 10:12 ` [PATCH v3 4/8] MIPS: mscc: Add initial support for Microsemi MIPS SoCs Alexandre Belloni
2018-02-14 16:51 ` James Hogan
2018-02-14 21:38 ` Philippe Ombredanne
2018-01-16 10:12 ` [PATCH v3 5/8] MIPS: mscc: add ocelot dtsi Alexandre Belloni
2018-02-14 16:57 ` James Hogan
2018-02-27 15:47 ` Alexandre Belloni [this message]
2018-02-27 21:01 ` Jonas Gorski
2018-02-28 13:14 ` Alexandre Belloni
2018-01-16 10:12 ` [PATCH v3 6/8] MIPS: mscc: add ocelot PCB123 device tree Alexandre Belloni
2018-02-14 17:00 ` James Hogan
2018-02-27 15:54 ` Alexandre Belloni
2018-02-27 15:57 ` James Hogan
2018-01-16 10:12 ` [PATCH v3 7/8] MIPS: defconfigs: add a defconfig for Microsemi SoCs Alexandre Belloni
2018-02-14 17:03 ` James Hogan
2018-02-27 16:15 ` Alexandre Belloni
2018-02-27 16:23 ` James Hogan
2018-01-16 10:12 ` [PATCH v3 8/8] MAINTAINERS: Add entry for Microsemi MIPS SoCs Alexandre Belloni
2018-02-14 17:05 ` James Hogan
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=20180227154754.GA15333@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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