From: pengfuyuan <pengfuyuan@kylinos.cn>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, "Helge Deller" <deller@gmx.de>,
"Hans de Goede" <hansg@kernel.org>, "Lee Jones" <lee@kernel.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Zsolt Kajtar" <soci@c64.rulez.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v1 v1 0/4] [RUST] Framebuffer driver support
Date: Tue, 27 Jan 2026 16:04:19 +0800 [thread overview]
Message-ID: <20260127080419.GA965382@peng> (raw)
In-Reply-To: <DFYG7MT5JINY.1T8ZZ4ASIWXU@nvidia.com>
On Mon, Jan 26, 2026 at 07:28:21PM +0900, Alexandre Courbot wrote:
> On Mon Jan 26, 2026 at 7:01 PM JST, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 26.01.26 um 09:17 schrieb pengfuyuan:
> >> This patch series adds Rust bindings and safe abstractions for the Linux
> >> framebuffer subsystem, enabling framebuffer drivers to be implemented in Rust.
> >
> > The framebuffer subsystem is obsolete and has been deprecated for a
> > decade. No new drivers accepted. Anything that really wants fbdev
> > already has a driver. Can we please let it die?
>
> This, and the patchset is also obviously AI-generated.
Hi,
Thank you for the feedback.
I’d like to be clear about how I used AI in this work:
1.Cover letter – Yes, I used AI to help summarize and phrase the cover letter.
2.Comments in the code – Some comments were written or refined with AI assistance.
3.Learning the codebase – When reading and understanding existing Rust-for-Linux code (including DRM and other abstractions), I used AI as a helper to analyze and explain structure and patterns.
4.Writing the code – The implementation was not fully generated by AI. I wrote the code myself and used AI mainly to look up existing abstractions, traits, and APIs (e.g. “how does X work? ”, “what’s the right trait for Y?”) while I was coding.
So: AI was used for summaries, comments, learning, and looking things up; the logic and structure of the code are mine, and I take responsibility for them.
If you have concerns about specific parts (e.g. wording, style, or design), I’m happy to rework those patches or to adjust how I describe tool use in future submissions.
Thanks,
pengfuyuan
next prev parent reply other threads:[~2026-01-27 8:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 8:17 [PATCH v1 v1 0/4] [RUST] Framebuffer driver support pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 1/4] rust: io: mem: add ioremap_wc support pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 2/4] rust: device: add platdata accessors pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 3/4] rust: fb: add framebuffer driver support pengfuyuan
2026-01-26 22:29 ` kernel test robot
2026-01-26 8:17 ` [PATCH v1 v1 4/4] rust: fb: add simplefb test driver pengfuyuan
2026-01-26 10:01 ` [PATCH v1 v1 0/4] [RUST] Framebuffer driver support Thomas Zimmermann
2026-01-26 10:28 ` Alexandre Courbot
2026-01-26 11:46 ` Miguel Ojeda
2026-01-27 8:30 ` pengfuyuan
2026-01-27 8:04 ` pengfuyuan [this message]
2026-01-27 8:16 ` Helge Deller
2026-01-27 8:58 ` pengfuyuan
2026-01-27 9:35 ` Greg Kroah-Hartman
2026-01-27 9:38 ` Helge Deller
2026-01-28 14:55 ` Alexandre Courbot
2026-01-26 12:27 ` Helge Deller
2026-01-26 10:32 ` Greg Kroah-Hartman
2026-01-26 12:15 ` Miguel Ojeda
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=20260127080419.GA965382@peng \
--to=pengfuyuan@kylinos.cn \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=soci@c64.rulez.org \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/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