Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Hemanth Selam <hemanth.selam@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Peter Jones <pjones@redhat.com>,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] fbdev: fix typos in comments
Date: Sat, 12 Sep 2026 18:46:43 +0200	[thread overview]
Message-ID: <973b9e09-1fef-492b-9510-bb25d158b2d9@gmx.de> (raw)
In-Reply-To: <20260904111355.25780-1-hemanth.selam@gmail.com>

On 9/4/26 13:13, Hemanth Selam wrote:
> Fix typos in comments, reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
>   drivers/video/fbdev/aty/aty128fb.c              | 2 +-
>   drivers/video/fbdev/aty/atyfb_base.c            | 4 ++--
>   drivers/video/fbdev/aty/mach64_cursor.c         | 2 +-
>   drivers/video/fbdev/aty/radeon_base.c           | 4 ++--
>   drivers/video/fbdev/aty/radeon_monitor.c        | 4 ++--
>   drivers/video/fbdev/aty/radeonfb.h              | 2 +-
>   drivers/video/fbdev/au1100fb.c                  | 2 +-
>   drivers/video/fbdev/efifb.c                     | 4 ++--
>   drivers/video/fbdev/grvga.c                     | 2 +-
>   drivers/video/fbdev/kyro/STG4000OverlayDevice.c | 2 +-
>   drivers/video/fbdev/maxinefb.c                  | 2 +-
>   drivers/video/fbdev/mmp/core.c                  | 2 +-
>   drivers/video/fbdev/mmp/hw/mmp_ctrl.c           | 4 ++--
>   drivers/video/fbdev/mmp/hw/mmp_ctrl.h           | 4 ++--
>   drivers/video/fbdev/mmp/hw/mmp_spi.c            | 2 +-
>   drivers/video/fbdev/ocfb.c                      | 2 +-
>   drivers/video/fbdev/omap2/omapfb/dss/dispc.c    | 4 ++--
>   drivers/video/fbdev/pm2fb.c                     | 2 +-
>   drivers/video/fbdev/skeletonfb.c                | 6 +++---
>   drivers/video/fbdev/sstfb.c                     | 2 +-
>   drivers/video/fbdev/tgafb.c                     | 6 +++---
>   drivers/video/fbdev/tridentfb.c                 | 2 +-
>   drivers/video/fbdev/via/dvi.c                   | 6 +++---
>   drivers/video/fbdev/via/hw.c                    | 2 +-
>   drivers/video/fbdev/via/viafbdev.c              | 4 ++--
>   drivers/video/sticore.c                         | 2 +-
>   include/video/mmp_disp.h                        | 6 +++---
>   27 files changed, 43 insertions(+), 43 deletions(-)
I've splitted it up in smaller patches per driver and applied them.

Thanks!
Helge

  reply	other threads:[~2026-09-12 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 11:13 [PATCH] fbdev: fix typos in comments Hemanth Selam
2026-09-12 16:46 ` Helge Deller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-04 12:22 Hemanth Selam
2026-09-12 16:22 ` Helge Deller

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=973b9e09-1fef-492b-9510-bb25d158b2d9@gmx.de \
    --to=deller@gmx.de \
    --cc=FlorianSchandinat@gmx.de \
    --cc=benh@kernel.crashing.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pjones@redhat.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