public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Lee Jones <lee.jones@linaro•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Liam Girdwood <lgirdwood@gmail•com>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Matti Vaittinen <matti.vaittinen@fi•rohmeurope.com>,
	Axel Lin <axel.lin@ingics•com>
Subject: Re: linux-next: manual merge of the mfd tree with the regulator-fixes tree
Date: Tue, 28 Jan 2020 12:03:44 +0000	[thread overview]
Message-ID: <20200128120344.GB4689@sirena.org.uk> (raw)
In-Reply-To: <20200128073901.GB3548@dell>

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-01-28 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  1:02 linux-next: manual merge of the mfd tree with the regulator-fixes tree Stephen Rothwell
2020-01-28  7:39 ` Lee Jones
2020-01-28 12:03   ` Mark Brown [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=20200128120344.GB4689@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=axel.lin@ingics$(echo .)com \
    --cc=lee.jones@linaro$(echo .)org \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=matti.vaittinen@fi$(echo .)rohmeurope.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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