The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: linux-doc@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, simona.vetter@ffwll.ch,
	airlied@gmail.com,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH] docs: driver-api: firmware: clarify userspace requirements
Date: Mon, 17 Mar 2025 16:53:49 -0600	[thread overview]
Message-ID: <874izre0aq.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250314100137.2972355-1-jacek.lawrynowicz@linux.intel.com>

Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com> writes:

> The guidelines mention that firmware updates can't break the kernel,
> but it doesn't state directly that they can't break userspace programs.
> Make it explicit that firmware updates cannot break UAPI.
>
> Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
> ---
>  .../driver-api/firmware/firmware-usage-guidelines.rst        | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/driver-api/firmware/firmware-usage-guidelines.rst b/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> index fdcfce42c6d28..5f8f13e2ee510 100644
> --- a/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> +++ b/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> @@ -42,3 +42,8 @@ then of course these rules will not apply strictly.)
>    deprecating old major versions, then this should only be done as a
>    last option, and be stated clearly in all communications.
>  
> +* Firmware files that affect the User API (UAPI) shall not introduce
> +  changes that break existing userspace programs. Updates to such firmware
> +  must ensure backward compatibility with existing userspace applications.
> +  This includes maintaining consistent interfaces and behaviors that
> +  userspace programs rely on.
> \ No newline at end of file

This ^^^^^^^^^^^^^^^^^^^^^^^^  is a good thing to avoid.  That can be
fixed up at apply time.

Dave, you're the only one with fingerprints on this document; is the
change OK with you?

Thanks,

jon

  parent reply	other threads:[~2025-03-17 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 10:01 [PATCH] docs: driver-api: firmware: clarify userspace requirements Jacek Lawrynowicz
2025-03-14 12:34 ` Bagas Sanjaya
2025-03-17 22:53 ` Jonathan Corbet [this message]
2025-03-17 22:56   ` Dave Airlie
2025-03-17 23:06     ` Jonathan Corbet

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=874izre0aq.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simona.vetter@ffwll.ch \
    /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