Linux Virtualization - Nov 2019 - [net-next V3 0/2] drivers: net: virtio_net: implement

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.

Thanks,

-- 
MST

On Wed, Nov 27, 2019 at 06:38:39AM -0500, Michael S. Tsirkin
wrote:
> 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.

I just mean 1/2 btw. I think 2/2 might still need some work.
> Thanks,
> 
> -- 
> MST

From: "Michael S. Tsirkin" <mst at redhat.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.

On Wed, Nov 27, 2019 at 10:59:56AM -0800, David Miller
wrote:
> From: "Michael S. Tsirkin" <mst at redhat.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.