From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Small Bluetooth fix for 2.6.27-rc6
Date: Fri, 12 Sep 2008 04:59:10 +0200 [thread overview]
Message-ID: <1221188350.6695.7.camel@californication> (raw)
In-Reply-To: <20080911.195147.81650729.davem@davemloft.net>
Hi Dave,
> > > > > > Please pull from
> > > > > >
> > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master
> > > > >
> > > > > You did your work against Linus's tree, so I can't pull this,
> > > > > it will bring in tons of irrelevant stuff into net-2.6.
> > > > >
> > > > > Please send me pull requests using net-2.6 as your base.
> > > >
> > > > I re-based the tree on net-2.6 now. Please pull.
> > >
> > > Pulled, thanks.
> >
> > I assume you want me to queue the compiler warning fix for the next
> > merge window, right?
>
> Which one?
the one for this warning:
CC [M] net/bluetooth/af_bluetooth.o
net/bluetooth/af_bluetooth.c:60: warning: ‘bt_key_strings’ defined but not used
net/bluetooth/af_bluetooth.c:71: warning: ‘bt_slock_key_strings’ defined but not used
It is not a new one, it just got ignored by everybody and now I got
annoyed enough to fix it. I just don't know what's that take on compiler
warning fixes after the merge window. Do we want them or not. I can
queue this up for 2.6.28.
Regards
Marcel
next prev parent reply other threads:[~2008-09-12 2:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 3:56 Small Bluetooth fix for 2.6.27-rc6 Marcel Holtmann
2008-09-12 2:01 ` David Miller
2008-09-12 2:11 ` Marcel Holtmann
2008-09-12 2:12 ` David Miller
2008-09-12 2:15 ` Marcel Holtmann
2008-09-12 2:51 ` David Miller
2008-09-12 2:59 ` Marcel Holtmann [this message]
2008-09-12 3:03 ` David Miller
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=1221188350.6695.7.camel@californication \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).