From: Peter Maydell <peter.maydell@linaro.org>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: "Andrew Jeffery" <andrew@aj.id.au>,
qemu-arm <qemu-arm@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Joel Stanley" <joel@jms.id.au>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v3 0/4] arm/aspeed: Watchdog and SDRAM fixes
Date: Tue, 19 Nov 2019 13:44:10 +0000 [thread overview]
Message-ID: <CAFEAcA82Nf=2tEyfgX5=_pi19C7PC8YODX2XCC=NafT6SUP38Q@mail.gmail.com> (raw)
In-Reply-To: <3dbfb0eb-4ecb-35b4-9c8d-dec3fd6f083f@kaod.org>
On Thu, 14 Nov 2019 at 14:17, Cédric Le Goater <clg@kaod.org> wrote:
> We are preparing, and reviewing, the initial 5.0 patchset
> which will contain the I2C pool buffer model plus the fixes
> Joel and I sent.
OK. I currently have in my 'maybe I should do something with this'
list these patchsets:
aspeed/i2c: Add support for pool and DMA transfer modes
arm/aspeed: Watchdog and SDRAM fixes
aspeed: AST2600 SMC fixes and tacoma-bmc machine
aspeed: rework inter model link properties
(I had a quick scan through and there's nothing in any of
them that looked odd to me, though I haven't done a detailed
review). Should I just assume that you'll send out a rollup
patchset with all of those once 5.0 is out ? Alternatively
I could apply them to the target-arm.for-5.0 branch I'm
currently keeping, which will become the first target-arm
pullreq once 5.0 reopens, if you prefer (and if you've
got on-list reviewed-by tags for them all).
thanks
-- PMM
next prev parent reply other threads:[~2019-11-19 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 22:12 [PATCH v3 0/4] arm/aspeed: Watchdog and SDRAM fixes Joel Stanley
2019-11-13 22:12 ` [PATCH v3 1/4] aspeed/sdmc: Make ast2600 default 1G Joel Stanley
2019-11-13 22:12 ` [PATCH v3 2/4] aspeed/scu: Fix W1C behavior Joel Stanley
2019-11-13 22:13 ` [PATCH v3 3/4] watchdog/aspeed: Improve watchdog timeout message Joel Stanley
2019-11-13 22:13 ` [PATCH v3 4/4] watchdog/aspeed: Fix AST2600 frequency behaviour Joel Stanley
2019-11-14 14:04 ` [PATCH v3 0/4] arm/aspeed: Watchdog and SDRAM fixes Peter Maydell
2019-11-14 14:16 ` Cédric Le Goater
2019-11-19 13:44 ` Peter Maydell [this message]
2019-11-19 14:05 ` Cédric Le Goater
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='CAFEAcA82Nf=2tEyfgX5=_pi19C7PC8YODX2XCC=NafT6SUP38Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).