public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	lrodriguez@atheros.com
Subject: Re: ath3k for 2.6.33-rc6
Date: Wed, 03 Feb 2010 07:35:03 -0800	[thread overview]
Message-ID: <1265211303.31341.123.camel@localhost.localdomain> (raw)
In-Reply-To: <20100128215828.GE8069@bombadil.infradead.org>

Hi Luis,

> > sorry about the confusion the other day about overstepping you for a
> > push for ath3k into 2.6.33, I'd like to clarify that was not my
> > intention, I made the incorrect assumption you received my ping but
> > didn't care to push it. I wanted to see what you think its OK to push
> > ath3k into the next cycle for the 2.6.33-rc6 release.
> > 
> > Thanks,
> 
> Marcel, was wondering if you have given this some thought. Thanks,

that driver ended up in Linus' tree now. So just for future reference
for everybody. After -rc2, I only wanna have fixes. There should be no
reason why a driver couldn't be ready in time before the merge window.
And approx 2-3 weeks grace period after it for new drivers seems to be
more than enough to get them cleaned and merged.

Regards

Marcel



      parent reply	other threads:[~2010-02-03 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23  0:52 ath3k for 2.6.33-rc6 Luis R. Rodriguez
2010-01-28 21:58 ` Luis R. Rodriguez
2010-01-29  7:17   ` Marcel Holtmann
2010-02-03 15:35   ` Marcel Holtmann [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=1265211303.31341.123.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mcgrof@bombadil.infradead.org \
    --cc=mcgrof@gmail.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