netdev - Re: [PATCH net-next] doc: document MSG

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: <20170901144424.72f9c9e9@redhat.com>
Date:   Fri, 1 Sep 2017 14:44:24 +0200
From:   Jesper Dangaard Brouer <brouer@...hat.com>
To:     Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc:     brouer@...hat.com, netdev@...r.kernel.org, davem@...emloft.net,
        Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next] doc: document MSG_ZEROCOPY

On Thu, 31 Aug 2017 17:00:13 -0400
Willem de Bruijn <willemdebruijn.kernel@...il.com> wrote:

> +More Info
> +---------
> +
> +Much of this document was derived from a longer paper presented at
> +netdev 2.1. For more in-depth information see that paper and talk,
> +the excellent reporting over at LWN.net or read the original code.
> +
> +  paper, slides, video
> +    https://netdevconf.org/2.1/session.html?debruijn
> +
> +  LWN article
> +    https://lwn.net/Articles/726917/
> +
> +  patchset
> +    [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
> +    https://lwn.net/Articles/730010/
> +    https://www.spinics.net/lists/netdev/msg447552.html

IMHO I think it would be better to use the type links also used in the
git log.  If you look at the kernel git log, then the "Link:" tag have
the form: http://lkml.kernel.org/r/
And you can simply append the "Message-Id:" email header.

In this case the link would be:
  http://lkml.kernel.org/r/20170803202945.70750-1-willemdebruijn.kernel@gmail.com
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer