All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M, Krishnamoorthi" <krishnamoorthi.m@amd.com>
To: YH Chung <yh_chung@aspeedtech.com>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"akshata.mukundshetty@amd.com" <akshata.mukundshetty@amd.com>,
	"bleung@chromium.org" <bleung@chromium.org>,
	"groeck@chromium.org" <groeck@chromium.org>,
	"chrome-platform@lists.linux.dev"
	<chrome-platform@lists.linux.dev>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	YC Hsieh <yc_hsieh@aspeedtech.com>,
	Maciej Lawniczak <maciej.lawniczak@intel.com>,
	Ryan Chen <ryan_chen@aspeedtech.com>
Subject: Re: [RFC PATCH 0/4] espi: introduce eSPI bus framework
Date: Thu, 20 Aug 2026 19:24:23 +0530	[thread overview]
Message-ID: <c690ee50-d044-4bfb-b19e-0960e40335a5@amd.com> (raw)
In-Reply-To: <KL1PR0601MB427610EA42683AA298B53C4390A42@KL1PR0601MB4276.apcprd06.prod.outlook.com>

Hi Chung,

On 8/20/2026 11:55 AM, YH Chung wrote:
> Hi Krishna,
> 
> Thanks. I'd like to introduce Yu-Che Hsieh, who will be taking over the
> eSPI ownership and upstreaming work from the ASPEED's side.
> 
> As I'll be leaving ASPEED next week, Yu-Che will continue the discussion
> on the eSPI subsystem design. I've already briefed him on the current
> discussion and design considerations.
> 
> Yu-Che, please take it from here for the upcoming discussion and revisions.
> 
> Thanks again for all the discussion and guidance.

Thank you Chung for the valuable design inputs and best wishes for your 
next role.

Yu-Che, please share your thoughts or comments on the eSPI framework 
design whenever you are ready.

Thanks,
Krishna

> 
> Best regards,
> Yun Hsuan.


  reply	other threads:[~2026-08-20 13:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:52 [RFC PATCH 0/4] espi: introduce eSPI bus framework Krishnamoorthi M
2026-08-04 11:52 ` [RFC PATCH 1/4] espi: add core " Krishnamoorthi M
2026-08-06 13:31   ` Uwe Kleine-König
2026-08-12 12:50     ` M, Krishnamoorthi
2026-08-12 16:30       ` Uwe Kleine-König
2026-08-17 10:57         ` M, Krishnamoorthi
2026-08-04 11:52 ` [RFC PATCH 2/4] espi: add slave device model and event notification Krishnamoorthi M
2026-08-04 11:52 ` [RFC PATCH 3/4] Documentation: espi: add subsystem overview and MAINTAINERS entry Krishnamoorthi M
2026-08-04 16:39   ` Randy Dunlap
2026-08-04 19:14     ` M, Krishnamoorthi
2026-08-04 11:52 ` [RFC PATCH 4/4] espi: amd: add AMD eSPI controller driver Krishnamoorthi M
2026-08-04 12:18 ` [RFC PATCH 0/4] espi: introduce eSPI bus framework Greg KH
2026-08-04 13:26   ` Greg KH
2026-08-05  0:42   ` Andrew Jeffery
2026-08-05 18:35     ` M, Krishnamoorthi
2026-08-10  6:13       ` YH Chung
2026-08-18 13:25         ` M, Krishnamoorthi
2026-08-20  6:25           ` YH Chung
2026-08-20 13:54             ` M, Krishnamoorthi [this message]
2026-08-05 10:14   ` M, Krishnamoorthi

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=c690ee50-d044-4bfb-b19e-0960e40335a5@amd.com \
    --to=krishnamoorthi.m@amd.com \
    --cc=akshata.mukundshetty@amd.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=bleung@chromium.org \
    --cc=broonie@kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=maciej.lawniczak@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ryan_chen@aspeedtech.com \
    --cc=skhan@linuxfoundation.org \
    --cc=yc_hsieh@aspeedtech.com \
    --cc=yh_chung@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.