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
Subject: Re: [GIT PULL] few omap driver fixes for v4.21
Date: Wed, 12 Dec 2018 14:21:04 -0800 [thread overview]
Message-ID: <20181212222104.yww344h66ql5lg4s@localhost> (raw)
In-Reply-To: <pull-1544638438-182658@atomide.com>
On Wed, Dec 12, 2018 at 10:14:33AM -0800, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 3be5e10daf1fc063ec5cff3cd785c4a59814af0b:
>
> Merge branch 'omap-for-v4.21/ti-sysc' into omap-for-v4.21/driver (2018-11-29 11:39:23 -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/driver-part2-signed
>
> for you to fetch changes up to c2ade654dbf7d02f09ad491f5621fc321d4af96b:
>
> memory: omap-gpmc: Use of_node_name_eq for node name comparisons (2018-12-11 08:30:29 -0800)
>
> ----------------------------------------------------------------
> Few more omap driver fixes and improvments for v4.21 merge window
>
> This series of changes improves the TI module flag handling to allow
> booting with older dts files until the module flags have been moved
> to the interconnect target module level. And there's a of_node_name_eq()
> clean-up patch from Rob Herring for the GPMC driver.
Merged into next/drivers. Thanks.
-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-12 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:14 [GIT PULL] few omap driver fixes for v4.21 Tony Lindgren
2018-12-12 22:21 ` 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=20181212222104.yww344h66ql5lg4s@localhost \
--to=olof@lixom.net \
--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