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] ARM: omap2: twl-common update
Date: Fri, 15 Mar 2013 09:24:16 -0700	[thread overview]
Message-ID: <20130315162416.GC9370@atomide.com> (raw)
In-Reply-To: <5142E376.9080407@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [130315 02:05]:
> Hi Tony,
> 
> The branch is on top of today's mainline.
> Is it still possible to send this for 3.9?

It seems that fixing reboot is a good reason to try to merge it during
the -rc cycle. Is this a regression? If so it should mention what broke
it.

Also please base this on a recent mainline tag like v3.8 or v3.9-rc2..
 
> The following changes since commit a2362d24764a4e9a3187fc46b14e1d2cd0657700:
> 
>   mm/fremap.c: fix possible oops on error path (2013-03-14 17:00:39 -0700)

..as this commit seems to be a random base and might cause confusion that
there's some dependency to that patch.

Regards,

Tony
 
> are available in the git repository at:
> 
>   git://gitorious.org/omap-audio/linux-audio.git peter/upstream/for-tony
> 
> for you to fetch changes up to 25d28e7988512eb4964eca5fc54a214ae69a7154:
> 
>   omap2: twl-common: Add default power configuration (2013-03-15 09:59:28 +0100)
> 
> ----------------------------------------------------------------
> Matthias Brugger (1):
>       omap2: twl-common: Add default power configuration
> 
>  arch/arm/mach-omap2/twl-common.c | 38 ++++++++++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/twl-common.h |  1 +
>  2 files changed, 39 insertions(+)

      reply	other threads:[~2013-03-15 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  9:01 [GIT PULL] ARM: omap2: twl-common update Peter Ujfalusi
2013-03-15 16:24 ` Tony Lindgren [this message]

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=20130315162416.GC9370@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).