linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: soc@kernel.org, arm@kernel.org
Cc: linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] amlogic Drivers updates for v6.7
Date: Mon, 16 Oct 2023 10:37:37 +0200	[thread overview]
Message-ID: <00ef6ab3-59c1-484a-9d70-50f16e4cc584@linaro.org> (raw)

Hi,

Here's an Amlogic Drivers changeset for v6.7, with only a couple of
low priority fixes concerning the meson_sm driver.

Neil

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

   Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

   https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git tags/amlogic-drivers-for-v6.7

for you to fetch changes up to 5d59b6a49bb8f6841acf53affc0c4720fe7450e5:

   firmware: meson: Use device_get_match_data() (2023-10-09 10:48:15 +0200)

----------------------------------------------------------------
Amlogic drivers changes for v6.7:
- correct meson_sm_* API retval handling
- Use device_get_match_data() in meson SM

----------------------------------------------------------------
Alexey Romanov (1):
       drivers: meson: sm: correct meson_sm_* API retval handling

Rob Herring (1):
       firmware: meson: Use device_get_match_data()

  drivers/firmware/meson/meson_sm.c       | 25 ++++++++++++++++---------
  include/linux/firmware/meson/meson_sm.h |  2 +-
  2 files changed, 17 insertions(+), 10 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2023-10-16  8:38 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=00ef6ab3-59c1-484a-9d70-50f16e4cc584@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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).