linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin Stürz" <benni@stuerz.xyz>
To: "Benjamin Stürz" <benni@stuerz.xyz>
Cc: sebastian.hesselbarth@gmail.com, gregory.clement@bootlin.com,
	linux@armlinux.org.uk, linux@simtec.co.uk, krzk@kernel.org,
	alim.akhtar@samsung.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	robert.moore@intel.com, rafael.j.wysocki@intel.com,
	lenb@kernel.org, 3chas3@gmail.com, laforge@gnumonks.org,
	arnd@arndb.de, gregkh@linuxfoundation.org, mchehab@kernel.org,
	tony.luck@intel.com, james.morse@arm.com, rric@kernel.org,
	linus.walleij@linaro.org, brgl@bgdev.pl,
	mike.marciniszyn@cornelisnetworks.com,
	dennis.dalessandro@cornelisnetworks.com, jgg@ziepe.ca,
	pali@kernel.org, dmitry.torokhov@gmail.com, isdn@linux-pingi.de,
	benh@kernel.crashing.org, fbarrat@linux.ibm.com,
	ajd@linux.ibm.com, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, nico@fluxnic.net, loic.poulain@linaro.org,
	kvalo@kernel.org, pkshih@realtek.com, bhelgaas@google.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-ia64@vger.kernel.org, linux-acpi@vger.kernel.org,
	devel@acpica.org, linux-atm-general@lists.sourceforge.net,
	netdev@vger.kernel.org, linux-edac@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-input@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-media@vger.kernel.org, wcn36xx@lists.infradead.org,
	linux-wireless@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH 00/22] Replace comments with C99 initializers
Date: Sun, 27 Mar 2022 14:46:00 +0200	[thread overview]
Message-ID: <8f9271b6-0381-70a9-f0c2-595b2235866a@stuerz.xyz> (raw)
In-Reply-To: <20220326165909.506926-1-benni@stuerz.xyz>

This patch series replaces comments with C99's designated initializers
in a few places. It also adds some enum initializers. This is my first
time contributing to the Linux kernel, therefore I'm probably doing a
lot of things the wrong way. I'm sorry for that.

I've gotten a few emails so far stating that this patch series is
unnecessary. Yes, in fact this patch series is not necessary by itself,
but it could help me understand how the whole process works and maybe I
could help somewhere, where help is actually needed.

This patch itself is a no-op.

Signed-off-by: Benjamin Stürz <benni@stuerz.xyz>
---
 .gitignore | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitignore b/.gitignore
index 7afd412dadd2..706f667261eb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,7 +20,7 @@
 *.dtb
 *.dtbo
 *.dtb.S
-*.dwo
+*.dwo
 *.elf
 *.gcno
 *.gz
-- 
2.35.1

  parent reply	other threads:[~2022-03-27 12:46 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 16:58 [PATCH 01/22] orion5x: Replace comments with C99 initializers Benjamin Stürz
2022-03-26 16:58 ` [PATCH 02/22] s3c: " Benjamin Stürz
2022-03-26 19:44   ` Joe Perches
2022-03-28 13:37   ` Daniel Thompson
2022-03-26 16:58 ` [PATCH 03/22] ia64: " Benjamin Stürz
2022-03-26 16:58 ` [PATCH 04/22] x86: " Benjamin Stürz
2022-03-28 23:08   ` Thomas Gleixner
2022-03-26 16:58 ` [PATCH 05/22] acpica: " Benjamin Stürz
2022-03-27 19:59   ` Andy Shevchenko
2022-03-31 19:27     ` Moore, Robert
2022-04-01  5:09       ` Christoph Hellwig
2022-04-01  5:10     ` Christoph Hellwig
2022-03-28 12:33   ` Rafael J. Wysocki
2022-03-26 16:58 ` [PATCH 06/22] idt77252: " Benjamin Stürz
2022-03-26 16:58 ` [PATCH 07/22] cm4000: " Benjamin Stürz
2022-03-26 16:58 ` [PATCH 08/22] i5100: " Benjamin Stürz
2022-03-26 16:58 ` [PATCH 09/22] gpio-winbond: Use " Benjamin Stürz
2022-03-27 12:03   ` Linus Walleij
2022-03-29 12:30   ` Bartosz Golaszewski
2022-03-26 16:58 ` [PATCH 10/22] hfi1: Replace comments with " Benjamin Stürz
2022-03-26 16:58 ` [PATCH 11/22] rdmavt: " Benjamin Stürz
2022-03-27  7:04   ` Leon Romanovsky
2022-03-31 17:41     ` Dennis Dalessandro
2022-03-26 16:58 ` [PATCH 12/22] alps: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 13/22] capi: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 14/22] mISDN: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 15/22] macintosh: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 16/22] dvb-usb: " Benjamin Stürz
2022-03-26 18:24   ` Mauro Carvalho Chehab
2022-03-26 18:27     ` Mauro Carvalho Chehab
2022-03-26 19:51       ` Joe Perches
2022-03-26 20:11         ` Larry Finger
2022-03-26 21:08           ` Mauro Carvalho Chehab
2022-03-26 16:59 ` [PATCH 17/22] cxl: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 18/22] smsc: " Benjamin Stürz
2022-03-26 16:59 ` [PATCH 19/22] wnc36xx: " Benjamin Stürz
2022-03-28 16:17   ` Jeff Johnson
2022-03-26 16:59 ` [PATCH 20/22] wireless: " Benjamin Stürz
2022-03-28 12:06   ` Kalle Valo
2022-03-26 16:59 ` [PATCH 21/22] rtw89: " Benjamin Stürz
2022-03-26 18:55   ` Larry Finger
2022-03-28  9:28     ` Kalle Valo
2022-03-28 12:21       ` David Laight
2022-03-26 16:59 ` [PATCH 22/22] pci: " Benjamin Stürz
2022-03-26 18:20 ` [PATCH 01/22] orion5x: " Mauro Carvalho Chehab
2022-03-26 19:23 ` Arnd Bergmann
2022-03-28 13:19   ` Segher Boessenkool
2022-03-27 12:46 ` Benjamin Stürz [this message]
2022-03-28  9:33   ` [PATCH 00/22] " Kalle Valo
2022-03-28 11:51     ` Benjamin Stürz
2022-03-28 12:31       ` Kalle Valo
2022-03-28 20:20       ` Jakub Kicinski
2022-03-28 13:47   ` Daniel Thompson
2022-03-28 13:17 ` [PATCH 01/22] orion5x: " Daniel Thompson

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=8f9271b6-0381-70a9-f0c2-595b2235866a@stuerz.xyz \
    --to=benni@stuerz.xyz \
    --cc=3chas3@gmail.com \
    --cc=ajd@linux.ibm.com \
    --cc=alim.akhtar@samsung.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=brgl@bgdev.pl \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=devel@acpica.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=fbarrat@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@bootlin.com \
    --cc=hpa@zytor.com \
    --cc=isdn@linux-pingi.de \
    --cc=james.morse@arm.com \
    --cc=jgg@ziepe.ca \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=laforge@gnumonks.org \
    --cc=lenb@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@simtec.co.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loic.poulain@linaro.org \
    --cc=mchehab@kernel.org \
    --cc=mike.marciniszyn@cornelisnetworks.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=pabeni@redhat.com \
    --cc=pali@kernel.org \
    --cc=pkshih@realtek.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.com \
    --cc=rric@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=wcn36xx@lists.infradead.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).