From: Lee Jones <lee.jones@linaro.org>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Joel Stanley <joel@jms.id.au>,
Alexandre Courbot <gnurou@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jeremy Kerr <jk@ozlabs.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/8] syscon: dt-bindings: Add documentation for Aspeed system control units
Date: Thu, 8 Sep 2016 08:01:31 +0100 [thread overview]
Message-ID: <20160908070131.GG4921@dell> (raw)
In-Reply-To: <1473296480.10397.5.camel@aj.id.au>
On Thu, 08 Sep 2016, Andrew Jeffery wrote:
> On Wed, 2016-09-07 at 16:38 +0200, Linus Walleij wrote:
> > On Tue, Aug 30, 2016 at 9:54 AM, Andrew Jeffery <andrew@aj.id.au> wrote:
> >
> > >
> > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
> > > Acked-by: Rob Herring <robh@kernel.org>
> > > Acked-by: Joel Stanley <joel@jms.id.au>
> > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > I guess the MFD maintainer (Lee Jones) should merge this?
> >
> > Why is he not on CC?
>
> I used get_maintainer.pl on the series to construct the CC, but Lee
> wasn't listed in the output. I'll poke further at MAINTAINERs in the
> future to make sure I have coverage for affected subsystems.
Good point. Will fix.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-09-08 6:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 7:54 [PATCH v3 0/8] aspeed: Add pinctrl and gpio drivers Andrew Jeffery
2016-08-30 7:54 ` [PATCH v3 1/8] MAINTAINERS: Add glob for Aspeed devicetree bindings Andrew Jeffery
2016-09-07 14:37 ` Linus Walleij
2016-09-07 14:42 ` Arnd Bergmann
2016-08-30 7:54 ` [PATCH v3 2/8] syscon: dt-bindings: Add documentation for Aspeed system control units Andrew Jeffery
2016-09-07 14:38 ` Linus Walleij
2016-09-07 16:30 ` Lee Jones
2016-09-08 1:03 ` Andrew Jeffery
2016-09-08 1:01 ` Andrew Jeffery
2016-09-08 7:01 ` Lee Jones [this message]
2016-08-30 7:54 ` [PATCH v3 3/8] pinctrl: dt-bindings: Add documentation for Aspeed pin controllers Andrew Jeffery
2016-09-07 14:40 ` Linus Walleij
2016-08-30 7:54 ` [PATCH v3 4/8] gpio: dt-bindings: Add documentation for Aspeed GPIO controllers Andrew Jeffery
2016-09-02 15:00 ` Rob Herring
2016-09-07 14:43 ` Linus Walleij
2016-09-08 1:19 ` Andrew Jeffery
2016-08-30 7:54 ` [PATCH v3 5/8] pinctrl: Add core support for Aspeed SoCs Andrew Jeffery
2016-09-07 14:50 ` Linus Walleij
2016-09-08 3:58 ` Andrew Jeffery
2016-08-30 7:54 ` [PATCH v3 6/8] pinctrl: Add pinctrl-aspeed-g4 driver Andrew Jeffery
2016-09-07 14:53 ` Linus Walleij
2016-08-30 7:54 ` [PATCH v3 7/8] pinctrl: Add pinctrl-aspeed-g5 driver Andrew Jeffery
2016-09-07 14:54 ` Linus Walleij
2016-08-30 7:54 ` [PATCH v3 8/8] gpio: Add Aspeed driver Andrew Jeffery
2016-09-07 14:59 ` Linus Walleij
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=20160908070131.GG4921@dell \
--to=lee.jones@linaro.org \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).