From: Wade Farnsworth <wfarnsworth@mvista.com>
To: Jon Loeliger <jdl@freescale.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Fix drivers/rtc/Kconfig for powerpc
Date: Thu, 07 Jun 2007 09:33:00 -0700 [thread overview]
Message-ID: <1181233980.5674.174.camel@rhino> (raw)
In-Reply-To: <1181232488.31686.19.camel@ld0161-tx32>
On Thu, 2007-06-07 at 11:08 -0500, Jon Loeliger wrote:
> On Wed, 2007-06-06 at 12:17, Wade Farnsworth wrote:
>
> > >
> > > Did you miss where I ACK'ed it 16-May-2007? :-)
> >
> > Ah okay, maybe I don't understand what that means. When you say
> > "Acked-by" does that mean you'll push it upstream?
>
> I meant that I picked the patch up, applied it to my tree,
> tested it, and verified that _I_ thought it was good.
> It received my Vote of Confidence, for whatever that is worth.
Ok. Thanks for acking it by the way.
>
> > What I meant was I haven't seen anybody pick up this patch yet, and
> > would like to know it if will be, or if there is something else I need
> > to do.
>
> Right. This patch is in "generic" PowerPC related code,
> and not in my area to "push upstream". I would expect, say,
> Paul to pick it up directly. Perhaps Kumar would pick it up
> and stage it for Paul. Perhaps akpm would pick it up. :-)
>
But since this is in drivers/rtc/Kconfig, wouldn't the maintainer of
that subsystem be expected to pick this up?
Thanks for the clarifications.
--Wade
next prev parent reply other threads:[~2007-06-07 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 16:57 [PATCH] Fix drivers/rtc/Kconfig for powerpc Wade Farnsworth
2007-06-06 17:07 ` Jon Loeliger
2007-06-06 17:17 ` Wade Farnsworth
2007-06-07 16:08 ` Jon Loeliger
2007-06-07 16:33 ` Wade Farnsworth [this message]
2007-06-07 16:37 ` Jon Loeliger
2007-06-07 23:34 ` David Gibson
2007-06-08 14:14 ` Loeliger Jon-LOELIGER
-- strict thread matches above, loose matches on Subject: below --
2007-05-15 16:53 Wade Farnsworth
2007-05-16 16:31 ` Jon Loeliger
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=1181233980.5674.174.camel@rhino \
--to=wfarnsworth@mvista.com \
--cc=a.zummo@towertech.it \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=rtc-linux@googlegroups.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).