netdev - Re: [PATCH 0/2] doc: net: ieee802154: move from plain text to rst

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190301.170155.327420277076342114.davem@davemloft.net>
Date:   Fri, 01 Mar 2019 17:01:55 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     stefan@...enfreihafen.org
Cc:     corbet@....net, netdev@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-wpan@...r.kernel.org
Subject: Re: [PATCH 0/2] doc: net: ieee802154: move from plain text to rst

From: Stefan Schmidt <stefan@...enfreihafen.org>
Date: Wed, 27 Feb 2019 22:20:58 +0100

> Hello Jon.
> 
> On 27.02.19 21:18, Jonathan Corbet wrote:
>> On Wed, 27 Feb 2019 20:59:12 +0100
>> Stefan Schmidt <stefan@...enfreihafen.org> wrote:
>> 
>>> The patches are based on net-next, but they only touch the networking book so I
>>> would not expect and trouble. From what I have seen they would go through
>>> Jonathan's tree after being acked by Dave? If you want this patches against a
>>> different tree let me know.
>> 
>> Usually Dave takes networking documentation patches directly, so that is
>> what I would expect here.
> 
> OK, so I got that wrong. Works for me. Dave, you want to take them
> directly, if nothing else comes up during review, or should I apply them
> to my tree and send them with the next pull request?

I'll take them, thanks.