From: David Miller <davem@davemloft.net>
To: lersek@redhat.com
Cc: ian.campbell@citrix.com, konrad.wilk@oracle.com, jeremy@goop.org,
xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 REPOST] xen-netfront: delay gARP until backend switches to Connected
Date: Fri, 09 Dec 2011 13:45:14 -0500 (EST) [thread overview]
Message-ID: <20111209.134514.2071890208094978847.davem@davemloft.net> (raw)
In-Reply-To: <1323430738-3798-1-git-send-email-lersek@redhat.com>
From: Laszlo Ersek <lersek@redhat.com>
Date: Fri, 9 Dec 2011 12:38:58 +0100
> These two together provide complete ordering. Sub-condition (1) is
> satisfied by pvops commit 43223efd9bfd.
I don't see this commit in Linus's tree, so I doubt it's valid for
me to apply this as a bug fix to my 'net' tree since the precondition
pvops commit isn't upstream as far as I can tell.
Where did you intend me to apply this patch, and how did you expect
the dependent commit to make it's way into the tree so that this
fix is complete?
BTW, you should always explicitly specificy the answers to all the
questions in the previous paragraph, otherwise (like right now) we
go back and forth wasting time establishing these facts.
The way to say which tree the patch is intended for is to specify
it in the Subject like, f.e. "[PATCH net-next v3 REPOST] ..."
next prev parent reply other threads:[~2011-12-09 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 11:38 [PATCH v3 REPOST] xen-netfront: delay gARP until backend switches to Connected Laszlo Ersek
2011-12-09 18:45 ` David Miller [this message]
2011-12-09 21:23 ` Ian Campbell
2011-12-10 0:24 ` David Miller
2011-12-11 11:48 ` [PATCH net-next v4] " Laszlo Ersek
2012-01-02 14:50 ` Jan Beulich
2012-01-02 16:54 ` Laszlo Ersek
2012-01-02 17:04 ` Jan Beulich
2012-01-02 17:14 ` Laszlo Ersek
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=20111209.134514.2071890208094978847.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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).