From: Randy Dunlap <rdunlap@infradead.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Tony Lindgren" <tony@atomide.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, patches@armlinux.org.uk,
"Paul Walmsley" <paul@pwsan.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Kevin Hilman" <khilman@kernel.org>
Subject: Re: [PATCH 00/13] ARM: OMAP2+: fix a bunch of kernel-doc warnings
Date: Thu, 1 Feb 2024 08:27:25 -0800 [thread overview]
Message-ID: <1f53a83d-cae4-4223-ad47-6d1d9c80dc2b@infradead.org> (raw)
In-Reply-To: <ZbtlOWcGglCeYj6X@shell.armlinux.org.uk>
On 2/1/24 01:32, Russell King (Oracle) wrote:
> On Wed, Jan 17, 2024 at 08:52:16AM -0800, Randy Dunlap wrote:
>>
>>
>> On 1/17/24 05:13, Tony Lindgren wrote:
>>> * Randy Dunlap <rdunlap@infradead.org> [240117 01:10]:
>>>> Fix many kernel-doc warnings in arch/arm/mach-omap2/:
>>>
>>> Thanks for fixing these. These are unlikely to conflict with anything so
>>> please queue them along with other clean-up:
>>>
>>> Acked-by: Tony Lindgren <tony@atomide.com>
>>>
>>> Or alternatively let me know if you want me to apply them.
>>
>> Yes, please go ahead and apply them.
>
> If you intend people other than me to apply patches, then please do not
> copy the patches to the patch system. I now have to go through all 16
> patches and search the mailing list to find out what happened... and so
> far for the few I've checked, other people have applied them. So I'm
> coming to the conclusion I should just discard the entire lot.
>
Got it. and sorry about that. :(
--
#Randy
prev parent reply other threads:[~2024-02-01 16:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 1:09 [PATCH 00/13] ARM: OMAP2+: fix a bunch of kernel-doc warnings Randy Dunlap
2024-01-17 1:09 ` [PATCH 01/13] ARM: OMAP2+: am33xx-restart: fix function name in kernel-doc Randy Dunlap
2024-01-17 1:09 ` [PATCH 02/13] ARM: OMAP2+: clockdomain: fix kernel-doc warnings Randy Dunlap
2024-01-17 1:09 ` [PATCH 03/13] ARM: OMAP2+: clock: fix a function name in kernel-doc Randy Dunlap
2024-01-17 1:09 ` [PATCH 04/13] ARM: OMAP2+: cm33xx: use matching " Randy Dunlap
2024-01-17 1:09 ` [PATCH 05/13] ARM: OMAP2+: CMINST: " Randy Dunlap
2024-01-17 1:09 ` [PATCH 06/13] ARM: OMAP2+: hwmod: remove misuse of kernel-doc Randy Dunlap
2024-01-17 1:09 ` [PATCH 07/13] ARM: OMAP2+: hwmod: fix kernel-doc warnings Randy Dunlap
2024-01-17 1:09 ` [PATCH 08/13] ARM: OMAP2+: pmic-cpcap: " Randy Dunlap
2024-01-17 1:09 ` [PATCH 09/13] ARM: OMAP2+: prm44xx: fix a kernel-doc warning Randy Dunlap
2024-01-17 1:09 ` [PATCH 10/13] ARM: OMAP2+: PRM: fix kernel-doc warnings Randy Dunlap
2024-01-17 1:09 ` [PATCH 11/13] ARM: OMAP2+: fix a kernel-doc warning Randy Dunlap
2024-01-17 1:10 ` [PATCH 12/13] ARM: OMAP2+: fix kernel-doc warnings Randy Dunlap
2024-01-17 1:10 ` [PATCH 13/13] " Randy Dunlap
2024-01-17 13:13 ` [PATCH 00/13] ARM: OMAP2+: fix a bunch of " Tony Lindgren
2024-01-17 16:52 ` Randy Dunlap
2024-01-18 8:57 ` Tony Lindgren
2024-01-26 8:39 ` Tony Lindgren
2024-02-01 9:32 ` Russell King (Oracle)
2024-02-01 16:27 ` Randy Dunlap [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=1f53a83d-cae4-4223-ad47-6d1d9c80dc2b@infradead.org \
--to=rdunlap@infradead.org \
--cc=bcousson@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=patches@armlinux.org.uk \
--cc=paul@pwsan.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 read-only IMAP folder(s) and NNTP newsgroup(s).