All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jilin Yuan <yuanjilin@cdjrlc.com>
To: deller@gmx.de
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Jilin Yuan <yuanjilin@cdjrlc.com>
Subject: [PATCH] video/fbdev: fix repeated words in comments
Date: Tue, 16 Aug 2022 21:10:13 +0800	[thread overview]
Message-ID: <20220816131013.30643-1-yuanjilin@cdjrlc.com> (raw)

 Delete the redundant word 'its'.

Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
---
 drivers/video/fbdev/skeletonfb.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/skeletonfb.c b/drivers/video/fbdev/skeletonfb.c
index 818b3a5003e1..f316ea320d29 100644
--- a/drivers/video/fbdev/skeletonfb.c
+++ b/drivers/video/fbdev/skeletonfb.c
@@ -97,7 +97,7 @@ static const struct fb_fix_screeninfo xxxfb_fix = {
     /*
      * 	Modern graphical hardware not only supports pipelines but some 
      *  also support multiple monitors where each display can have its  
-     *  own unique data. In this case each display could be  
+     *  own unique data. In this case each display could be
      *  represented by a separate framebuffer device thus a separate 
      *  struct fb_info. Now the struct xxx_par represents the graphics
      *  hardware state thus only one exist per card. In this case the 
-- 
2.36.1


WARNING: multiple messages have this Message-ID (diff)
From: Jilin Yuan <yuanjilin@cdjrlc.com>
To: deller@gmx.de
Cc: linux-fbdev@vger.kernel.org, Jilin Yuan <yuanjilin@cdjrlc.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH] video/fbdev: fix repeated words in comments
Date: Tue, 16 Aug 2022 21:10:13 +0800	[thread overview]
Message-ID: <20220816131013.30643-1-yuanjilin@cdjrlc.com> (raw)

 Delete the redundant word 'its'.

Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
---
 drivers/video/fbdev/skeletonfb.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/skeletonfb.c b/drivers/video/fbdev/skeletonfb.c
index 818b3a5003e1..f316ea320d29 100644
--- a/drivers/video/fbdev/skeletonfb.c
+++ b/drivers/video/fbdev/skeletonfb.c
@@ -97,7 +97,7 @@ static const struct fb_fix_screeninfo xxxfb_fix = {
     /*
      * 	Modern graphical hardware not only supports pipelines but some 
      *  also support multiple monitors where each display can have its  
-     *  own unique data. In this case each display could be  
+     *  own unique data. In this case each display could be
      *  represented by a separate framebuffer device thus a separate 
      *  struct fb_info. Now the struct xxx_par represents the graphics
      *  hardware state thus only one exist per card. In this case the 
-- 
2.36.1


             reply	other threads:[~2022-08-16 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 13:10 Jilin Yuan [this message]
2022-08-16 13:10 ` [PATCH] video/fbdev: fix repeated words in comments Jilin Yuan
  -- strict thread matches above, loose matches on Subject: below --
2022-08-16 13:07 Jilin Yuan
2022-08-16 13:07 ` Jilin Yuan
2022-08-24  7:31 ` Geert Uytterhoeven

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=20220816131013.30643-1-yuanjilin@cdjrlc.com \
    --to=yuanjilin@cdjrlc.com \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.