netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Martin Habets <mhabets@solarflare.com>
Cc: Julio Faracco <jcfaracco@gmail.com>,
	netdev@vger.kernel.org, davem@davemloft.net, jasowang@redhat.com,
	virtualization@lists.linux-foundation.org, dnmendes76@gmail.com
Subject: Re: [net-next V3 1/2] netdev: pass the stuck queue to the timeout handler
Date: Tue, 3 Dec 2019 01:46:08 -0500	[thread overview]
Message-ID: <20191203014532-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <c2cddeea-8a6e-f0b9-1fde-7d2a29538518@solarflare.com>

On Wed, Nov 27, 2019 at 03:11:51PM +0000, Martin Habets wrote:
> Your @work correctly identifies that the drivers/net/ethernet/sfc drivers need patching, but the actual patches for them are missing.
> Please add those. Makes me wonder if any other files are missing patches.
> 
> Martin

Good point, pattern was missing _ in variable name. Will repost a
fixed version.


  parent reply	other threads:[~2019-12-03  6:46 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 [this message]
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
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=20191203014532-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=mhabets@solarflare.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).