linux-kernel - Re: [PATCH 1/2] staging: usbip: use interrupt safe spinlock to avoid potential deadlock.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130108055128.GA4561@kroah.com>
Date:	Mon, 7 Jan 2013 21:51:28 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Harvey Yang <harvey.huawei.yang@...il.com>
Cc:	Matt Mooney <mfm@...eddisk.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] staging: usbip: use interrupt safe spinlock to avoid
 potential deadlock.

On Tue, Jan 08, 2013 at 01:49:01PM +0800, Harvey Yang wrote:
> 
> Signed-off-by: Harvey Yang <harvey.huawei.yang@...il.com>

You need to describe _why_ you did this, not just what you did.  Why is
this needed?  What are you fixing by doing this?  Is this something that
older kernels need?  Is it something that others are seeing?

Same goes for patch 2/2 here, you have to provide a good changelog entry
in order for this to be accepted.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/