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 v3.4-rc1
Date: Thu, 5 Apr 2012 11:19:00 -0700	[thread overview]
Message-ID: <20120405181900.GE3785@atomide.com> (raw)
In-Reply-To: <CAOesGMg7DWDH4ix30fh23YZ1hg207S7oQ05njrfEBkaYPjKWDQ@mail.gmail.com>

* Olof Johansson <olof@lixom.net> [120405 10:51]:
> Hi,
> 
> On Wed, Apr 4, 2012 at 5:42 PM, Tony Lindgren <tony@atomide.com> wrote:
> > Hi Arnd & Olof,
> >
> > Please pull omap fixes from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes
> >
> > Note that this also contains a set of fixes that are not regressions
> > or oopses to properly deal with the smsc911x regulator issue.
> >
> > Basically the regulators must be per board file as the regulators
> > can also come from drivers, such as twl4030. So it's best to dumb
> > down gpmc-smsc911x.c to not even care about the regulators.
> >
> > Regards,
> >
> > Tony
> >
> >
> > The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:
> > ?Linus Torvalds (1):
> > ? ? ? ?Linux 3.4-rc1
> >
> > are available in the git repository at:
> >
> > ?git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes
> 
> 
> Thanks, pulled.

Thanks.
 
> Feel free to start sending these as signed tags with the above in the
> tag description, so it's carried forward in the git history without
> any work for us. :-)

OK will do.

Tony

      reply	other threads:[~2012-04-05 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  0:42 [GIT PULL] omap fixes for v3.4-rc1 Tony Lindgren
2012-04-05 17:48 ` Olof Johansson
2012-04-05 18:19   ` 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=20120405181900.GE3785@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).