public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, pkrystad@codeaurora.org,
	marcel@holtmann.org, andrei.emeltchenko.news@gmail.com,
	szymon.janc@tieto.com
Subject: Re: [PATCHv4 2/2] Bluetooth: Functions for handling ERTM control fields
Date: Fri, 6 Apr 2012 19:36:08 -0300	[thread overview]
Message-ID: <20120406223608.GB2915@joana> (raw)
In-Reply-To: <20120406222935.GA2915@joana>

Hi Mat,

* Gustavo Padovan <gustavo@padovan.org> [2012-04-06 19:29:35 -0300]:

> Hi Mat,
>=20
> * Mat Martineau <mathewm@codeaurora.org> [2012-04-04 11:29:43 -0700]:
>=20
> > These functions encode or decode ERTM control fields (extended or
> > enhanced) to or from the new l2cap_ctrl structure.
> >=20
> > Acked-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
> > ---
> >  net/bluetooth/l2cap_core.c |   99 ++++++++++++++++++++++++++++++++++++=
++++++++
> >  1 file changed, 99 insertions(+)
>=20
> Both patches were applied to bluetooth-next. thanks.

net/bluetooth/l2cap_core.c:317:12: warning: =E2=80=98l2cap_seq_list_pop=E2=
=80=99 defined but not used [-Wunused-function]
net/bluetooth/l2cap_core.c:323:13: warning: =E2=80=98l2cap_seq_list_clear=
=E2=80=99 defined but not used [-Wunused-function]
net/bluetooth/l2cap_core.c:335:13: warning: =E2=80=98l2cap_seq_list_append=
=E2=80=99 defined but not used [-Wunused-function]
net/bluetooth/l2cap_core.c:780:12: warning: =E2=80=98__pack_enhanced_contro=
l=E2=80=99 defined but not used [-Wunused-function]
net/bluetooth/l2cap_core.c:823:12: warning: =E2=80=98__pack_extended_contro=
l=E2=80=99 defined but not used [-Wunused-function]

So, this is not good, we can't just throw unused code here, they will gener=
ate
warnings and I'll get complains from maintainers above me if I merge this.
Both patches were reverted.

	Gustavo

      reply	other threads:[~2012-04-06 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 18:29 [PATCHv4 0/2] ERTM state machine changes, part 1 Mat Martineau
2012-04-04 18:29 ` [PATCHv4 1/2] Bluetooth: Add the l2cap_seq_list structure for tracking frames Mat Martineau
2012-04-04 20:30   ` Marcel Holtmann
2012-04-04 18:29 ` [PATCHv4 2/2] Bluetooth: Functions for handling ERTM control fields Mat Martineau
2012-04-04 20:31   ` Marcel Holtmann
2012-04-06 14:48     ` Mat Martineau
2012-04-06 22:29   ` Gustavo Padovan
2012-04-06 22:36     ` Gustavo Padovan [this message]

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=20120406223608.GB2915@joana \
    --to=gustavo@padovan.org \
    --cc=andrei.emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mathewm@codeaurora.org \
    --cc=pkrystad@codeaurora.org \
    --cc=szymon.janc@tieto.com \
    /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