From: Mark Brown <broonie@kernel.org>
To: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Joel Stanley <joel@jms.id.au>,
gregkh <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI
Date: Wed, 3 Jan 2018 14:32:26 +0000 [thread overview]
Message-ID: <20180103143226.GI5603@sirena.org.uk> (raw)
In-Reply-To: <004d3017-5477-ec42-c78a-aba0ca0621bc@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote:
> Should send to like this ? Because I add patch for Aspeed chip:
> ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c
> Joel Stanley <joel@jms.id.au> (maintainer:ARM/ASPEED MACHINE SUPPORT)
> Arnd Bergmann <arnd@arndb.de> (supporter:CHAR and MISC DRIVERS)
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:CHAR and MISC
> DRIVERS)
> linux-kernel@vger.kernel.org (open list)
So it's not actually doing anything at all with the SPI subsystem? I
lacked any context for the discussion having been copied in part way
through. If it is a SPI controller it ought to have been in
drivers/spi.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-03 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 1:53 [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI Haiyue Wang
2017-12-30 23:10 ` Arnd Bergmann
2017-12-31 17:04 ` Wang, Haiyue
2017-12-31 17:08 ` Wang, Haiyue
2018-01-02 15:13 ` Arnd Bergmann
2018-01-02 15:36 ` Wang, Haiyue
2018-01-02 16:23 ` Arnd Bergmann
2018-01-03 2:21 ` Wang, Haiyue
2018-01-03 15:17 ` Arnd Bergmann
2018-01-03 16:43 ` Wang, Haiyue
2018-01-03 17:08 ` Wang, Haiyue
2018-01-04 0:11 ` Wang, Haiyue
2018-01-03 11:38 ` Mark Brown
2018-01-03 14:28 ` Wang, Haiyue
2018-01-03 14:32 ` Mark Brown [this message]
2018-01-03 14:34 ` Wang, Haiyue
2018-01-03 15:05 ` Arnd Bergmann
2018-01-03 16:48 ` Wang, Haiyue
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=20180103143226.GI5603@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=haiyue.wang@linux.intel.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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