[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150919092145.GG3218@x1>
Date: Sat, 19 Sep 2015 10:21:45 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-crypto@...r.kernel.org,
Peter Korsgaard <peter@...sgaard.com>,
Fabio Estevam <festevam@...il.com>,
Kieran Bingham <kieranbingham@...il.com>,
"kernel@...inux.com" <kernel@...inux.com>
Subject: Re: [PATCH v2 0/7] hwrng: Add support for STMicroelectronics' RNG IP
On Sat, 19 Sep 2015, Herbert Xu wrote:
> On Fri, Sep 18, 2015 at 04:51:12PM +0100, Lee Jones wrote:
> >
> > I think it's okay for you to take all but patch 6.
> >
> > Patch 6 is an ARM patch and needs to go into ARM SoC via
> > STMicroelectronics STi tree.
>
> In future please don't send me patches that you don't want me to
> merge in the series.
That's not how it works. It's helpful, more often than not, to submit
the entire set to each maintainer concerned so they can keep up with
the general conversation. By only sending specific patches to
maintainers you essentially blinker them to the bigger picture.
As a maintainer you should _know_ that you can't apply patches from
other subsystems without appropriate Acks. I'm sure you'd take
exception to another maintainer who started accepting patches for
subsystems you are responsible for. This works both ways.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists