From: Jens Axboe <axboe@kernel.dk>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
ALWAYS copy <linux-ide@vger.kernel.org>,
Andre Hedrick <andre@linux-ide.org>,
Colten Edwards <pje120@cs.usask.ca>, Hat Inc <alan@redhat.com>,
Jan Harkes <jaharkes@cwi.nl>, Jaromir Koutek <miri@punknet.cz>,
"L.C. Chang" <lcchang@sis.com.tw>,
Lionel Bouton <Lionel.Bouton@inet6.fr>,
Mark Lord <mlord@pobox.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Torben Mathiasen <torben.mathiasen@hp.com>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH 00/15] [Set 2] Rid W=1 warnings from ATA
Date: Tue, 30 Mar 2021 20:21:58 -0600 [thread overview]
Message-ID: <e4b9785d-ba31-e1ce-dbab-0fd31605e9d1@kernel.dk> (raw)
In-Reply-To: <20210318085150.3131936-1-lee.jones@linaro.org>
On 3/18/21 2:51 AM, Lee Jones wrote:
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
>
> This is set 2 out of 2 sets required.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-03-31 2:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 8:51 [PATCH 00/15] [Set 2] Rid W=1 warnings from ATA Lee Jones
2021-03-18 8:51 ` [PATCH 01/15] ata: pata_pdc202xx_old: Fix some incorrectly named functions Lee Jones
2021-03-18 8:51 ` [PATCH 02/15] ata: pata_sil680: Add some missing function parameter docs Lee Jones
2021-03-18 8:51 ` [PATCH 03/15] ata: pata_sis: Remove superfluous param description and supply another Lee Jones
2021-03-18 8:51 ` [PATCH 04/15] ata: pata_triflex: Repair some misnamed functions and fix some param descriptions Lee Jones
2021-03-18 8:51 ` [PATCH 05/15] ata: pata_it821x: Fix possible doc-rotted function names Lee Jones
2021-03-18 8:51 ` [PATCH 06/15] ata: pata_via: Fix a kernel-doc formatting issue Lee Jones
2021-03-18 8:51 ` [PATCH 07/15] ata: pata_piccolo: 'ata_tosh_init()' is misnamed in its header Lee Jones
2021-03-18 8:51 ` [PATCH 08/15] ata: pata_sl82c105: Fix potential doc-rot Lee Jones
2021-03-18 8:51 ` [PATCH 09/15] ata: pata_opti: Fix spelling issue of 'val' in 'opti_write_reg()' Lee Jones
2021-03-18 8:51 ` [PATCH 10/15] ata: ata_generic: Fix misspelling of 'ata_generic_init_one()' Lee Jones
2021-03-18 8:51 ` [PATCH 11/15] ata: pata_legacy: Repair a couple kernel-doc problems Lee Jones
2021-03-18 8:51 ` [PATCH 12/15] ata: pata_cs5530: Fix misspelling of 'cs5530_init_one()'s 'pdev' param Lee Jones
2021-03-18 8:51 ` [PATCH 13/15] ata: sata_mv: Fix misnaming of 'mv_bmdma_stop()' Lee Jones
2021-03-18 8:51 ` [PATCH 14/15] ata: libata-acpi: Fix function name and provide description for 'prev_gtf' Lee Jones
2021-03-18 8:51 ` [PATCH 15/15] ata: pata_acpi: Fix some incorrect function param descriptions Lee Jones
2021-03-30 13:20 ` [PATCH 00/15] [Set 2] Rid W=1 warnings from ATA Lee Jones
2021-03-31 2:21 ` Jens Axboe [this message]
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=e4b9785d-ba31-e1ce-dbab-0fd31605e9d1@kernel.dk \
--to=axboe@kernel.dk \
--cc=Lionel.Bouton@inet6.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=andre@linux-ide.org \
--cc=jaharkes@cwi.nl \
--cc=lcchang@sis.com.tw \
--cc=lee.jones@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miri@punknet.cz \
--cc=mlord@pobox.com \
--cc=pje120@cs.usask.ca \
--cc=samuel.thibault@ens-lyon.org \
--cc=torben.mathiasen@hp.com \
--cc=vojtech@suse.cz \
/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