From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jcfaracco@gmail.com, netdev@vger.kernel.org, jasowang@redhat.com,
virtualization@lists.linux-foundation.org, dnmendes76@gmail.com
Subject: Re: [net-next V3 0/2] drivers: net: virtio_net: implement
Date: Wed, 27 Nov 2019 14:58:45 -0500 [thread overview]
Message-ID: <20191127145831-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191127.105956.842685942160278820.davem@davemloft.net>
On Wed, Nov 27, 2019 at 10:59:56AM -0800, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@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.
next prev parent reply other threads:[~2019-11-27 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 20:06 [net-next V3 0/2] drivers: net: virtio_net: implement Julio Faracco
2019-11-26 20:06 ` [net-next V3 1/2] netdev: pass the stuck queue to the timeout handler Julio Faracco
2019-11-27 15:11 ` Martin Habets
2019-11-27 15:46 ` Julio Faracco
2019-12-03 7:04 ` Michael S. Tsirkin
2019-12-03 6:46 ` Michael S. Tsirkin
2019-11-26 20:06 ` [net-next V3 2/2] drivers: net: virtio_net: Implement a dev_watchdog handler Julio Faracco
2019-11-27 11:41 ` Michael S. Tsirkin
2019-11-26 22:06 ` [net-next V3 0/2] drivers: net: virtio_net: implement David Miller
2019-11-27 11:38 ` Michael S. Tsirkin
2019-11-27 11:40 ` Michael S. Tsirkin
2019-11-27 18:59 ` David Miller
2019-11-27 19:58 ` Michael S. Tsirkin [this message]
2019-12-03 7:05 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191127145831-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=dnmendes76@gmail.com \
--cc=jasowang@redhat.com \
--cc=jcfaracco@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).