linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Clean-up for omaps for v6.5
Date: Mon,  5 Jun 2023 09:28:53 +0300	[thread overview]
Message-ID: <pull-1685946511-835910@atomide.com> (raw)

From: "Tony Lindgren" <tony@atomide.com>

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v6.5/cleanup-signed

for you to fetch changes up to 937e87229ea04e94c4f1a2f3f5ae9d2c56989acd:

  ARM: omap2: Fix checkpatch issues (2023-06-02 12:33:48 +0300)

----------------------------------------------------------------
Clean-up for omaps for v6.5

Two patches for checkpatch warnings, and one change to use pr_err instead
of printk.

----------------------------------------------------------------
Franziska Naepelt (2):
      ARM: omap: Fix checkpatch issues
      ARM: omap2: Fix checkpatch issues

Prathu Baronia (1):
      arm: omap1: replace printk() with pr_err macro

 arch/arm/mach-omap1/pm.c                   |  2 +-
 arch/arm/mach-omap1/sram-init.c            |  2 +-
 arch/arm/mach-omap2/omap-wakeupgen.c       |  1 +
 arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 11 +++++------
 arch/arm/mach-omap2/omap_phy_internal.c    | 12 ++++++------
 arch/arm/mach-omap2/sdrc2xxx.c             |  2 --
 arch/arm/mach-omap2/sram.c                 |  4 ++--
 arch/arm/mach-omap2/ti81xx-restart.c       |  3 ++-
 8 files changed, 18 insertions(+), 19 deletions(-)

                 reply	other threads:[~2023-06-05  6:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pull-1685946511-835910@atomide.com \
    --to=tony@atomide.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=soc@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).