From: David Miller <davem@davemloft.net>
To: Ian.Campbell@citrix.com
Cc: jeremy@goop.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, lersek@redhat.com
Subject: Re: [PATCH v3 REPOST] xen-netfront: delay gARP until backend switches to Connected
Date: Fri, 09 Dec 2011 19:24:39 -0500 (EST) [thread overview]
Message-ID: <20111209.192439.275865894437319638.davem@davemloft.net> (raw)
In-Reply-To: <1323465781.20936.49.camel@dagon.hellion.org.uk>
From: Ian Campbell <Ian.Campbell@citrix.com>
Date: Fri, 9 Dec 2011 21:23:00 +0000
> On Fri, 2011-12-09 at 18:45 +0000, David Miller wrote:
>> 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,
>
> The referenced commit is in
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git#xen/next-2.6.32 some people call the "pvops tree" but there's no reason to expect someone outside the Xen world to know that...
>
> A better reference would have been 6b0b80ca7165 in
> git://xenbits.xen.org/people/ianc/linux-2.6.git#upstream/dom0/backend/netback-history which is the precise branch that was flattened to make f942dc2552b8, which is the upstream commit that added netback, so this change is already in upstream.
I want the commit message fixed so someone seeing the commit ID can
figure out what it actually refers to.
next prev parent reply other threads:[~2011-12-10 0:24 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
2011-12-09 21:23 ` Ian Campbell
2011-12-10 0:24 ` David Miller [this message]
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.192439.275865894437319638.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).