public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	arm@kernel.org, Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: move of AIC drivers for 3.17: fixes #1
Date: Fri, 15 Aug 2014 16:41:50 +0200	[thread overview]
Message-ID: <20140815164150.5085b324@bbrezillon> (raw)
In-Reply-To: <20140815142225.GF5063@titan.lakedaemon.net>

Hi Jason,

On Fri, 15 Aug 2014 10:22:25 -0400
Jason Cooper <jason@lakedaemon.net> wrote:

> Nicolas,
> 
> On Thu, Aug 14, 2014 at 05:45:56PM +0200, Nicolas Ferre wrote:
> > Arnd, Olof, Kevin,
> > 
> > Boris moved both of our AIC drivers to their new home: the drivers/irqchip
> > directory taking advantage of the genirc framework. For DT-enabled SoCs, we can
> > use these drivers (aic and aic5) right now: Jason merged them and they are
> > available in early 3.17 merge window.
> > So, I build this pull-request for enabling the use of these drivers now as:
> > - we are very early in 3.17 development
> > - it allowed us to avoid having to depend on Jason's branch before the opening
> >   of the merge window
> 
> Then why did I create a topic branch for you to base on?
> 
>   git://git.infradead.org/users/jcooper/linux.git irqchip/atmel-aic

Don't blame Nicolas for this, he was in vacation when you created this
branch (he came back this week), and I should have told you that he
couldn't use it for this release cycle.

> 
> > - it removes some code from the mach-at91 directory: including the whole
> >   aic5 driver
> > - we'd have quite a bit of time to solve issues if we found a bug
> > - the code is basically moved so it should be error free.
> 
> Well, this is certainly up to Arnd, Olof and Kevin, but it seems a bit
> unusual.  You're basically asking to merge changes into the current window
> that has had _no_ time in -next...  Sounds like a recipe for trouble to
> me.
> 
> In the future, please let me know if you're not going to need a topic
> branch.

This is all my fault, I'm the one who asked Nicolas to get these patches
merged in 3.17, and, as I said, I should have told you that he was in
vacation and thus could not use your topic branch for this release
cycle.

Anyway, I understand your concern about merging stuff that have not been
tested on linux-next.

Arnd, Olof, Kevin, I'd totally understand if you refuses to takes these
patches for this release cycle.

Best Regards,

Boris


-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2014-08-15 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 15:45 [GIT PULL] at91: move of AIC drivers for 3.17: fixes #1 Nicolas Ferre
2014-08-15 14:22 ` Jason Cooper
2014-08-15 14:41   ` Boris BREZILLON [this message]
2014-08-15 15:05     ` Jason Cooper
2014-08-18 13:42       ` Nicolas Ferre
2014-08-16 15:31     ` 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=20140815164150.5085b324@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.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