From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MFD for v4.4
Date: Fri, 6 Nov 2015 21:19:00 +0000 [thread overview]
Message-ID: <20151106211900.GK18409@sirena.org.uk> (raw)
In-Reply-To: <CA+55aFxcSz3KxCEMmAmK2s1r50PQx+gBMfXF2m0ZS0+6qVNR2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Fri, Nov 06, 2015 at 10:37:23AM -0800, Linus Torvalds wrote:
> On Fri, Nov 6, 2015 at 12:04 AM, Lee Jones <lee.jones@linaro.org> wrote:
> > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-for-linus-4.4
> So I had some of the patches you listed from before throughthe regmap
> merge etc. So you and Mark Brown merged some of the same branches.
> That all looks fine, I just want to confirm that it was intentional
> and you were both aware of this, and it happened because you both
> wanted some of the infrastructure?
Yup, some of the MFD drivers wanted new regmap functionality so Lee
pulled in some branches I tagged. At least for my stuff in general if
someone's merged something from a tag I signed I was expecting that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-11-06 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:04 Lee Jones
2015-11-06 18:37 ` Linus Torvalds
2015-11-06 21:19 ` Mark Brown [this message]
2015-11-06 18:46 ` Linus Torvalds
2015-11-07 12:42 ` Lee Jones
2015-11-07 19:29 ` Linus Torvalds
2015-11-09 13:31 ` Sudip Mukherjee
2015-11-10 9:38 ` Lee Jones
2016-01-14 9:19 Lee Jones
2016-01-14 14:11 ` Stephen Rothwell
2016-01-14 15:32 ` Lee Jones
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=20151106211900.GK18409@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®