From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Bluetooth update for 2.6
Date: Sat, 08 Jul 2006 00:54:30 +0200 [thread overview]
Message-ID: <1152312870.3693.24.camel@localhost> (raw)
In-Reply-To: <20060707.001745.07431025.davem@davemloft.net>
Hi Dave,
> > this is the second part of pending updates of the Bluetooth subsystem
> > for the upcoming 2.6.18 kernel. A couple of them are only coding style
> > cleanups which I failed to submit for the previous kernel release. They
> > slipped somehow. The rest is driver model integration stuff. Please push
> > them to Linus as soon as possible.
>
> The merge window for 2.6.18 is closed, so you will need to eliminate
> things like code cleanups and other non-bugfixes.
yes, I saw that, but actually these patches were meant to get to you
before the merge window closed. I failed to prepare the tree, because I
lost remote access to one of my machines were I unfortunately had queued
all of these patches. Do you think Linus will make an exception?
Regards
Marcel
next prev parent reply other threads:[~2006-07-07 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 20:09 Bluetooth update for 2.6 Marcel Holtmann
2006-07-07 7:17 ` David Miller
2006-07-07 22:54 ` Marcel Holtmann [this message]
2006-07-07 23:14 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 21:49 Marcel Holtmann
2006-07-12 22:34 ` David Miller
2006-07-14 14:38 Marcel Holtmann
2006-07-18 17:08 ` Marcel Holtmann
2006-09-21 19:47 Marcel Holtmann
2006-09-26 10:46 ` Marcel Holtmann
2006-09-28 5:58 ` David Miller
2006-09-28 21:14 ` Marcel Holtmann
2006-09-28 22:30 ` David Miller
2006-10-15 16:10 Marcel Holtmann
2006-10-16 6:13 ` David Miller
2006-10-20 7:49 Marcel Holtmann
2006-10-20 8:16 ` David Miller
2006-11-19 0:34 Marcel Holtmann
2006-11-21 0:14 ` 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=1152312870.3693.24.camel@localhost \
--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).