From: Helge Deller <deller@gmx.de>
To: Javier Garcia <rampxxxx@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH v2] fbdev/vesafb: Use dev_* fn's instead printk.
Date: Fri, 31 Oct 2025 00:20:34 +0100 [thread overview]
Message-ID: <eb8bc92d-0b00-4ad2-81e4-904f39ea7ddf@gmx.de> (raw)
In-Reply-To: <20251030200723.2788931-1-rampxxxx@gmail.com>
On 10/30/25 21:07, Javier Garcia wrote:
> - Family dev_* fn's will show device name, giving extra info to logs.
> - Delete the prefix `vesafb:` from msg strings, not needed now.
>
> [ 0.981825] vesa-framebuffer vesa-framebuffer.0: scrolling: redraw
>
> Signed-off-by: Javier Garcia <rampxxxx@gmail.com>
> ---
> v1 -> v2:
> * Fix checkpatch.pl messages, thanks Helge Deller.
> * v1 https://lore.kernel.org/lkml/20251028185021.2758401-1-rampxxxx@gmail.com/
>
> drivers/video/fbdev/vesafb.c | 29 +++++++++++++++--------------
> 1 file changed, 15 insertions(+), 14 deletions(-)
applied.
Thanks!
Helge
prev parent reply other threads:[~2025-10-30 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 18:50 [PATCH] fbdev/vesafb: Use dev_* fn's instead printk Javier Garcia
2025-10-30 20:07 ` [PATCH v2] " Javier Garcia
2025-10-30 23:20 ` Helge Deller [this message]
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=eb8bc92d-0b00-4ad2-81e4-904f39ea7ddf@gmx.de \
--to=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rampxxxx@gmail.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).