From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [GIT PULL] omap1 changes for v4.21
Date: Wed, 12 Dec 2018 13:59:17 -0800 [thread overview]
Message-ID: <20181212215917.yao2orsyr6qqagi2@localhost> (raw)
In-Reply-To: <pull-1544638322-89579@atomide.com>
On Wed, Dec 12, 2018 at 10:13:14AM -0800, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> 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/tmlind/linux-omap tags/omap-for-v4.21/omap1-signed
>
> for you to fetch changes up to 5a87809b89b64c0ccd82261de53c41f2fffb56da:
>
> Merge branch 'omap1-usb-fix' into omap-for-v4.21/omap1 (2018-12-11 08:14:58 -0800)
>
> ----------------------------------------------------------------
> Changes for omap1 variants for v4.21 merge window
>
> In this set of changes Aaro Koskinen revives Palm Tungsten E for the
> MMC and USB making it usable again. And Janusz Krzysztofik follows up
> on the clean-up of ams-delta GPIO handling. The other changes are
> clean-up for DEFINE_SHOW_ATTRIBUTE by Yangtao Li.
Cool, merged into next/soc now. Is the kernel about to outgrow these platforms
due to binary size just slowly increasing over time, or is it still usable?
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-12 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:13 [GIT PULL] omap1 changes for v4.21 Tony Lindgren
2018-12-12 21:59 ` Olof Johansson [this message]
2018-12-12 23:02 ` Aaro Koskinen
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=20181212215917.yao2orsyr6qqagi2@localhost \
--to=olof@lixom.net \
--cc=aaro.koskinen@iki.fi \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 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).