Greg KH wrote:
On Mon, Mar 28, 2011 at 09:57:22AM +0800, DDD wrote:
Frank Pan wrote:
What is the commit id you are refering to?  Also, if you could provide
the backport, that you have tested to work properly, that would be best.
The commit id is:
fb82c0ff27b2c40c6f7a3d1a94cafb154591fa80

I've tested this on the xen pv-ops 2.6.32-next branch. It works fine.
If this is not enough, I can test that on the vanilla 2.6.32.y branch.
Yep, That patch is simple and easy to backport to 2.6.32, Just need
to patch it on kernel/kgdb.c instead of kernel/debug/gdbstub.c as
Frank said. But it is better to test your patch on vanilla 2.6.32.y
branch. :-)

Someone needs to provide me with the tested and backported patch before
I can apply it.

Done.

Could you apply the attachment patch which was based on 2.6.32.y to stable tree?

Or I need to use git-sendmail to send a independent patch mail to you?

BR,
Dongdong

Attachment: 0001-kgdb-repair-gdbstub-to-match-the-gdbserial-protocol.patch
Description: application/mbox

_______________________________________________
stable mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/stable

Reply via email to