From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, Xu Yilun <yilun.xu@intel.com>,
hao.wu@intel.com, lgoncalv@redhat.com,
matthew.gerlach@linux.intel.com, trix@redhat.com,
russell.h.weight@intel.com
Subject: Re: [PATCH v4 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support
Date: Thu, 27 Aug 2020 13:27:22 +0100 [thread overview]
Message-ID: <20200827122722.GG1627017@dell> (raw)
In-Reply-To: <20200827122013.GB4674@sirena.org.uk>
On Thu, 27 Aug 2020, Mark Brown wrote:
> On Thu, Aug 27, 2020 at 07:56:47AM +0100, Lee Jones wrote:
> > On Wed, 26 Aug 2020, Mark Brown wrote:
>
> > > [2/2] mfd: intel-m10-bmc: add Max10 BMC chip support for Intel FPGA PAC
> > > commit: 53be8bbc2f4058d4a6bfff3dadf34164bcaafa87
>
> > Que? This is yet to be reviewed.
>
> Sorry, meant to only fetch the first patch. Dropped now.
Thanks.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2020-08-27 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 7:34 [PATCH v4 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support Xu Yilun
2020-08-19 7:34 ` [PATCH v4 1/2] regmap: add Intel SPI Slave to AVMM Bus Bridge support Xu Yilun
2020-08-19 7:34 ` [PATCH v4 2/2] mfd: intel-m10-bmc: add Max10 BMC chip support for Intel FPGA PAC Xu Yilun
2020-08-28 10:02 ` Lee Jones
2020-08-28 13:50 ` Tom Rix
2020-09-08 11:56 ` Lee Jones
2020-08-29 18:24 ` Xu Yilun
2020-09-08 12:03 ` Lee Jones
2020-09-09 6:01 ` Xu Yilun
2020-09-09 7:31 ` Lee Jones
2020-09-09 8:29 ` Xu Yilun
2020-08-26 19:16 ` [PATCH v4 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support Mark Brown
2020-08-27 6:56 ` Lee Jones
2020-08-27 12:20 ` Mark Brown
2020-08-27 12:27 ` Lee Jones [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=20200827122722.GG1627017@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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.