From: amarjargal <amarjargal16@gmail.com>
To: qemu-devel@nongnu.org
Cc: sgarzare@redhat.com, amarjargal <amarjargal16@gmail.com>
Subject: [PATCH 0/4] ui:hw: fix tab indentation
Date: Tue, 18 Oct 2022 02:23:55 +0800 [thread overview]
Message-ID: <cover.1666029821.git.amarjargal16@gmail.com> (raw)
There are still a lot of old files in the QEMU UI, graphics, audio and USB code base
that use TABs for indentation instead of using 4 spaces in these files.
The TABs should be replaced with spaces, to make sure that we have a consistent
coding style with an indentation of 4 spaces everywhere.
amarjargal (4):
ui: fix tab indentation
hw/audio: fix tab indentation into spaces
hw/display: fix tab indentation
hw/usb: fix tab indentation
hw/audio/fmopl.c | 1664 +++---
hw/audio/fmopl.h | 138 +-
hw/audio/intel-hda-defs.h | 1008 ++--
hw/audio/wm8750.c | 270 +-
hw/display/blizzard.c | 352 +-
hw/display/cirrus_vga.c | 1602 +++---
hw/display/omap_dss.c | 598 +--
hw/display/omap_lcdc.c | 24 +-
hw/display/pxa2xx_lcd.c | 196 +-
hw/display/tc6393xb.c | 74 +-
hw/display/vga.c | 6 +-
hw/display/vga_regs.h | 6 +-
hw/display/xenfb.c | 260 +-
hw/usb/dev-hub.c | 86 +-
hw/usb/dev-network.c | 286 +-
hw/usb/dev-wacom.c | 4 +-
hw/usb/hcd-musb.c | 328 +-
hw/usb/quirks-pl2303-ids.h | 180 +-
include/hw/usb.h | 118 +-
include/hw/usb/dwc2-regs.h | 1628 +++---
ui/vgafont.h | 9214 +++++++++++++++++-----------------
ui/vnc-enc-zywrle-template.c | 20 +-
ui/vnc-enc-zywrle.h | 16 +-
ui/vnc_keysym.h | 2 +-
24 files changed, 9040 insertions(+), 9040 deletions(-)
--
2.25.1
next reply other threads:[~2022-10-17 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 18:23 amarjargal [this message]
2022-10-17 18:23 ` [PATCH 1/4] ui: fix tab indentation amarjargal
2022-10-18 9:38 ` Daniel P. Berrangé
2022-10-17 18:23 ` [PATCH 2/4] hw/audio: fix tab indentation into spaces amarjargal
2022-10-17 18:23 ` [PATCH 3/4] hw/display: fix tab indentation amarjargal
2022-10-17 18:23 ` [PATCH 4/4] hw/usb: " amarjargal
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=cover.1666029821.git.amarjargal16@gmail.com \
--to=amarjargal16@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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;
as well as URLs for NNTP newsgroup(s).