From: Richard Cochran <richardcochran@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Flavio Suligoi <f.suligoi@asem.it>,
IDT-support-1588@lm.renesas.com, Jakub Kicinski <kuba@kernel.org>,
LAPIS SEMICONDUCTOR <tshimizu818@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] Rid W=1 warnings from PTP
Date: Sat, 13 Mar 2021 06:37:32 -0800 [thread overview]
Message-ID: <20210313143732.GA31725@hoboy.vegasvil.org> (raw)
In-Reply-To: <20210312110910.2221265-1-lee.jones@linaro.org>
On Fri, Mar 12, 2021 at 11:09:06AM +0000, 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.
>
> Lee Jones (4):
> ptp_pch: Remove unused function 'pch_ch_control_read()'
> ptp_pch: Move 'pch_*()' prototypes to shared header
> ptp: ptp_clockmatrix: Demote non-kernel-doc header to standard comment
> ptp: ptp_p: Demote non-conformant kernel-doc headers and supply a
> param description
For the series:
Acked-by: Richard Cochran <richardcochran@gmail.com>
prev parent reply other threads:[~2021-03-13 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:09 [PATCH 0/4] Rid W=1 warnings from PTP Lee Jones
2021-03-12 11:09 ` [PATCH 1/4] ptp_pch: Remove unused function 'pch_ch_control_read()' Lee Jones
2021-03-12 11:09 ` [PATCH 2/4] ptp_pch: Move 'pch_*()' prototypes to shared header Lee Jones
2021-03-12 11:09 ` [PATCH 3/4] ptp: ptp_clockmatrix: Demote non-kernel-doc header to standard comment Lee Jones
2021-03-12 11:09 ` [PATCH 4/4] ptp: ptp_p: Demote non-conformant kernel-doc headers and supply a param description Lee Jones
2021-03-13 14:37 ` Richard Cochran [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=20210313143732.GA31725@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=IDT-support-1588@lm.renesas.com \
--cc=davem@davemloft.net \
--cc=f.suligoi@asem.it \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tshimizu818@gmail.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).