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 07/15] fbdev/hpfb: Remove trailing whitespaces
Date: Fri, 31 Mar 2023 11:23:06 +0200 [thread overview]
Message-ID: <20230331092314.2209-8-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>
---
drivers/video/fbdev/hpfb.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/video/fbdev/hpfb.c b/drivers/video/fbdev/hpfb.c
index cdd44e5deafe..77fbff47b1a8 100644
--- a/drivers/video/fbdev/hpfb.c
+++ b/drivers/video/fbdev/hpfb.c
@@ -92,7 +92,7 @@ static int hpfb_setcolreg(unsigned regno, unsigned red, unsigned green,
if (regno >= info->cmap.len)
return 1;
-
+
while (in_be16(fb_regs + 0x6002) & 0x4) udelay(1);
out_be16(fb_regs + 0x60ba, 0xff);
@@ -143,7 +143,7 @@ static void topcat_blit(int x0, int y0, int x1, int y1, int w, int h, int rr)
out_8(fb_regs + WMOVE, fb_bitmask);
}
-static void hpfb_copyarea(struct fb_info *info, const struct fb_copyarea *area)
+static void hpfb_copyarea(struct fb_info *info, const struct fb_copyarea *area)
{
topcat_blit(area->sx, area->sy, area->dx, area->dy, area->width, area->height, RR_COPY);
}
@@ -315,7 +315,7 @@ static int hpfb_init_one(unsigned long phys_base, unsigned long virt_base)
return ret;
}
-/*
+/*
* Check that the secondary ID indicates that we have some hope of working with this
* framebuffer. The catseye boards are pretty much like topcats and we can muddle through.
*/
@@ -323,7 +323,7 @@ static int hpfb_init_one(unsigned long phys_base, unsigned long virt_base)
#define topcat_sid_ok(x) (((x) == DIO_ID2_LRCATSEYE) || ((x) == DIO_ID2_HRCCATSEYE) \
|| ((x) == DIO_ID2_HRMCATSEYE) || ((x) == DIO_ID2_TOPCAT))
-/*
+/*
* Initialise the framebuffer
*/
static int hpfb_dio_probe(struct dio_dev *d, const struct dio_device_id *ent)
--
2.40.0
next prev 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 ` Thomas Zimmermann [this message]
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 ` [PATCH 15/15] fbdev/vfb: " Thomas Zimmermann
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-8-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).