From: Jonathan Corbet <corbet@lwn.net>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "rppt@linux.ibm.com" <rppt@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"willy@infradead.org" <willy@infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] docs/core-api: memory-allocation: remove uses of c:func:
Date: Thu, 24 Oct 2019 14:57:12 -0600 [thread overview]
Message-ID: <20191024145712.165556c1@lwn.net> (raw)
In-Reply-To: <1ddbd3045d6a989b32065c0bd5b3a3c0ef525953.camel@alliedtelesis.co.nz>
On Thu, 24 Oct 2019 20:51:23 +0000
Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> When I do actually get a series that applies to docs-next it'll
> conflict with 59bb47985c1d ("mm, sl[aou]b: guarantee
> natural alignment for kmalloc(power-of-two)") in Linus's tree.
Alternatively, if I sync up to -rc4, does the problem go away? I should
be able to explain that to Linus without too much trouble...
Thanks,
jon
next prev parent reply other threads:[~2019-10-24 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:50 [PATCH v3 0/3] docs/core-api: memory-allocation: minor cleanups Chris Packham
2019-10-24 19:50 ` [PATCH v3 1/3] docs/core-api: memory-allocation: fix typo Chris Packham
2019-10-24 19:50 ` [PATCH v3 2/3] docs/core-api: memory-allocation: remove uses of c:func: Chris Packham
2019-10-24 20:29 ` Jonathan Corbet
2019-10-24 20:51 ` Chris Packham
2019-10-24 20:57 ` Jonathan Corbet [this message]
2019-10-24 21:07 ` Chris Packham
2019-10-25 20:26 ` Mike Rapoport
2019-10-24 19:50 ` [PATCH v3 3/3] docs/core-api: memory-allocation: mention size helpers Chris Packham
2019-10-24 20:16 ` [PATCH v3 0/3] docs/core-api: memory-allocation: minor cleanups Matthew Wilcox
2019-10-25 20:25 ` Mike Rapoport
2019-10-29 10:46 ` 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=20191024145712.165556c1@lwn.net \
--to=corbet@lwn.net \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--cc=willy@infradead.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 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).