From: Kalle Valo <kvalo@kernel•org>
To: "Benjamin Stürz" <benni@stuerz•xyz>
Cc: linux-atm-general@lists•sourceforge.net,
linux-ia64@vger•kernel.org, linus.walleij@linaro•org,
dave.hansen@linux•intel.com, linux-pci@vger•kernel.org,
robert.moore@intel•com, laforge@gnumonks•org,
alim.akhtar@samsung•com, hpa@zytor•com,
wcn36xx@lists•infradead.org, pkshih@realtek•com,
linux-samsung-soc@vger•kernel.org, linux-acpi@vger•kernel.org,
linux-edac@vger•kernel.org,
dennis.dalessandro@cornelisnetworks•com,
linux-rdma@vger•kernel.org, gregory.clement@bootlin•com,
rafael.j.wysocki@intel•com, linux@armlinux•org.uk,
krzk@kernel•org, jgg@ziepe•ca, mingo@redhat•com,
3chas3@gmail•com, linux-input@vger•kernel.org, kuba@kernel•org,
pabeni@redhat•com, lenb@kernel•org,
mike.marciniszyn@cornelisnetworks•com, rric@kernel•org,
ajd@linux•ibm.com, arnd@arndb•de, linuxppc-dev@lists•ozlabs.org,
linux-gpio@vger•kernel.org, loic.poulain@linaro•org,
bp@alien8•de, bhelgaas@google•com, tglx@linutronix•de,
mchehab@kernel•org, linux-media@vger•kernel.org,
linux@simtec•co.uk, linux-arm-kernel@lists•infradead.org,
devel@acpica•org, isdn@linux-pingi•de, tony.luck@intel•com,
nico@fluxnic•net, gregkh@linuxfoundation•org,
dmitry.torokhov@gmail•com, linux-wireless@vger•kernel.org,
linux-kernel@vger•kernel.org, davem@davemloft•net,
james.morse@arm•com, netdev@vger•kernel.org,
fbarrat@linux•ibm.com, sebastian.hesselbarth@gmail•com,
pali@kernel•org, brgl@bgdev•pl
Subject: Re: [PATCH 00/22] Replace comments with C99 initializers
Date: Mon, 28 Mar 2022 12:33:42 +0300 [thread overview]
Message-ID: <87fsn2zaix.fsf@kernel.org> (raw)
In-Reply-To: <8f9271b6-0381-70a9-f0c2-595b2235866a@stuerz.xyz> ("Benjamin \=\?utf-8\?Q\?St\=C3\=BCrz\=22's\?\= message of "Sun, 27 Mar 2022 14:46:00 +0200")
Benjamin Stürz <benni@stuerz•xyz> writes:
> 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.
Just a small tip: If you are new, start with something small and learn
from that. Don't do a controversial big patchset spanning multiple
subsystems, that's the hard way to learn things. First submit one patch
at a time to one subsystem and gain understanding of the process that
way.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-03-28 10:58 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 ` [PATCH 00/22] " Benjamin Stürz
2022-03-28 9:33 ` Kalle Valo [this message]
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=87fsn2zaix.fsf@kernel.org \
--to=kvalo@kernel$(echo .)org \
--cc=3chas3@gmail$(echo .)com \
--cc=ajd@linux$(echo .)ibm.com \
--cc=alim.akhtar@samsung$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=benni@stuerz$(echo .)xyz \
--cc=bhelgaas@google$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=brgl@bgdev$(echo .)pl \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=davem@davemloft$(echo .)net \
--cc=dennis.dalessandro@cornelisnetworks$(echo .)com \
--cc=devel@acpica$(echo .)org \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=fbarrat@linux$(echo .)ibm.com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=gregory.clement@bootlin$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=isdn@linux-pingi$(echo .)de \
--cc=james.morse@arm$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=krzk@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=laforge@gnumonks$(echo .)org \
--cc=lenb@kernel$(echo .)org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-atm-general@lists$(echo .)sourceforge.net \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-gpio@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-samsung-soc@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=linux@simtec$(echo .)co.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=loic.poulain@linaro$(echo .)org \
--cc=mchehab@kernel$(echo .)org \
--cc=mike.marciniszyn@cornelisnetworks$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nico@fluxnic$(echo .)net \
--cc=pabeni@redhat$(echo .)com \
--cc=pali@kernel$(echo .)org \
--cc=pkshih@realtek$(echo .)com \
--cc=rafael.j.wysocki@intel$(echo .)com \
--cc=robert.moore@intel$(echo .)com \
--cc=rric@kernel$(echo .)org \
--cc=sebastian.hesselbarth@gmail$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=tony.luck@intel$(echo .)com \
--cc=wcn36xx@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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