[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9F4C7D19E8361D4C94921B95BE08B81B950364@zin33exm22.fsl.freescale.net>
Date: Thu, 29 Oct 2009 16:03:30 +0530
From: "Kumar Gopalpet-B05799" <B05799@...escale.com>
To: "David Miller" <davem@...emloft.net>
Cc: <netdev@...r.kernel.org>, <avorontsov@...mvista.com>
Subject: RE: [PATCH v2 4/7] fsl_pq_mdio: Add Suport for etsec2.0 devices.
>-----Original Message-----
>From: David Miller [mailto:davem@...emloft.net]
>Sent: Thursday, October 29, 2009 3:46 PM
>To: Kumar Gopalpet-B05799
>Cc: netdev@...r.kernel.org; avorontsov@...mvista.com
>Subject: Re: [PATCH v2 4/7] fsl_pq_mdio: Add Support for
>etsec2.0 devices.
>
>From: "Kumar Gopalpet-B05799" <B05799@...escale.com>
>Date: Thu, 29 Oct 2009 15:41:22 +0530
>
>> This is the tree I generated the patches against initially.
>> The initial set of patches were generated against this tree:
>>
>(http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>> )
>>
>> Can you please confirm that the above tree is correct.
>
>Yes.
Thank you. I cloned this tree again about 2 hours ago (and updated it 5
mins ago as well).
git describe:
v2.6.32-rc3-464-gb37b62f
The last commit is: b37b62fea1d1bf68ca51818f8eb1035188efd030
>
>> The patches sent by me applies cleanly to the above mentioned
>> net-next-2.6 tree.
>
>It may have applied cleanly when you sent them, but by the
>time I applied them it didn't.
The PATCH v2 series applied cleanly to the above clone.
>
>Resend a fresh patch set against a fresh net-next-2.6 checkout
>and let's see what happens :-)
Ok. But there is NO change to the patch set.
--
Thanks
Sandeep
--
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
Powered by blists - more mailing lists