|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [GIT/PATCH v5] xen network backend driver
To: |
Ian.Campbell@xxxxxxxxxxxxx |
Subject: |
[Xen-devel] Re: [GIT/PATCH v5] xen network backend driver |
From: |
David Miller <davem@xxxxxxxxxxxxx> |
Date: |
Mon, 14 Mar 2011 13:23:55 -0700 (PDT) |
Cc: |
jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, mirqus@xxxxxxxxx, romieu@xxxxxxxxxxxxx, bhutchings@xxxxxxxxxxxxxx, shemminger@xxxxxxxxxx |
Delivery-date: |
Mon, 14 Mar 2011 13:23:56 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<1300131040.32696.23.camel@xxxxxxxxxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<1300112879.17339.2162.camel@xxxxxxxxxxxxxxxxxxxxxx> <1300128035.2584.6.camel@bwh-desktop> <1300131040.32696.23.camel@xxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Mon, 14 Mar 2011 19:30:40 +0000
> On Mon, 2011-03-14 at 18:40 +0000, Ben Hutchings wrote:
>> I know you have asked for this to be pulled, in order to retain its
>> history, but I'm not sure that David Miller will do this unless the
>> driver is at least buildable at each stage in the history. (However,
>> given that the driver wouldn't be enabled before it's added, I'm not
>> sure it matters in this case.)
>
> I think it should be, at least from the second commit onwards (modulo
> any mistakes made in the past).
I don't want to retain all of that history, there are so many broken
points in the history that the only thing you can do is go back and
add Kconfig commits to depend the driver upon BROKEN, and that in effect
changes the history devalueing it even further.
I just want one patch that adds the driver in it's most current state,
and that's all.
Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|