linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: deller@gmx.de
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 15/15] fbdev/vfb: Remove trailing whitespaces
Date: Fri, 31 Mar 2023 11:23:14 +0200	[thread overview]
Message-ID: <20230331092314.2209-16-tzimmermann@suse.de> (raw)
In-Reply-To: <20230331092314.2209-1-tzimmermann@suse.de>

Fix coding style. No functional changes.

Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Acked-by: Helge Deller <deller@gmx.de>
---
 drivers/video/fbdev/vfb.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/video/fbdev/vfb.c b/drivers/video/fbdev/vfb.c
index 95d3c59867d0..680c88267ef4 100644
--- a/drivers/video/fbdev/vfb.c
+++ b/drivers/video/fbdev/vfb.c
@@ -110,7 +110,7 @@ static u_long get_line_length(int xres_virtual, int bpp)
      *  First part, xxxfb_check_var, must not write anything
      *  to hardware, it should only verify and adjust var.
      *  This means it doesn't alter par but it does use hardware
-     *  data from it to check this var. 
+     *  data from it to check this var.
      */
 
 static int vfb_check_var(struct fb_var_screeninfo *var,
@@ -168,7 +168,7 @@ static int vfb_check_var(struct fb_var_screeninfo *var,
 
 	/*
 	 * Now that we checked it we alter var. The reason being is that the video
-	 * mode passed in might not work but slight changes to it might make it 
+	 * mode passed in might not work but slight changes to it might make it
 	 * work. This way we let the user know what is acceptable.
 	 */
 	switch (var->bits_per_pixel) {
@@ -234,8 +234,8 @@ static int vfb_check_var(struct fb_var_screeninfo *var,
 }
 
 /* This routine actually sets the video mode. It's in here where we
- * the hardware state info->par and fix which can be affected by the 
- * change in par. For this driver it doesn't do much. 
+ * the hardware state info->par and fix which can be affected by the
+ * change in par. For this driver it doesn't do much.
  */
 static int vfb_set_par(struct fb_info *info)
 {
@@ -378,7 +378,7 @@ static int vfb_pan_display(struct fb_var_screeninfo *var,
 }
 
     /*
-     *  Most drivers don't need their own mmap function 
+     *  Most drivers don't need their own mmap function
      */
 
 static int vfb_mmap(struct fb_info *info,
-- 
2.40.0


  parent reply	other threads:[~2023-03-31  9:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  9:22 [PATCH 00/15] fbdev: Remove trailing whitespaces Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 01/15] fbdev/68328fb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 02/15] fbdev/atmel_lcdfb: " Thomas Zimmermann
2023-03-31  9:53   ` [02/15] " Sui Jingfeng
2023-03-31  9:23 ` [PATCH 03/15] fbdev/cg14: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 04/15] fbdev/controlfb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 05/15] fbdev/g364fb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 06/15] fbdev/hgafb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 07/15] fbdev/hpfb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 08/15] fbdev/macfb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 09/15] fbdev/maxinefb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 10/15] fbdev/p9100: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 11/15] fbdev/platinumfb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 12/15] fbdev/sa1100fb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 13/15] fbdev/stifb: " Thomas Zimmermann
2023-03-31  9:23 ` [PATCH 14/15] fbdev/valkyriefb: " Thomas Zimmermann
2023-03-31  9:23 ` Thomas Zimmermann [this message]
2023-05-11 12:08 ` [PATCH 00/15] fbdev: " Thomas Zimmermann
2023-05-11 12:51   ` Helge Deller
2023-05-11 12:53     ` Thomas Zimmermann
2023-05-11 13:05       ` 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=20230331092314.2209-16-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@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 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).