From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Alexandre Bounine <alex.bou9@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>,
Evgeniy Polyakov <zbr@ioremap.net>,
Hans de Goede <hdegoede@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Jon Maloy <jmaloy@redhat.com>, Kees Cook <keescook@chromium.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Mark Gross <mgross@linux.intel.com>,
Matt Porter <mporter@kernel.crashing.org>,
Maxime Ripard <mripard@kernel.org>,
Maximilian Luz <luzmaximilian@gmail.com>,
Mike Rapoport <rppt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Richard Gong <richard.gong@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Tony Luck <tony.luck@intel.com>, Will Drewry <wad@chromium.org>,
Ying Xue <ying.xue@windriver.com>,
dri-devel@lists.freedesktop.org, linux-fsdevel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH v6 00/16] Fix several bad kernel-doc markups
Date: Thu, 21 Jan 2021 12:09:54 -0700 [thread overview]
Message-ID: <20210121120954.5ed4c3b2@lwn.net> (raw)
In-Reply-To: <cover.1610610937.git.mchehab+huawei@kernel.org>
On Thu, 14 Jan 2021 09:04:36 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> 1) 10 remaining fixup patches from the series I sent back on Dec, 1st:
>
> parport: fix a kernel-doc markup
> rapidio: fix kernel-doc a markup
> fs: fix kernel-doc markups
> pstore/zone: fix a kernel-doc markup
> firmware: stratix10-svc: fix kernel-doc markups
> connector: fix a kernel-doc markup
> lib/crc7: fix a kernel-doc markup
> memblock: fix kernel-doc markups
> w1: fix a kernel-doc markup
> selftests: kselftest_harness.h: partially fix kernel-doc markups
A week later none of these have shown up in linux-next, so I went ahead
and applied the set.
Thanks,
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
platform-driver-x86@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
Evgeniy Polyakov <zbr@ioremap.net>,
Richard Gong <richard.gong@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
Mark Gross <mgross@linux.intel.com>,
Anton Vorontsov <anton@enomsg.org>,
Jakub Kicinski <kuba@kernel.org>,
Matt Porter <mporter@kernel.crashing.org>,
Kees Cook <keescook@chromium.org>,
Hans de Goede <hdegoede@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Tony Luck <tony.luck@intel.com>, Will Drewry <wad@chromium.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Jon Maloy <jmaloy@redhat.com>,
Alexandre Bounine <alex.bou9@gmail.com>,
tipc-discussion@lists.sourceforge.net,
Colin Cross <ccross@android.com>,
Ying Xue <ying.xue@windriver.com>,
linux-fsdevel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Maximilian Luz <luzmaximilian@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v6 00/16] Fix several bad kernel-doc markups
Date: Thu, 21 Jan 2021 12:09:54 -0700 [thread overview]
Message-ID: <20210121120954.5ed4c3b2@lwn.net> (raw)
In-Reply-To: <cover.1610610937.git.mchehab+huawei@kernel.org>
On Thu, 14 Jan 2021 09:04:36 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> 1) 10 remaining fixup patches from the series I sent back on Dec, 1st:
>
> parport: fix a kernel-doc markup
> rapidio: fix kernel-doc a markup
> fs: fix kernel-doc markups
> pstore/zone: fix a kernel-doc markup
> firmware: stratix10-svc: fix kernel-doc markups
> connector: fix a kernel-doc markup
> lib/crc7: fix a kernel-doc markup
> memblock: fix kernel-doc markups
> w1: fix a kernel-doc markup
> selftests: kselftest_harness.h: partially fix kernel-doc markups
A week later none of these have shown up in linux-next, so I went ahead
and applied the set.
Thanks,
jon
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-21 19:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:04 [PATCH v6 00/16] Fix several bad kernel-doc markups Mauro Carvalho Chehab
2021-01-14 8:04 ` Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 01/16] parport: fix a kernel-doc markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 02/16] rapidio: fix kernel-doc a markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 03/16] fs: fix kernel-doc markups Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 04/16] pstore/zone: fix a kernel-doc markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 05/16] firmware: stratix10-svc: fix kernel-doc markups Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 06/16] connector: fix a kernel-doc markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 07/16] lib/crc7: " Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 08/16] memblock: fix kernel-doc markups Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 09/16] w1: fix a kernel-doc markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 10/16] selftests: kselftest_harness.h: partially fix kernel-doc markups Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 11/16] scripts: kernel-doc: validate kernel-doc markup with the actual names Mauro Carvalho Chehab
2021-01-14 10:11 ` kernel test robot
2021-01-14 10:11 ` kernel test robot
2021-01-14 10:16 ` kernel test robot
2021-01-14 10:16 ` kernel test robot
2021-01-18 20:35 ` Jonathan Corbet
2021-01-19 7:43 ` Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 12/16] net: tip: fix a couple kernel-doc markups Mauro Carvalho Chehab
2021-01-14 15:59 ` Jon Maloy
2021-01-14 18:34 ` Jakub Kicinski
2021-01-14 21:22 ` Johannes Berg
2021-01-14 8:04 ` [PATCH v6 13/16] net: cfg80211: fix a kerneldoc markup Mauro Carvalho Chehab
2021-01-14 8:04 ` [PATCH v6 14/16] reset: core: fix a kernel-doc markup Mauro Carvalho Chehab
2021-01-14 8:25 ` Philipp Zabel
2021-01-14 8:04 ` [PATCH v6 15/16] drm: drm_crc: " Mauro Carvalho Chehab
2021-01-14 8:04 ` Mauro Carvalho Chehab
2021-01-14 8:06 ` Simon Ser
2021-01-14 8:06 ` Simon Ser
2021-01-14 14:13 ` Simon Ser
2021-01-14 14:13 ` Simon Ser
2021-01-14 8:04 ` [PATCH v6 16/16] platform/surface: aggregator: " Mauro Carvalho Chehab
2021-01-14 14:53 ` Maximilian Luz
2021-01-18 18:20 ` Hans de Goede
2021-01-21 19:09 ` Jonathan Corbet [this message]
2021-01-21 19:09 ` [PATCH v6 00/16] Fix several bad kernel-doc markups Jonathan Corbet
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=20210121120954.5ed4c3b2@lwn.net \
--to=corbet@lwn.net \
--cc=airlied@linux.ie \
--cc=alex.bou9@gmail.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jmaloy@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luzmaximilian@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mchehab+huawei@kernel.org \
--cc=mgross@linux.intel.com \
--cc=mporter@kernel.crashing.org \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=richard.gong@linux.intel.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tony.luck@intel.com \
--cc=tzimmermann@suse.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wad@chromium.org \
--cc=ying.xue@windriver.com \
--cc=zbr@ioremap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.