[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111209.192439.275865894437319638.davem@davemloft.net>
Date: Fri, 09 Dec 2011 19:24:39 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: Ian.Campbell@...rix.com
Cc: lersek@...hat.com, konrad.wilk@...cle.com, jeremy@...p.org,
xen-devel@...ts.xensource.com,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 REPOST] xen-netfront: delay gARP until backend
switches to Connected
From: Ian Campbell <Ian.Campbell@...rix.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@...hat.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists