-----Original Message-----
From: David Miller [mailto:davem@davemloft.net] 
Sent: Friday, October 30, 2009 1:29 PM
To: Kumar Gopalpet-B05799
Cc: netdev@vger.kernel.org; Fleming Andy-AFLEMING
Subject: Re: [PATCH v3 4/7] fsl_pq_mdio: Add Suport for 
etsec2.0 devices.

From: "Kumar Gopalpet-B05799" <redacted>
Date: Fri, 30 Oct 2009 12:52:29 +0530

quoted

1. The patch failure is due to the absence of following commit in
net-next-2.6 tree.
	
	commit e72701acbe0b35e52d3f04d442837c06b4e64f1c
	Author: Anton Vorontsov [off-list ref]
	Date:   Wed Oct 14 14:54:52 2009 -0700

It is in the net-next-2.6 tree, something is wrong with your clone.

We were referring to the logs shown on the gitweb.
The tree log does not show this commit. 
(search for this commit id failed)
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fdavem%2Fnet-next-2.6.git
&a=search&h=29906f6a427d2004a515ebbcdc7b28bae8f6c19c&st=commit&s=e72701a
cbe0b35e52d3f04d442837c06b4e64f1c

Whereas, the log for the file does show the commit.
http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=histo
ry;f=drivers/net/fsl_pq_mdio.c;h=6ac4648669728421b934d32646ffbb626128387
6;hb=HEAD

Why is there such a mismatch on the tree itself?

davem@sunset:~/src/GIT/net-next-2.6$ git describe 
e72701acbe0b35e52d3f04d442837c06b4e64f1c
v2.6.31-9041-ge72701a
davem@sunset:~/src/GIT/net-next-2.6$ 

Even we get this on our clone. 
However, the changes to the file itself are absent.

Shall we generate the patch series against the snapshot (which contains
the changes)? 


--

Thanks
Sandeep