From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: dnmendes76@gmail.com, netdev@vger.kernel.org,
jcfaracco@gmail.com, virtualization@lists.linux-foundation.org
Subject: Re: [net-next V3 0/2] drivers: net: virtio_net: implement
Date: Wed, 27 Nov 2019 06:38:35 -0500 [thread overview]
Message-ID: <20191127063624-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191126.140630.1195989367614358026.davem@davemloft.net>
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
WARNING: multiple messages have this Message-ID (diff)
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 06:38:35 -0500 [thread overview]
Message-ID: <20191127063624-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191126.140630.1195989367614358026.davem@davemloft.net>
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
next prev parent reply other threads:[~2019-11-27 11:38 UTC|newest]
Thread overview: 28+ 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-26 20:06 ` 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 7:04 ` Michael S. Tsirkin
2019-11-27 15:46 ` Julio Faracco
2019-12-03 6:46 ` 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-27 11:41 ` Michael S. Tsirkin
2019-11-26 20:06 ` Julio Faracco
2019-11-26 22:06 ` [net-next V3 0/2] drivers: net: virtio_net: implement David Miller
2019-11-26 22:06 ` David Miller
2019-11-26 22:06 ` David Miller
2019-11-27 11:38 ` Michael S. Tsirkin [this message]
2019-11-27 11:38 ` Michael S. Tsirkin
2019-11-27 11:40 ` Michael S. Tsirkin
2019-11-27 11:40 ` Michael S. Tsirkin
2019-11-27 18:59 ` David Miller
2019-11-27 18:59 ` David Miller
2019-11-27 19:58 ` Michael S. Tsirkin
2019-11-27 19:58 ` Michael S. Tsirkin
2019-12-03 7:05 ` Michael S. Tsirkin
2019-12-03 7:05 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2019-11-26 20:06 Julio Faracco
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=20191127063624-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=dnmendes76@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.