From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Arnd Bergmann" <arnd@kernel.org>,
"Andy Shevchenko" <andy@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Tronnes" <notro@tronnes.org>,
"Helge Deller" <deller@gmx.de>,
"Chintan Patel" <chintanlike@gmail.com>
Cc: "Abdun Nihaal" <abdun.nihaal@gmail.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Jianglei Nie" <niejianglei2021@163.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix dev_info() device arguments
Date: Mon, 02 Feb 2026 13:12:03 +0100 [thread overview]
Message-ID: <3384db41-0ddb-4c00-9af1-f194ec5dccc4@app.fastmail.com> (raw)
In-Reply-To: <6580aa60-5f9d-49c7-8482-83bed12dfb0c@suse.de>
On Mon, Feb 2, 2026, at 12:32, Thomas Zimmermann wrote:
> Hi,
>
> there's already
>
> https://patchwork.freedesktop.org/series/160468/
>
> which no one picked up yet. This needs to go into the fbdev tree, but I
> can also take into drm-misc-fixes.
Ok, that looks fine as well. The output is of course
different, but I don't think that matters either way.
> Am 02.02.26 um 10:57 schrieb Arnd Bergmann:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> Fixes: c296d5f9957c ("staging: fbtft: core support")
>> Fixes: bc9f9cb85a7d ("staging: fbtft: Make FB_DEVICE dependency optional")
>
> These commit hashes differ from the other fix?
No idea. The bc9f9cb85a7d commit is currently in linux-next,
the a06d03f9f238 is not.
Arnd
next prev parent reply other threads:[~2026-02-02 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:57 Arnd Bergmann
2026-02-02 11:32 ` Thomas Zimmermann
2026-02-02 12:12 ` Arnd Bergmann [this message]
2026-02-02 13:11 ` Helge Deller
2026-02-02 13:29 ` Thomas Zimmermann
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=3384db41-0ddb-4c00-9af1-f194ec5dccc4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=abdun.nihaal@gmail.com \
--cc=andy@kernel.org \
--cc=arnd@kernel.org \
--cc=chintanlike@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=niejianglei2021@163.com \
--cc=notro@tronnes.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tzimmermann@suse.de \
--cc=willy@infradead.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®