From: Jean Delvare <jdelvare@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Enno Luebbers <enno.luebbers@intel.com>,
gwendal@chromium.org, Banajit Goswami <bgoswami@codeaurora.org>,
Heiko Stuebner <heiko@sntech.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-doc@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Mark Brown <broonie@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Juergen Fitschen <jfi@ssv-embedded.de>,
alsa-devel@alsa-project.org, Stefan Agner <stefan@agner.ch>,
Sebastian Reichel <sre@kernel.org>,
Jilayne Lovejoy <opensource@jilayne.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Guido Kiener <guido@kiener-muenchen.de>,
linux-i2c@vger.kernel.org,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Dong Aisheng <aisheng.dong@nxp.com>,
Guenter Roeck <groeck@chromium.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ravi Chandra Sadineni <ravisad>
Subject: Re: [PATCH 00/10] Move part of cros-ec out of MFD subsystem
Date: Thu, 6 Jun 2019 08:28:18 +0200 [thread overview]
Message-ID: <20190606082818.424c783c@endymion> (raw)
In-Reply-To: <0a5acc33-40f9-9235-505e-92f534ddc7e2@infradead.org>
Hi Randy,
On Tue, 4 Jun 2019 15:18:43 -0700, Randy Dunlap wrote:
> Was there a patch 02/10? I didn't see it.
> What mailing list(s) was it sent to?
There was, but I can't find it in list archives, probably because there
were too many recipients.
I'll bounce the copy I received to you.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2019-06-06 6:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 15:20 [PATCH 00/10] Move part of cros-ec out of MFD subsystem Enric Balletbo i Serra
2019-06-04 15:20 ` [PATCH 02/10] mfd / platform: cros_ec: Move cros-ec core driver out from MFD Enric Balletbo i Serra
2019-06-05 8:31 ` Thierry Reding
2019-06-05 10:02 ` Mark Brown
2019-06-05 14:19 ` Wolfram Sang
2019-06-05 14:23 ` Neil Armstrong
2019-06-05 16:25 ` Alexandre Belloni
2019-06-08 12:02 ` Jonathan Cameron
2019-06-11 9:20 ` Benjamin Tissoires
2019-06-11 17:09 ` Dmitry Torokhov
2019-06-11 19:52 ` Sebastian Reichel
2019-06-04 15:20 ` [PATCH 06/10] mfd / platform: cros_ec: Reorganize platform and mfd includes Enric Balletbo i Serra
2019-06-05 10:02 ` Mark Brown
2019-06-05 14:20 ` Wolfram Sang
2019-06-05 14:26 ` Neil Armstrong
2019-06-05 16:26 ` Alexandre Belloni
2019-06-08 12:05 ` Jonathan Cameron
2019-06-11 9:20 ` Benjamin Tissoires
2019-06-11 17:10 ` Dmitry Torokhov
2019-06-11 19:54 ` Sebastian Reichel
2019-06-04 16:07 ` [PATCH 00/10] Move part of cros-ec out of MFD subsystem Andy Shevchenko
2019-06-04 22:18 ` Randy Dunlap
2019-06-06 6:28 ` Jean Delvare [this message]
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=20190606082818.424c783c@endymion \
--to=jdelvare@suse.de \
--cc=aisheng.dong@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=enno.luebbers@intel.com \
--cc=groeck@chromium.org \
--cc=guido@kiener-muenchen.de \
--cc=gwendal@chromium.org \
--cc=heiko@sntech.de \
--cc=jfi@ssv-embedded.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=opensource@jilayne.com \
--cc=pmeerw@pmeerw.net \
--cc=rdunlap@infradead.org \
--cc=sre@kernel.org \
--cc=stefan@agner.ch \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).