From: Pavel Machek <pavel@ucw.cz>
To: "Hawkins, Nick" <nick.hawkins@hpe.com>
Cc: "Verdun, Jean-Marie" <verdun@hpe.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v7 1/8] ARM: hpe: Introduce the HPE GXP architecture
Date: Wed, 1 Jun 2022 22:57:23 +0200 [thread overview]
Message-ID: <20220601205723.GA10927@duo.ucw.cz> (raw)
In-Reply-To: <DM4PR84MB19274FE59381E204CBCFE55888DF9@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Wed 2022-06-01 14:14:33, Hawkins, Nick wrote:
> > > From: Nick Hawkins <nick.hawkins@hpe.com>
> > >
> > > The GXP is the HPE BMC SoC that is used in the majority of current
> > > generation HPE servers. Traditionally the asic will last multiple
> > > generations of server before being replaced.
> > >
> > > Info about SoC:
>
> > Normally, 1/7 goes into the same thread as 0/7 mail.
>
> Hello Pavel,
>
> Thank you for the feedback. I believe the code is already in the process of being merged upstream in version v8. For future reference can you elaborate on what you mean?
>
You used separate email threads for 0/7 and the rest of the
patches. Normally, they should go to single email thread.
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-06-01 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 19:13 nick.hawkins
2022-05-06 19:13 ` [PATCH v7 2/8] ARM: configs: multi_v7_defconfig: Add HPE GXP ARCH nick.hawkins
2022-05-06 19:13 ` [PATCH v7 3/8] watchdog: hpe-wdt: Introduce HPE GXP Watchdog nick.hawkins
2022-05-10 19:48 ` Guenter Roeck
2022-05-10 23:56 ` Hawkins, Nick
2022-05-06 19:13 ` [PATCH v7 4/8] clocksource/drivers/timer-gxp: Add HPE GXP Timer nick.hawkins
2022-05-06 19:13 ` [PATCH v7 5/8] dt-bindings: timer: hpe,gxp-timer: Add HPE GXP Timer and Watchdog nick.hawkins
2022-05-06 19:13 ` [PATCH v7 6/8] dt-bindings: arm: hpe: add GXP Support nick.hawkins
2022-05-06 19:13 ` [PATCH v7 7/8] ARM: dts: Introduce HPE GXP Device tree nick.hawkins
2022-05-07 16:02 ` Krzysztof Kozlowski
2022-05-06 19:13 ` [PATCH v7 8/8] MAINTAINERS: Introduce HPE GXP Architecture nick.hawkins
2022-05-30 7:06 ` [PATCH v7 1/8] ARM: hpe: Introduce the HPE GXP architecture Pavel Machek
2022-06-01 14:14 ` Hawkins, Nick
2022-06-01 20:57 ` Pavel Machek [this message]
2022-06-02 6:51 ` Arnd Bergmann
2022-06-02 14:37 ` Hawkins, Nick
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=20220601205723.GA10927@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nick.hawkins@hpe.com \
--cc=verdun@hpe.com \
/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
all inboxes | Powered by JetHome®