From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] ACPI support fixes and cleanups for 7.2-rc1
Date: Tue, 30 Jun 2026 13:38:54 +0200 [thread overview]
Message-ID: <6023934.DvuYhMxLoT@rafael.j.wysocki> (raw)
In-Reply-To: <12935226.O9o76ZdvQC@rafael.j.wysocki>
On Monday, June 29, 2026 3:15:12 PM CEST Rafael J. Wysocki wrote:
> On Monday, June 29, 2026 2:22:51 PM CEST Rafael J. Wysocki (Intel) wrote:
> > On Fri, Jun 26, 2026 at 10:14 PM Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > >
> > > On Fri, 26 Jun 2026 at 10:54, Rafael J. Wysocki <rafael@kernel.org> wrote:
> > >
> > > How about just adding a trivial strncpy_pad() to
> > > <acpi/platform/acenv.h> or something. A place that already knows about
> > > the whole "I'm building the app side" now.
> > >
> > > Hmm?
> >
> > Something like that or define acpi_ut_safe_strncpy() as an alias for
> > strncpy_pad() when that's available.
> >
> > I'll figure this out.
Interestingly enough, the ACPICA tools don't even call acpi_ut_safe_strncpy(),
so if it is defined as an strncpy_pad() alias, the original definition of it
can be dropped entirely.
I'm going to make this change.
next prev parent reply other threads:[~2026-06-30 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 17:54 Rafael J. Wysocki
2026-06-26 20:13 ` Linus Torvalds
2026-06-26 20:31 ` Linus Torvalds
2026-06-29 12:22 ` Rafael J. Wysocki (Intel)
2026-06-29 13:15 ` Rafael J. Wysocki
2026-06-30 11:38 ` Rafael J. Wysocki [this message]
2026-06-26 20:31 ` 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=6023934.DvuYhMxLoT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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®