linux-kernel - Re: [PATCH] bluetooth: rfcomm_dev_state

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: <20080601.235018.266140984.davem@davemloft.net>
Date:	Sun, 01 Jun 2008 23:50:18 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	marcel@...tmann.org
Cc:	hidave.darkstar@...il.com, arjan@...ux.intel.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-bluetooth@...r.kernel.org
Subject: Re: [PATCH] bluetooth: rfcomm_dev_state_change deadlock fix

From: Marcel Holtmann <marcel@...tmann.org>
Date: Mon, 2 Jun 2008 08:15:03 +0200

> Acked-by: Marcel Holtmann <marcel@...tmann.org>

Applied, but I had to add the commit header string to the two SHA ID
commit references.  Please always provide the header line text as well
as the SHA ID when referencing commits because when backporting or
putting the patch into a different tree the SHA ID will be different
and people will have a terrible time trying to find the commits you
are referring to.

Thanks.
--
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/