From: Joe Perches <joe@perches.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"Gustavo F. Padovan" <padovan@profusion.mobi>,
"David S. Miller" <davem@davemloft.net>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to bt_err/bt_info
Date: Fri, 17 Feb 2012 10:12:22 -0800 [thread overview]
Message-ID: <1329502342.584.4.camel@joe2Laptop> (raw)
In-Reply-To: <20120217094110.GB12814@x220>
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?
next prev parent reply other threads:[~2012-02-17 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 7:32 [PATCH V2 0/3] bluetooth: Shrink object size, use current logging style Joe Perches
2012-02-17 7:32 ` [PATCH V2 1/3] bluetooth: Add logging functions bt_info and bt_err Joe Perches
2012-02-17 8:37 ` Marcel Holtmann
2012-02-17 9:38 ` Johan Hedberg
2012-02-17 7:32 ` [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to bt_err/bt_info Joe Perches
2012-02-17 8:40 ` Marcel Holtmann
2012-02-17 9:41 ` Johan Hedberg
2012-02-17 18:12 ` Joe Perches [this message]
2012-02-17 7:32 ` [PATCH V2 3/3] bluetooth: Convert BT_DBG to pr_debug Joe Perches
2012-02-17 8:42 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1329502342.584.4.camel@joe2Laptop \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).