netdev - Re: [net-next V3 0/2] drivers: net: virtio

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: <20191127145831-mutt-send-email-mst@kernel.org>
Date:   Wed, 27 Nov 2019 14:58:45 -0500
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     David Miller <davem@...emloft.net>
Cc:     jcfaracco@...il.com, netdev@...r.kernel.org, jasowang@...hat.com,
        virtualization@...ts.linux-foundation.org, dnmendes76@...il.com
Subject: Re: [net-next V3 0/2] drivers: net: virtio_net: implement

On Wed, Nov 27, 2019 at 10:59:56AM -0800, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@...hat.com>
> Date: Wed, 27 Nov 2019 06:38:35 -0500
> 
> > On Tue, Nov 26, 2019 at 02:06:30PM -0800, David Miller wrote:
> >> 
> >> net-next is closed
> > 
> > Could you merge this early when net-next reopens though?
> > This way I don't need to keep adding drivers to update.
> 
> It simply needs to be reposted this as soon as net-next opens back up.
> 
> I fail to understand even what special treatment you want given to
> a given change, it doesn't make any sense.  We have a process for
> doing this, it's simple, it's straightforward, and is fair to
> everyone.
> 
> Thanks.

Will do, thanks.