From: Andrew Morton <akpm@linux-foundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Subject: Re: [PATCH] docs: core-api: fix broken references for div64.c and gcd.c
Date: Fri, 19 Apr 2019 13:35:56 -0700 [thread overview]
Message-ID: <20190419133556.80a049d3fbc71f0f2d594702@linux-foundation.org> (raw)
In-Reply-To: <20190419125548.2cca263d@lwn.net>
On Fri, 19 Apr 2019 12:55:48 -0600 Jonathan Corbet <corbet@lwn.net> wrote:
> > -.. kernel-doc:: lib/div64.c
> > +.. kernel-doc:: lib/math/div64.c
> > :functions: div_s64_rem div64_u64_rem div64_u64 div64_s64
> >
> > -.. kernel-doc:: lib/gcd.c
> > +.. kernel-doc:: lib/math/gcd.c
> > :export:
>
> This, of course, creates a build error in docs-next...hopefully that
> situation won't last more than a couple of weeks or so.
I'll fold this into the base patch
lib-move-mathematic-helpers-to-separate-folder.patch so there won't be
such a situation.
> Applied, thanks.
Please unapply ;)
prev parent reply other threads:[~2019-04-19 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 9:50 Mauro Carvalho Chehab
2019-04-18 21:59 ` Randy Dunlap
2019-04-18 22:51 ` Mauro Carvalho Chehab
2019-04-19 18:55 ` Jonathan Corbet
2019-04-19 20:35 ` Andrew Morton [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=20190419133556.80a049d3fbc71f0f2d594702@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rjui@broadcom.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@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
Powered by JetHome