linux-kernel - Re: [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to bt_err/bt

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: <1329502342.584.4.camel@joe2Laptop>
Date:	Fri, 17 Feb 2012 10:12:22 -0800
From:	Joe Perches <joe@...ches.com>
To:	Johan Hedberg <johan.hedberg@...il.com>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	"Gustavo F. Padovan" <padovan@...fusion.mobi>,
	"David S. Miller" <davem@...emloft.net>,
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to
 bt_err/bt_info

On Fri, 2012-02-17 at 11:41 +0200, Johan Hedberg wrote:
> Patches 2/3 and 3/3 have never actually made it to the linux-bluetooth
> list (I've never seen them and they're not visible in the archives
> either). Doing the split like Marcel proposes would probably solve the
> issue since I'm guessing the large message size is to blame.

Hi Johan.

I'm not subscribed to linux-bluetooth.

linux-bluetooth is a vger list so I would expect
the maximum message size to be no different than
lkml though.  These messages did get through to
netdev and lkml.

http://patchwork.ozlabs.org/patch/141748/
http://patchwork.ozlabs.org/patch/141749/

You're not listed as a bluetooth maintainer.
Should you be?

Do you want the original patch set sent directly
to you?

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