All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Can someone Ack and queue a patch for RTC subsytem?
Date: Fri, 20 Dec 2013 10:03:04 +0100	[thread overview]
Message-ID: <20131220090304.GA3144@lukather> (raw)
In-Reply-To: <20131219184924.13a12247@linux.lan.towertech.it>

Hi Alessandro,

On Thu, Dec 19, 2013 at 06:49:24PM +0100, Alessandro Zummo wrote:
> On Thu, 19 Dec 2013 18:46:18 +0100
> arno at natisbad.org (Arnaud Ebalard) wrote:
> 
> > > I don't mind routing it though mvebu/arm-soc since the only consumers
> > > are currently mvebu boards, but I'd like to hear from Andrew that this
> > > is ok.  
> > 
> > I will do what you think is the best.
> 
>  If the only consumers are mvebu boards, I believe it is correct to
>  route though that tree. imho.

We're pretty much in the same situation for the Allwinner RTC driver

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-November/211849.html

I'm fine with merging it through my tree, however, we still need some
reviews and an Acked-by from you.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131220/1d53aebe/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: Arnaud Ebalard <arno@natisbad.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Jason Cooper <jason@lakedaemon.net>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Stephen Warren <swarren@wwwdotorg.org>,
	linux-kernel@vger.kernel.org,
	Rob Herring <rob.herring@calxeda.com>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	Grant Likely <grant.likely@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>, Rob Landley <rob@landley.net>,
	Kumar Gala <galak@codeaurora.org>,
	rtc-linux@googlegroups.com,
	Peter Huewe <peter.huewe@infineon.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thierry Reding <treding@nvidia.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Can someone Ack and queue a patch for RTC subsytem?
Date: Fri, 20 Dec 2013 10:03:04 +0100	[thread overview]
Message-ID: <20131220090304.GA3144@lukather> (raw)
In-Reply-To: <20131219184924.13a12247@linux.lan.towertech.it>

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

Hi Alessandro,

On Thu, Dec 19, 2013 at 06:49:24PM +0100, Alessandro Zummo wrote:
> On Thu, 19 Dec 2013 18:46:18 +0100
> arno@natisbad.org (Arnaud Ebalard) wrote:
> 
> > > I don't mind routing it though mvebu/arm-soc since the only consumers
> > > are currently mvebu boards, but I'd like to hear from Andrew that this
> > > is ok.  
> > 
> > I will do what you think is the best.
> 
>  If the only consumers are mvebu boards, I believe it is correct to
>  route though that tree. imho.

We're pretty much in the same situation for the Allwinner RTC driver

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-November/211849.html

I'm fine with merging it through my tree, however, we still need some
reviews and an Acked-by from you.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-20  9:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 16:34 Can someone Ack and queue a patch for RTC subsytem? Arnaud Ebalard
2013-12-19 16:34 ` Arnaud Ebalard
2013-12-19 16:38 ` Alessandro Zummo
2013-12-19 16:38   ` Alessandro Zummo
2013-12-19 17:28   ` Arnaud Ebalard
2013-12-19 17:28     ` Arnaud Ebalard
2013-12-19 17:40     ` Alessandro Zummo
2013-12-19 17:40       ` Alessandro Zummo
2013-12-19 18:01       ` Jason Cooper
2013-12-19 18:01         ` Jason Cooper
2013-12-19 18:03         ` Alessandro Zummo
2013-12-19 18:03           ` Alessandro Zummo
2013-12-19 18:05       ` Arnaud Ebalard
2013-12-19 18:05         ` Arnaud Ebalard
2013-12-19 18:09         ` Jason Cooper
2013-12-19 18:09           ` Jason Cooper
2013-12-19 19:48           ` Guenter Roeck
2013-12-19 19:48             ` Guenter Roeck
2013-12-19 19:52             ` Jason Cooper
2013-12-19 19:52               ` Jason Cooper
2013-12-19 16:46 ` Jason Cooper
2013-12-19 16:46   ` Jason Cooper
2013-12-19 16:57   ` [rtc-linux] " Alessandro Zummo
2013-12-19 16:57     ` Alessandro Zummo
2013-12-19 22:17     ` Arnaud Ebalard
2013-12-19 22:17       ` Arnaud Ebalard
2013-12-20 18:30       ` Mark Brown
2013-12-20 18:30         ` Mark Brown
2013-12-20 20:23         ` Arnaud Ebalard
2013-12-20 20:23           ` Arnaud Ebalard
2013-12-21 14:16           ` Mark Brown
2013-12-21 14:16             ` Mark Brown
2013-12-19 17:46   ` Arnaud Ebalard
2013-12-19 17:46     ` Arnaud Ebalard
2013-12-19 17:49     ` Alessandro Zummo
2013-12-19 17:49       ` Alessandro Zummo
2013-12-20  9:03       ` Maxime Ripard [this message]
2013-12-20  9:03         ` Maxime Ripard
2013-12-20 11:00         ` Alessandro Zummo
2013-12-19 17:50     ` Jason Cooper
2013-12-19 17:50       ` Jason Cooper
2013-12-20  0:57     ` Jason Cooper
2013-12-20  0:57       ` Jason Cooper

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=20131220090304.GA3144@lukather \
    --to=maxime.ripard@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.