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: Dave Gerlach <d-gerlach@ti.com>, Faiz Abbas <faiz_abbas@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Keerthy <j-keerthy@ti.com>, Nishanth Menon <nm@ti.com>,
	Suman Anna <s-anna@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Few clean-up patches after dropping legacy data
Date: Fri, 12 Mar 2021 11:25:14 +0200	[thread overview]
Message-ID: <20210312092516.42884-1-tony@atomide.com> (raw)

Hi all,

Here are few clean-up patches after we are dropping the legacy data for
omap4/5 and dra7. These are against my omap-for-v5.13/genpd-drop-legacy
branch at [0].

Regards,

Tony


[0] https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v5.13/genpd-drop-legacy

Tony Lindgren (2):
  ARM: OMAP2+: Stop building legacy code for dra7 and omap4/5
  bus: ti-sysc: Warn about old dtb for dra7 and omap4/5

 arch/arm/mach-omap2/Makefile       |  8 ++++----
 arch/arm/mach-omap2/io.c           |  7 ++++++-
 arch/arm/mach-omap2/omap_hwmod.h   | 13 +++++++++++++
 arch/arm/mach-omap2/pdata-quirks.c |  2 +-
 arch/arm/mach-omap2/sr_device.c    |  7 +++++++
 drivers/bus/ti-sysc.c              |  3 +++
 6 files changed, 34 insertions(+), 6 deletions(-)

-- 
2.30.2

             reply	other threads:[~2021-03-12  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  9:25 Tony Lindgren [this message]
2021-03-12  9:25 ` [PATCH 1/2] ARM: OMAP2+: Stop building legacy code for dra7 and omap4/5 Tony Lindgren
2021-03-12  9:25 ` [PATCH 2/2] bus: ti-sysc: Warn about old dtb " 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=20210312092516.42884-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gerlach@ti.com \
    --cc=faiz_abbas@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=s-anna@ti.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).