From: David Miller <davem@davemloft.net>
To: Paul.Durrant@citrix.com
Cc: netdev@vger.kernel.org, wei.liu2@citrix.com
Subject: Re: Reversion of "xen-netback: create a debugfs node for hash information"
Date: Fri, 07 Oct 2016 23:48:56 -0400 (EDT) [thread overview]
Message-ID: <20161007.234856.1725862322997622606.davem@davemloft.net> (raw)
In-Reply-To: <cbedcf0845fb449892e415e2a1c69a40@AMSPEX02CL03.citrite.net>
From: Paul Durrant <Paul.Durrant@citrix.com>
Date: Fri, 7 Oct 2016 09:50:04 +0000
> I notice that you have made the above reversion of commit c0c64c15
> (debugfs node) due to a build failure, despite the failure being
> caused by commit 0364a882 (switch to threaded irq) which was made
> subsequently. I assume you want me to re-spin a new patch for the
> debugfs node to fix the build problem?
Yes, that's probably what you need to do.
Thanks.
prev parent reply other threads:[~2016-10-08 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 9:50 Reversion of "xen-netback: create a debugfs node for hash information" Paul Durrant
2016-10-08 3:48 ` David Miller [this message]
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=20161007.234856.1725862322997622606.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Paul.Durrant@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
/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).