linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Russell King - ARM Linux (linux@arm.linux.org.uk)"
	<linux@arm.linux.org.uk>, Loic PALLARDY <loic.pallardy@st.com>,
	"Tony Lindgren (tony@atomide.com)" <tony@atomide.com>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	Olof Johansson <olof@lixom.net>, Suman Anna <s-anna@ti.com>,
	"Omar Ramirez Luna (omar.ramirez@copitl.com)"
	<omar.ramirez@copitl.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] mailbox driver framework for v3.10 merge window
Date: Fri, 03 May 2013 15:49:05 +0200	[thread overview]
Message-ID: <4518021.h47erc1rfT@wuerfel> (raw)
In-Reply-To: <CACRpkdYSnNeO8F-1WWN9J+pkMi6B_Qydo85QovbgWOEoDDS9Aw@mail.gmail.com>

On Friday 03 May 2013 15:39:42 Linus Walleij wrote:
> On Fri, May 3, 2013 at 3:25 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 02 May 2013 17:09:07 Suman Anna wrote:
> >>
> >> I do not know how much of an impact it is for the ST driver as the
> >> series adds the driver, and would have to wait until the RFC is sorted
> >> out otherwise.
> >
> > I think I'd prefer to drop the branch from the 3.10 queue then
> > and let you all work out a common approach for 3.11. Olof, any
> > other input?
> 
> This will block all refactoring of the PRCMU driver, which Loic
> is working on, and also Ulf Hansson's clock driver. It is basically
> the key to breaking that driver apart and distributing it out into
> the proper subsystems. Loic has a big patch series for that
> for next merge window which will then have to be postponed,
> or queued on top of the mailbox work when finished.
> 
> But maybe it's the right thing to do if the subsystem needs more
> work? I have no clear opinion on this, Loic, Ulf?

I think we can queue them together. I'm certainly fine with the
mailbox subsystem getting merged through both the mfd and arm-soc
trees to avoid conflicts.

	Arnd

  reply	other threads:[~2013-05-03 13:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 21:48 [GIT PULL] mailbox driver framework for v3.10 merge window Anna, Suman
2013-04-09 10:55 ` Arnd Bergmann
2013-04-09 15:33   ` Anna, Suman
2013-04-29  4:07   ` Jassi Brar
2013-05-02 22:09     ` Suman Anna
2013-05-03  2:37       ` Jassi Brar
2013-05-03 16:29         ` Suman Anna
2013-05-03 13:25       ` Arnd Bergmann
2013-05-03 13:39         ` Linus Walleij
2013-05-03 13:49           ` Arnd Bergmann [this message]
     [not found] <CAFiDJ5_++vtnrExrRoAbn89GmuKycE_tuWGjPHXTw_E0SycLpg@mail.gmail.com>
2013-06-13 15:59 ` Suman Anna
     [not found] <CAFiDJ5_1w+M6TTroeQEjOcc5GNN2RCmLN4ZB5dxQNwoc+9R1YQ@mail.gmail.com>
2013-06-16 20:14 ` Suman Anna
2013-06-17 20:01   ` Olof Johansson

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=4518021.h47erc1rfT@wuerfel \
    --to=arnd@arndb.de \
    --cc=jaswinder.singh@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=loic.pallardy@st.com \
    --cc=olof@lixom.net \
    --cc=omar.ramirez@copitl.com \
    --cc=s-anna@ti.com \
    --cc=tony@atomide.com \
    --cc=ulf.hansson@linaro.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).