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] [day] [month] [year] [list]

Message-ID: <a8e1da0806012357g229f2734v83bf06d885e61876@mail.gmail.com>
Date:	Mon, 2 Jun 2008 14:57:47 +0800
From:	"Dave Young" <hidave.darkstar@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	marcel@...tmann.org, 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

On Mon, Jun 2, 2008 at 2:50 PM, David Miller <davem@...emloft.net> wrote:
> 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.

Will do next time, thanks.

>
> Thanks.
>



-- 
---
Regards
dave
--
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/