netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: hidave.darkstar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	oliver-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org,
	alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH]bluetooth: rfcomm_init bug fix
Date: Tue, 04 Aug 2009 10:01:46 -0700	[thread overview]
Message-ID: <1249405306.3094.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20090803.211136.00343745.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

Hi Dave,

> >> do you mind at least waiting for an ACK from my side. I haven't even
> >> looked at the final patch.
> > 
> > Sure, I haven't pushed it out yet, so now's your chance :)
> 
> Grumble, I accidently pushed my net-2.6 queue out before you
> had a chance to reply, sorry :-(

not a big deal. Just have to send a cleanup patch. The patch itself is
fine, but from a style perspective it is different than everything else
in the Bluetooth subsystem and I would have liked to fix that before
pushing it. I wait with that for 2.6.32 since it is not important.

The other Dave, please send patches to linux-bluetooth only and lets
follow the normal path to get them merged into Linus' tree. Skipping
bluetooth-2.6 is not an option. You have to use the same process than
everybody else.

Regards

Marcel

  parent reply	other threads:[~2009-08-04 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 14:26 [PATCH]bluetooth: rfcomm_init bug fix Dave Young
2009-08-03 20:29 ` David Miller
     [not found]   ` <20090803.132924.151782729.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-08-03 23:54     ` Marcel Holtmann
2009-08-04  2:19       ` David Miller
     [not found]         ` <20090803.191916.75688176.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-08-04  4:11           ` David Miller
     [not found]             ` <20090803.211136.00343745.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-08-04 17:01               ` Marcel Holtmann [this message]
     [not found]                 ` <1249405306.3094.18.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-08-05  5:16                   ` Dave Young
     [not found]                     ` <a8e1da0908042216u16037395k96cce0746baa504e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-05 15:35                       ` Marcel Holtmann
2009-08-05 16:31                         ` David Miller
     [not found]                           ` <20090805.093124.170466311.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-08-05 17:03                             ` 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=1249405306.3094.18.camel@localhost.localdomain \
    --to=marcel-kz+m5ild9qbg9huczpvpmw@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=hidave.darkstar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oliver-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.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).