From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
linus.walleij@stericsson.com, grant.likely@secretlab.ca,
cjb@laptop.org, sameo@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/22] regulator: Change db8500-prcmu match names to reflect Device Tree
Date: Mon, 11 Jun 2012 22:27:53 +0800 [thread overview]
Message-ID: <20120611142752.GS11439@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FD5FBAF.1060002@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Mon, Jun 11, 2012 at 03:07:43PM +0100, Lee Jones wrote:
> >>Well, I guess I'll end up dulplicating the commits :/
> >Duplicating them?
> Ah, you mean that you've already sent them to -next?
Yeah, I've already got them on a branch I don't really want to rebase.
> That's no problem though. Won't Git just sling them out at pull-time?
It'll merge out fine, it's just icky having the same thing appear twice
in history. Not the end of the world.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-11 14:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1338353260-10097-1-git-send-email-lee.jones@linaro.org>
2012-05-30 4:47 ` [PATCH 08/22] regulator: Change ab8500 match names to reflect Device Tree Lee Jones
2012-05-30 6:58 ` Linus Walleij
2012-05-30 10:03 ` Mark Brown
[not found] ` <CAF2Aj3gZMF9ev9B46rBM+aY-srwthef09ad2CWfuXXFHmqqAjA@mail.gmail.com>
2012-05-30 12:15 ` Mark Brown
2012-05-30 15:01 ` Lee Jones
2012-05-30 15:11 ` Mark Brown
2012-05-30 15:22 ` Lee Jones
2012-05-30 16:41 ` Mark Brown
2012-05-31 0:42 ` Lee Jones
2012-06-01 4:36 ` Lee Jones
2012-06-01 8:48 ` Mark Brown
2012-06-05 10:31 ` Lee Jones
2012-06-05 10:38 ` Mark Brown
2012-06-11 10:27 ` Lee Jones
2012-06-11 10:36 ` Mark Brown
2012-06-11 11:28 ` Lee Jones
2012-06-11 11:42 ` Mark Brown
2012-05-31 1:40 ` Linus Walleij
2012-06-01 14:32 ` Mark Brown
2012-05-30 4:47 ` [PATCH 09/22] regulator: Change db8500-prcmu " Lee Jones
2012-05-30 7:00 ` Linus Walleij
2012-06-05 10:24 ` Lee Jones
2012-06-05 10:29 ` Mark Brown
2012-06-05 10:34 ` Lee Jones
2012-06-05 10:42 ` Mark Brown
2012-06-11 11:21 ` Lee Jones
2012-06-11 12:08 ` Mark Brown
2012-06-11 13:34 ` Lee Jones
2012-06-11 14:07 ` Lee Jones
2012-06-11 14:27 ` Mark Brown [this message]
2012-06-11 14:50 ` Lee Jones
2012-06-11 15:15 ` Mark Brown
2012-06-11 15:18 ` Lee Jones
2012-06-11 15:39 ` Mark Brown
2012-06-11 15:59 ` Lee Jones
2012-06-11 16:09 ` Mark Brown
2012-05-30 4:47 ` [PATCH 16/22] mfd: ab8500-gpadc: Enable IRQF_ONESHOT when requesting a threaded IRQ Lee Jones
2012-05-30 7:10 ` Linus Walleij
2012-06-29 13:21 ` Samuel Ortiz
2012-05-30 4:47 ` [PATCH 18/22] mfd: Remove redundant Kconfig entry Lee Jones
2012-05-30 7:15 ` Linus Walleij
2012-05-30 7:37 ` Lee Jones
2012-05-30 7:43 ` Linus Walleij
2012-06-29 13:24 ` Samuel Ortiz
2012-05-30 4:47 ` [PATCH 22/22] mfd: Enable DT probing of the DB8500 PRCMU Lee Jones
2012-05-30 7:19 ` Linus Walleij
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=20120611142752.GS11439@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.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 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).