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,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Mackerras <paulus@samba.org>,
Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ricardo Ribalda Delgado <ribalda@kernel.org>,
Luca Ceresoli <luca@lucaceresoli.net>,
dmaengine@vger.kernel.org,
Matthias Maennich <maennich@google.com>,
Harry Wei <harryxiyou@gmail.com>,
x86@kernel.org, ecryptfs@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
target-devel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Johannes Berg <johannes.berg@intel.com>,
Jacopo Mondi <jacopo@jmondi.org>, Tyler Hicks <code@tyhicks.com>,
Vinod Koul <vkoul@kernel.org>,
Alex Shi <alex.shi@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-scsi@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
netdev@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linuxppc-dev@lists.ozlabs.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs
Date: Fri, 20 Mar 2020 17:10:20 -0600 [thread overview]
Message-ID: <20200320171020.78f045c5@lwn.net> (raw)
In-Reply-To: <cover.1584716446.git.mchehab+huawei@kernel.org>
On Fri, 20 Mar 2020 16:11:01 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> This small series address a regression caused by a new patch at
> docs-next (and at linux-next).
I don't know how I missed that mess, sorry. I plead distracting times or
something like that. Heck, I think I'll blame everything on the plague
for at least the next few weeks.
Anyway, I've applied this, thanks for cleaning it up.
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>,
linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Mackerras <paulus@samba.org>,
Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ricardo Ribalda Delgado <ribalda@kernel.org>,
Luca Ceresoli <luca@lucaceresoli.net>,
dmaengine@vger.kernel.org,
Matthias Maennich <maennich@google.com>,
Harry Wei <harryxiyou@gmail.com>,
x86@kernel.org, ecryptfs@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
target-devel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Johannes Berg <johannes.berg@intel.com>,
Jacopo Mondi <jacopo@jmondi.org>, Tyler Hicks <>
Subject: Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs
Date: Fri, 20 Mar 2020 17:10:20 -0600 [thread overview]
Message-ID: <20200320171020.78f045c5@lwn.net> (raw)
In-Reply-To: <cover.1584716446.git.mchehab+huawei@kernel.org>
On Fri, 20 Mar 2020 16:11:01 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> This small series address a regression caused by a new patch at
> docs-next (and at linux-next).
I don't know how I missed that mess, sorry. I plead distracting times or
something like that. Heck, I think I'll blame everything on the plague
for at least the next few weeks.
Anyway, I've applied this, thanks for cleaning it up.
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Ricardo Ribalda Delgado <ribalda@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
target-devel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
linux-scsi@vger.kernel.org, x86@kernel.org,
Tyler Hicks <code@tyhicks.com>, Ingo Molnar <mingo@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Jacopo Mondi <jacopo@jmondi.org>,
Luca Ceresoli <luca@lucaceresoli.net>,
Johannes Berg <johannes.berg@intel.com>,
ecryptfs@vger.kernel.org, Matthias Maennich <maennich@google.com>,
dmaengine@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>, Harry Wei <harryxiyou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>
Subject: Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs
Date: Fri, 20 Mar 2020 17:10:20 -0600 [thread overview]
Message-ID: <20200320171020.78f045c5@lwn.net> (raw)
In-Reply-To: <cover.1584716446.git.mchehab+huawei@kernel.org>
On Fri, 20 Mar 2020 16:11:01 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> This small series address a regression caused by a new patch at
> docs-next (and at linux-next).
I don't know how I missed that mess, sorry. I plead distracting times or
something like that. Heck, I think I'll blame everything on the plague
for at least the next few weeks.
Anyway, I've applied this, thanks for cleaning it up.
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>,
linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Mackerras <paulus@samba.org>,
Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ricardo Ribalda Delgado <ribalda@kernel.org>,
Luca Ceresoli <luca@lucaceresoli.net>,
dmaengine@vger.kernel.org,
Matthias Maennich <maennich@google.com>,
Harry Wei <harryxiyou@gmail.com>,
x86@kernel.org, ecryptfs@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
target-devel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Johannes Berg <johannes.berg@intel.com>,
Jacopo Mondi <jacopo@jmondi.org>, Tyler Hicks <code@tyhicks.com>,
Vinod Koul <vkoul@kernel.org>,
Alex Shi <alex.shi@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-scsi@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
netdev@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linuxppc-dev@lists.ozlabs.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs
Date: Fri, 20 Mar 2020 23:10:20 +0000 [thread overview]
Message-ID: <20200320171020.78f045c5@lwn.net> (raw)
In-Reply-To: <cover.1584716446.git.mchehab+huawei@kernel.org>
On Fri, 20 Mar 2020 16:11:01 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> This small series address a regression caused by a new patch at
> docs-next (and at linux-next).
I don't know how I missed that mess, sorry. I plead distracting times or
something like that. Heck, I think I'll blame everything on the plague
for at least the next few weeks.
Anyway, I've applied this, thanks for cleaning it up.
jon
next prev parent reply other threads:[~2020-03-20 23:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 15:11 [PATCH v2 0/2] Don't generate thousands of new warnings when building docs Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` [PATCH v2 1/2] docs: prevent warnings due to autosectionlabel Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` Mauro Carvalho Chehab
2020-03-20 15:11 ` [PATCH v2 2/2] docs: conf.py: avoid thousands of duplicate label warning on Sphinx Mauro Carvalho Chehab
2020-03-20 23:10 ` Jonathan Corbet [this message]
2020-03-20 23:10 ` [PATCH v2 0/2] Don't generate thousands of new warnings when building docs Jonathan Corbet
2020-03-20 23:10 ` Jonathan Corbet
2020-03-20 23:10 ` Jonathan Corbet
2020-04-16 10:05 ` Jani Nikula
2020-04-16 10:05 ` Jani Nikula
2020-04-16 10:05 ` Jani Nikula
2020-04-16 10:05 ` Jani Nikula
2020-04-07 3:46 ` Michael Ellerman
2020-04-07 3:46 ` Michael Ellerman
2020-04-07 3:46 ` Michael Ellerman
2020-04-07 3:46 ` Michael Ellerman
2020-04-08 11:40 ` Mauro Carvalho Chehab
2020-04-08 11:40 ` Mauro Carvalho Chehab
2020-04-08 11:40 ` Mauro Carvalho Chehab
2020-04-08 11:40 ` Mauro Carvalho Chehab
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=20200320171020.78f045c5@lwn.net \
--to=corbet@lwn.net \
--cc=alex.shi@linux.alibaba.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=code@tyhicks.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=hpa@zytor.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luca@lucaceresoli.net \
--cc=madhuparnabhowmik04@gmail.com \
--cc=maennich@google.com \
--cc=martin.petersen@oracle.com \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ribalda@kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vkoul@kernel.org \
--cc=x86@kernel.org \
/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.