linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for merge window
Date: Thu, 29 Mar 2012 07:41:52 -0700	[thread overview]
Message-ID: <20120329144151.GS9859@atomide.com> (raw)
In-Reply-To: <CAOesGMiKc5Tc2e5X9=gSiFS87JtMWGmmtOLSStWJcO7ayoE6Rg@mail.gmail.com>

* Olof Johansson <olof@lixom.net> [120328 22:04]:
> Hi Tony,
> 
> On Wed, Mar 21, 2012 at 11:05 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Hi Arnd & Olof,
> >
> > Here's a set of fixes that would be nice to get merged during
> > the merge window before the GPIO changes get merged to avoid
> > boot issues on many omap boards.
> >
> > The changes queued in the GPIO tree require getting rid of
> > OMAP_GPIO_IRQ and use gpio_to_irq() instead. This is needed for
> > dynamically allocated GPIO interrupt ranges.
> 
> Sorry for the slow response on this, we've been focused on getting the
> main pulls going in. I'm about to start a fixes branch now and looked
> at this pull request.
> 
> I replied to one of the original patches in this branch, they need to
> be fixed before they can go in:
> 
> http://marc.info/?l=linux-omap&m=133299716528617&w=2

Thanks, that's a good catch.
 
> Also, that way we can get a clean branch based on current mainline
> without merge conflicts.

Yes will do.

Regards,

Tony

  reply	other threads:[~2012-03-29 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 18:05 [GIT PULL] omap fixes for merge window Tony Lindgren
2012-03-29  5:01 ` Olof Johansson
2012-03-29 14:41   ` Tony Lindgren [this message]
2012-03-29 18:56     ` Tony Lindgren
2012-03-29 19:27       ` 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=20120329144151.GS9859@atomide.com \
    --to=tony@atomide.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 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).