From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] mmc: mmci: Move ios_handler functionality into the driver
Date: Wed, 23 Jan 2013 10:13:49 +0000 [thread overview]
Message-ID: <20130123101349.GH15873@gmail.com> (raw)
In-Reply-To: <20130122105608.GP6857@gmail.com>
On Tue, 22 Jan 2013, Lee Jones wrote:
> On Tue, 22 Jan 2013, Russell King - ARM Linux wrote:
>
> > On Tue, Jan 22, 2013 at 10:20:10AM +0000, Lee Jones wrote:
> > > On Tue, 22 Jan 2013, Russell King - ARM Linux wrote:
> > >
> > > > On Tue, Jan 22, 2013 at 10:53:42AM +0100, Linus Walleij wrote:
> > > > > On Tue, Jan 22, 2013 at 10:00 AM, Lee Jones <lee.jones@linaro.org> wrote:
> > > > >
> > > > > >> From: Lee Jones <lee.jones@linaro.org>
> > > > > >>
> > > > > >> There are currently two instances of the ios_handler being used.
> > > > > >> Both of which mearly toy with some regulator settings. Now there
> > > > > >> is a GPIO regulator API, we can use that instead, and lessen the
> > > > > >> per platform burden. By doing this, we also become more Device
> > > > > >> Tree compatible.
> > > > > >
> > > > > > Russell,
> > > > > >
> > > > > > Why is this patch in your tree with Ulf as the Author?
> > > > >
> > > > > This is because of the way Russell's patch tracker works, it sets
> > > > > Author: to the name of the person using the patch tracker and
> > > > > discards the From: field in the beginning of the patch which
> > > > > git am will conversely respect.
> > > >
> > > > Actually, the reverse. It does now respect the From: line, but the
> > > > From: line will be ignored for all notifications about the patch
> > > > because the patch system was never built to parse the actual comments
> > > > when sending out the email notifications.
> > >
> > > So what do I have to do to reaffirm myself as the author?
> >
> > I'd need to recommit the patch with the right information, which isn't
> > that easy to do.
>
> Are you saying that you won't do it? :)
>
> Is there anything I can do to make the process easier?
Thinking about this a little more. Is it easier to remove it from your
tree altogether? Only I have a small "ARM: ux500: " patch-set which
directly relies on this patch. I could take it in via ARM-SoC without
any fear of ordering issues.
The alternative is for me to wait until this hits Mainline, or for you
to take in the remainder of the patch-set via your patch tracker. The
first option would be my preference.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-01-23 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:30 [PATCH 0/2] mmc: mmci: Update regulator support Ulf Hansson
2012-12-14 14:30 ` [PATCH 1/2] mmc: mmci: Convert to use mmc_regulator_get_supply Ulf Hansson
2012-12-14 14:30 ` [PATCH V2 2/2] mmc: mmci: Move ios_handler functionality into the driver Ulf Hansson
2012-12-14 15:10 ` Russell King - ARM Linux
2012-12-14 15:52 ` Ulf Hansson
2012-12-14 16:33 ` Lee Jones
2013-01-22 9:00 ` Lee Jones
2013-01-22 9:53 ` Linus Walleij
2013-01-22 10:06 ` Russell King - ARM Linux
2013-01-22 10:11 ` Linus Walleij
2013-01-22 10:20 ` Lee Jones
2013-01-22 10:37 ` Russell King - ARM Linux
2013-01-22 10:56 ` Lee Jones
2013-01-23 10:13 ` Lee Jones [this message]
2013-01-23 10:17 ` Russell King - ARM Linux
2013-01-23 11:18 ` Lee Jones
2013-01-24 12:55 ` Ulf Hansson
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=20130123101349.GH15873@gmail.com \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).