From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Lee Jones <lee.jones@linaro.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
German Rivera <German.Rivera@freescale.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-omap@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Stuart Yoder <stuyoder@gmail.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 00/10] Rid W=1 warnings from Bus
Date: Thu, 17 Jun 2021 13:11:39 +0300 [thread overview]
Message-ID: <1711c37d-19d3-b923-d02a-433586c951ee@nxp.com> (raw)
In-Reply-To: <YMsajH2uxw4RHPeF@dell>
On 6/17/2021 12:49 PM, Lee Jones wrote:
> On Wed, 26 May 2021, Laurentiu Tudor wrote:
>
>> Hi Lee,
>>
>> On 5/26/2021 11:10 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.
>>>
>>> Lee Jones (10):
>>> bus: fsl-mc: mc-io: Supply function names for 'fsl_create_mc_io()' and
>>> 'fsl_destroy_mc_io()'
>>> bus: fsl-mc: mc-sys: Supply missing function names in kernel-doc
>>> headers
>>> bus: fsl-mc: fsl-mc-bus: Demote a bunch of non-conformant kernel-doc
>>> headers and help others
>>> bus: fsl-mc: dprc: Fix a couple of misspelling and formatting issues
>>> bus: fsl-mc: dprc-driver: Fix some missing/incorrect function
>>> parameter descriptions
>>> bus: fsl-mc: fsl-mc-allocator: Fix misspelling of 'new_mc_adev' and
>>> demote non-kernel-doc headers
>>> bus: qcom-ebi2: Fix incorrect documentation for '{slow,fast}_cfg'
>>> bus: fsl-mc-msi: Fix a little doc-rot pertaining to 'np' to 'fwnode'
>>> conversion
>>> bus: ti-sysc: Correct misdocumentation of 'sysc_ioremap()'
>>> bus: fsl-mc: mc-io: Correct misdocumentation of 'dpmcp_dev' param
>>>
>>> drivers/bus/fsl-mc/dprc-driver.c | 8 +++++---
>>> drivers/bus/fsl-mc/dprc.c | 4 ++--
>>> drivers/bus/fsl-mc/fsl-mc-allocator.c | 10 +++++-----
>>> drivers/bus/fsl-mc/fsl-mc-bus.c | 19 ++++++++++---------
>>> drivers/bus/fsl-mc/fsl-mc-msi.c | 2 +-
>>> drivers/bus/fsl-mc/mc-io.c | 6 +++---
>>> drivers/bus/fsl-mc/mc-sys.c | 19 ++++++++++---------
>>
>> Thanks for this. For drivers/bus/fsl-mc/*:
>>
>> Reviewed-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>
> Any idea who will take the 'fsl-mc' patches please?
>
Usually GregKH (added in the thread) picks them up through his char-misc
tree.
---
Best Regards, Laurentiu
next prev parent reply other threads:[~2021-06-17 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 8:10 [PATCH 00/10] Rid W=1 warnings from Bus Lee Jones
2021-05-26 8:10 ` [PATCH 07/10] bus: qcom-ebi2: Fix incorrect documentation for '{slow,fast}_cfg' Lee Jones
2021-05-26 22:33 ` Linus Walleij
2021-05-27 2:22 ` Bjorn Andersson
2021-05-26 12:19 ` [PATCH 00/10] Rid W=1 warnings from Bus Laurentiu Tudor
2021-06-17 9:49 ` Lee Jones
2021-06-17 10:11 ` Laurentiu Tudor [this message]
2021-06-17 10:57 ` Greg KH
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=1711c37d-19d3-b923-d02a-433586c951ee@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=German.Rivera@freescale.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stuyoder@gmail.com \
--cc=tony@atomide.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).