[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200128120344.GB4689@sirena.org.uk>
Date: Tue, 28 Jan 2020 12:03:44 +0000
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Liam Girdwood <lgirdwood@...il.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
Axel Lin <axel.lin@...ics.com>
Subject: Re: linux-next: manual merge of the mfd tree with the
regulator-fixes tree
On Tue, Jan 28, 2020 at 07:39:01AM +0000, Lee Jones wrote:
> A pull-request was sent out to avoid this.
> If Mark pulls it, this should just go away.
I didn't pull it in and Linus already took the regulator changes for
this cycle - I tend to only actually merge the pull requests if there's
any issue so that I minimize the extra bits in my pull requests and this
didn't come up in -next until just now. Sorry about that, it does look
simple enough though.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists