linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>, devicetree@vger.kernel.org
Subject: [PATCH 0/2] Two omap4/5 fixes
Date: Mon,  8 Mar 2021 13:56:29 +0200	[thread overview]
Message-ID: <20210308115631.44270-1-tony@atomide.com> (raw)

Hi all,

Here two fixes noticed while testing my pending patches to drop legacy
data in favor of device tree data for omap4/5.

Regards,

Tony


Tony Lindgren (2):
  ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
  ARM: dts: Fix moving mmc devices with aliases for omap4 & 5

 arch/arm/boot/dts/omap4.dtsi           | 5 +++++
 arch/arm/boot/dts/omap44xx-clocks.dtsi | 8 --------
 arch/arm/boot/dts/omap5.dtsi           | 5 +++++
 3 files changed, 10 insertions(+), 8 deletions(-)

-- 
2.30.1

             reply	other threads:[~2021-03-08 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 11:56 Tony Lindgren [this message]
2021-03-08 11:56 ` [PATCH 1/2] ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race Tony Lindgren
2021-03-08 11:56 ` [PATCH 2/2] ARM: dts: Fix moving mmc devices with aliases for omap4 & 5 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=20210308115631.44270-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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).