From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
gerg@kernel.org
Subject: [git pull] m68knommu changes for v6.16
Date: Mon, 2 Jun 2025 08:53:11 +1000 [thread overview]
Message-ID: <992c6488-4089-4e0c-96cf-70e8d18b4986@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree changes for v6.16.
A couple of changes for v6.16. Use new GPIO line setting values for
local gpio driver. Make more use of strscpy().
Regards
Greg
The following changes since commit a5806cd506af5a7c19bcd596e4708b5c464bfd21:
Linux 6.15-rc7 (2025-05-18 13:57:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v6.16
for you to fetch changes up to eb43efd062d10bacdf6b50df0e300a7049474e51:
m68k: Replace memcpy() + manual NUL-termination with strscpy() (2025-05-19 08:54:30 +1000)
----------------------------------------------------------------
m68knommu: updates and fixes for v6.16
. use new gpio line value settings
. use strscpy() more
----------------------------------------------------------------
Bartosz Golaszewski (1):
m68k: coldfire: gpio: use new line value setter callbacks
Mohammad Mahdi Anbaraki (1):
m68k/kernel: replace strncpy() with strscpy()
Thorsten Blum (1):
m68k: Replace memcpy() + manual NUL-termination with strscpy()
arch/m68k/coldfire/gpio.c | 8 +++++---
arch/m68k/kernel/setup_no.c | 3 +--
arch/m68k/kernel/uboot.c | 2 +-
3 files changed, 7 insertions(+), 6 deletions(-)
next reply other threads:[~2025-06-01 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 22:53 Greg Ungerer [this message]
2025-06-02 20:15 ` pr-tracker-bot
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=992c6488-4089-4e0c-96cf-70e8d18b4986@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®