[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9F4C7D19E8361D4C94921B95BE08B81BA08FCA@zin33exm22.fsl.freescale.net>
Date: Tue, 22 Dec 2009 10:32:49 +0530
From: "Kumar Gopalpet-B05799" <B05799@...escale.com>
To: "Michael Guntsche" <mike@...loops.com>
Cc: "netdev" <netdev@...r.kernel.org>
Subject: RE: [BUG] 2.6.33-rc1 gianfar error message
>-----Original Message-----
>From: Michael Guntsche [mailto:mike@...loops.com]
>Sent: Monday, December 21, 2009 10:09 PM
>To: Kumar Gopalpet-B05799
>Cc: netdev
>Subject: Re: [BUG] 2.6.33-rc1 gianfar error message
>
>On 21 Dec 09 14:19, Kumar Gopalpet-B05799 wrote:
>> Michael,
>>
>> Kindly try the following changes at your side and let me know the
>> results. I couldn't test this as I don't have any TSEC
>device with me.
><snip>
>
>Your patch did not apply to vanilla 2.6.32-rc1 at all. I patched the
>code myself and up to now I do not see any error messages. Uptime is at
>33 minutes, without the patch the error message appeared immediately
>after booting.
>
I am sorry about that, I forgot to mention that my patch was against
net-next-2.6 tree.
>Just for my understanding. Is the first diff part of the fix as well?
>With this change the FCB is only removed if there are padded bytes, why
>would this make a difference here?
>
Yes, the first diff portion is not required.
Also, if you confirm that the changes are working fine.
I will generate a clean patch and send it out.
Thanks for reporting it and testing it out.
--
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