From: Randy Dunlap <rdunlap@infradead.org>
To: robgithub <rob.github@jumpstation.co.uk>,
Helge Deller <deller@gmx.de>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org
Cc: "Prasanna Kumar T S M" <ptsm@linux.microsoft.com>,
"Wei Liu" <wei.liu@kernel.org>,
"Michael Kelley" <mhklinux@outlook.com>,
"Sukrut Heroorkar" <hsukrut3@gmail.com>,
"Mukesh Rathor" <mrathor@linux.microsoft.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: fbdev: update outdated help text for CONFIG_FB_NVIDIA
Date: Thu, 12 Mar 2026 14:02:18 -0700 [thread overview]
Message-ID: <034989df-cf86-4136-8522-6c48e5523645@infradead.org> (raw)
In-Reply-To: <20260312205507.70b9013b@hexa5>
Hi,
On 3/12/26 1:55 PM, robgithub wrote:
> The help text for CONFIG_FB_NVIDIA refers to obsolete hardware and
> incorrect default behaviour. This patch updates the description to
> reflect the current state of the driver and supported devices.
>
> Signed-off-by: robgithub <rob.github@jumpstation.co.uk>
Inline patches are preferred over attachments.
I thought that Claws mail could send inline patches successfully. (?)
Documentation/process/email-clients.rst says that it works (after a little
configuration setting).
I don't know anything about which products are supported, so I have no
comment on that.
In the patch, the indentation is incorrect. Kconfig help text should be
indented with one tab + 2 spaces, not with 4 spaces.
thanks.
--
~Randy
next prev parent reply other threads:[~2026-03-12 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:55 robgithub
2026-03-12 21:02 ` Randy Dunlap [this message]
2026-03-13 20:35 ` robgithub
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=034989df-cf86-4136-8522-6c48e5523645@infradead.org \
--to=rdunlap@infradead.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsukrut3@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=mrathor@linux.microsoft.com \
--cc=ptsm@linux.microsoft.com \
--cc=rob.github@jumpstation.co.uk \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
--cc=wei.liu@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
all inboxes | Powered by JetHome®