From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Pull request: bluetooth-next-2.6 2009-06-08
Date: Tue, 09 Jun 2009 17:25:20 +0200 [thread overview]
Message-ID: <1244561120.3068.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20090608.234701.51739911.davem@davemloft.net>
Hi Dave,
> >> > these are the Bluetooth patches for the 2.6.31 kernel release. They are
> >> > mostly cleanups and removal of dead/unused code. However we do integrate
> >> > with the re-written RFKILL subsystem now. This gives us proper soft-kill
> >> > support for internal and external devices.
> >>
> >> Where is the attached patch we talked about the other week
> >> so that your pull requests get tracked in patchwork?
> >
> > I thought you wanted it only for the net-2.6 pull requests and not for
> > the net-next-2.6 ones. Do you want them for both?
>
> If the diff is small enough to fit on the list, do them for both.
>
> If it's a lot of new stuff and huge, you can pass on it.
no problem. Do you want me to re-send this one or are you planning to
pull it like it is.
I am trying to cleanup the Marvell Bluetooth driver and get it compiler
warning free so that can be merged too. If you want me to re-send it
with patches attached, then I might do it before the weekend to include
that driver. Otherwise please pull this one.
Regards
Marcel
next prev parent reply other threads:[~2009-06-09 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 13:05 Pull request: bluetooth-next-2.6 2009-06-08 Marcel Holtmann
2009-06-08 21:24 ` David Miller
2009-06-09 5:42 ` Marcel Holtmann
2009-06-09 6:47 ` David Miller
2009-06-09 15:25 ` Marcel Holtmann [this message]
2009-06-10 0:55 ` David Miller
2009-06-11 13:05 ` Marcel Holtmann
2009-06-11 13:08 ` David Miller
2009-06-11 14:07 ` Marcel Holtmann
2009-06-11 13:08 ` 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=1244561120.3068.17.camel@localhost.localdomain \
--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).