From: Olof Johansson <olof@lixom.net>
To: Patrice CHOTARD <patrice.chotard@st.com>
Cc: "khilman@baylibre.com" <khilman@baylibre.com>,
"arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] STi SoC update for v4.21 round 1
Date: Mon, 31 Dec 2018 13:12:31 -0800 [thread overview]
Message-ID: <20181231211231.gtqe7lvl3nokdcx6@localhost> (raw)
In-Reply-To: <9459cb9d-aafe-b712-9c95-30b2ff979d34@st.com>
On Thu, Dec 20, 2018 at 01:54:20PM +0000, Patrice CHOTARD wrote:
> Hi Arnd, Olof, Kevin
>
> Please find STi SoC update for v4.21 round 1:
>
> The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
>
> Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git
> tags/sti-soc-for-v4.21-round1
>
> for you to fetch changes up to 704cfd7f5f71c6bc6cdfaa63a16ed0f72882b1a1:
>
> ARM: sti: remove pen_release and boot_lock (2018-12-20 14:32:15 +0100)
>
> ----------------------------------------------------------------
>
> Highlights:
> -----------
> - Following pen_release and boot_lock cleanup initiated by
> Russell King, .smp_prepare_cpus and .smp_boot_secondary STi callbacks
> must be reworked to keep secondary CPU's bringup.
Merged into next/late, will submit for upstream towards end of merge window to
get a bit of soak time.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-31 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 13:54 [GIT PULL] STi SoC update for v4.21 round 1 Patrice CHOTARD
2018-12-31 21:12 ` Olof Johansson [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=20181231211231.gtqe7lvl3nokdcx6@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@st.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