linux-kernel - Re: [PATCH v2 1/2] docs/core-api: memory-allocation: remove uses of c:func:

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 24 Oct 2019 12:49:57 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Chris Packham <Chris.Packham@...iedtelesis.co.nz>,
        "corbet@....net" <corbet@....net>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] docs/core-api: memory-allocation: remove uses of
 c:func:

On 10/24/19 12:39 PM, Chris Packham wrote:
> Hi Jon,
> 
> On Thu, 2019-10-24 at 12:02 -0600, Jonathan Corbet wrote:
>> On Wed, 23 Oct 2019 10:14:37 +1300
>> Chris Packham <chris.packham@...iedtelesis.co.nz> wrote:
>>
>>> These are no longer needed as the documentation build will automatically
>>> add the cross references.
>>>
>>> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
>>> ---
>>>
>>>  Documentation/core-api/memory-allocation.rst | 49 +++++++++-----------
>>>  1 file changed, 23 insertions(+), 26 deletions(-)
>>
>> So I can't get this patch to apply, and I can't even figure out why.  If
>> you take the patch from the list, can you apply it to a docs-next (or
>> mainline) branch?
>>
> 
> I think it might be dependent on my other typo fix patch[1]. I'll
> rebase to v5.4-rc4 and send as a series of 3. Sorry for the hassle.
> 
> --
> [1] 
> https://lore.kernel.org/lkml/20191021003833.15704-1-chris.packham@alliedtelesis.co.nz/
> 
> 
>> Thanks,
>>
>> jon

patch tells me:
patch: **** malformed patch at line 84: -:c:func:`kmem_cache_destroy`.

-- 
~Randy