From: Kevin Hilman <khilman@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window
Date: Mon, 14 Oct 2013 15:27:18 -0700 [thread overview]
Message-ID: <87mwmb4hfd.fsf@linaro.org> (raw)
In-Reply-To: <5258a9a0.0325310a.6fb0.ffffa19cSMTPIN_ADDED_BROKEN@mx.google.com> (Tony Lindgren's message of "Fri, 11 Oct 2013 18:44:57 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6:
>
> Linux 3.12-rc3 (2013-09-29 15:02:38 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/fixes-not-urgent-signed
>
> for you to fetch changes up to 8ff875e7f93e900e7a7e78f1c9c05a22b33c27cf:
>
> ARM: mach-omap1: Fix omap1510_fpga_init_irq() implicit declarations. (2013-10-08 11:04:22 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps that were not considered urgent for the -rc series.
> Just minor build fixes, removal of dead code, and a patch to
> use the die ID for increasing boot time entropy.
>
> ----------------------------------------------------------------
Thanks, pulled into fixes-non-critical.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window
Date: Mon, 14 Oct 2013 15:27:18 -0700 [thread overview]
Message-ID: <87mwmb4hfd.fsf@linaro.org> (raw)
In-Reply-To: <5258a9a0.0325310a.6fb0.ffffa19cSMTPIN_ADDED_BROKEN@mx.google.com> (Tony Lindgren's message of "Fri, 11 Oct 2013 18:44:57 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6:
>
> Linux 3.12-rc3 (2013-09-29 15:02:38 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/fixes-not-urgent-signed
>
> for you to fetch changes up to 8ff875e7f93e900e7a7e78f1c9c05a22b33c27cf:
>
> ARM: mach-omap1: Fix omap1510_fpga_init_irq() implicit declarations. (2013-10-08 11:04:22 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps that were not considered urgent for the -rc series.
> Just minor build fixes, removal of dead code, and a patch to
> use the die ID for increasing boot time entropy.
>
> ----------------------------------------------------------------
Thanks, pulled into fixes-non-critical.
Kevin
next parent reply other threads:[~2013-10-14 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5258a9a0.0325310a.6fb0.ffffa19cSMTPIN_ADDED_BROKEN@mx.google.com>
2013-10-14 22:27 ` Kevin Hilman [this message]
2013-10-14 22:27 ` [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window Kevin Hilman
2013-10-12 1:44 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2013-10-12 1:44 Tony Lindgren
2013-10-12 1:44 Tony Lindgren
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=87mwmb4hfd.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.