netdev - Re: [GIT PULL] xen-netfront driver updates for 2.6.36

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100803.163700.71134702.davem@davemloft.net>
Date:	Tue, 03 Aug 2010 16:37:00 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeremy@...p.org
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Xen-devel@...ts.xensource.com, dongxiao.xu@...el.com
Subject: Re: [GIT PULL] xen-netfront driver updates for 2.6.36

From: Jeremy Fitzhardinge <jeremy@...p.org>
Date: Tue, 03 Aug 2010 11:39:45 -0700

> Here's a git branch with some updates to the Xen netfront driver,
> which add a new "smartpoll" mode to the netfront backend protocol,
> which is basically equivalent to interrupt mitigation.  This merges
> cleanly with current linux-next (it previously just had a small
> constification conflict).
> 
> Do you want to take this via the net tree, or are you OK with me
> submitting them directly?

Well from my perspective:

1) It's too late to put into my tree because the merge window has
   already started.  If you want me to include this you should have
   asked me to pull it in days if not weeks ago.

2) Your tree is absolutely not in a state I can pull it.  It has lots
   of completely unrelated commits which are not in net-next-2.6 which
   in no way should I be pulling into my tree.

When you want me to take changes, your tree should be based upon mine.
And when I pull from your tree I should get only your specific
xen-netfront driver changes, and nothing more.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html