Messages in this thread | | | From | "Hawkins, Nick" <> | Subject | RE: [PATCH v5 01/11] aach: arm: mach-hpe: Introduce the HPE GXP architecture | Date | Mon, 25 Apr 2022 15:00:04 +0000 |
| |
-----Original Message----- From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org] Sent: Saturday, April 23, 2022 6:05 AM To: Hawkins, Nick <nick.hawkins@hpe.com>; Verdun, Jean-Marie <verdun@hpe.com>; joel@jms.id.au; arnd@arndb.de; openbmc@lists.ozlabs.org Cc: Russell King <linux@armlinux.org.uk>; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 01/11] aach: arm: mach-hpe: Introduce the HPE GXP architecture
On 21/04/2022 21:21, nick.hawkins@hpe.com wrote: > > From: Nick Hawkins <nick.hawkins@hpe.com> > > > > The GXP is the HPE BMC SoC that is used in the majority of HPE > > Generation 10 servers. Traditionally the asic will last multiple > > generations of server before being replaced. > > In gxp.c we reset the EHCI controller early to boot the asic. > > > > Info about SoC:
> Half of your patches did not make it to the lists. For example linux-arm-kernel has only 1, 2 and 10.
> Where is the rest? All your patches must be sent to linux-arm-kernel and linux-kernel. Unless the list of people To/Cc is too big (~ 10 people), entire patchset should be send to same addresses.
Apologies, I was relying on the ".scripts/get_maintainer.pl" in a script to grab and send emails. I will ensure on the next patchset that linux-arm-kernel and linux-kernel are included in all of the emails.
Thanks for the feedback,
-Nick Hawkins
| |