From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, dahinds@users.sourceforge.net,
Takashi Iwai <tiwai@suse.de>, Tian Tao <tiantao6@hisilicon.com>
Subject: Re: [PATCH 0/6] Rid W=1 warnings from PCMCIA
Date: Mon, 15 Mar 2021 08:25:38 +0100 [thread overview]
Message-ID: <YE8L8pO58W6rLN+l@light.dominikbrodowski.net> (raw)
In-Reply-To: <20210312110239.2220197-1-lee.jones@linaro.org>
Am Fri, Mar 12, 2021 at 11:02:33AM +0000 schrieb Lee Jones:
> 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.
>
> Lee Jones (6):
> pcmcia: rsrc_nonstatic: Demote kernel-doc abuses
> pcmcia: cistpl: Demote non-conformant kernel-doc headers to standard
> comments
> pcmcia: pcmcia_cis: Demote non-conforming kernel-doc headers to
> standard kernel-doc
> pcmcia: ds: Fix function name disparity in header
> pcmcia: pcmcia_resource: Fix some kernel-doc formatting/disparities
> and demote others
> pcmcia: rsrc_nonstatic: Fix call-back function as reference formatting
Applied the whole series to pcmcia-next, thanks.
Dominik
prev parent reply other threads:[~2021-03-15 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:02 Lee Jones
2021-03-12 11:02 ` [PATCH 1/6] pcmcia: rsrc_nonstatic: Demote kernel-doc abuses Lee Jones
2021-03-12 11:02 ` [PATCH 2/6] pcmcia: cistpl: Demote non-conformant kernel-doc headers to standard comments Lee Jones
2021-03-12 11:02 ` [PATCH 3/6] pcmcia: pcmcia_cis: Demote non-conforming kernel-doc headers to standard kernel-doc Lee Jones
2021-03-12 11:02 ` [PATCH 4/6] pcmcia: ds: Fix function name disparity in header Lee Jones
2021-03-12 11:02 ` [PATCH 5/6] pcmcia: pcmcia_resource: Fix some kernel-doc formatting/disparities and demote others Lee Jones
2021-03-12 11:02 ` [PATCH 6/6] pcmcia: rsrc_nonstatic: Fix call-back function as reference formatting Lee Jones
2021-03-15 7:25 ` Dominik Brodowski [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=YE8L8pO58W6rLN+l@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=dahinds@users.sourceforge.net \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiantao6@hisilicon.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®