* ath3k for 2.6.33-rc6
@ 2010-01-23 0:52 Luis R. Rodriguez
2010-01-28 21:58 ` Luis R. Rodriguez
0 siblings, 1 reply; 4+ messages in thread
From: Luis R. Rodriguez @ 2010-01-23 0:52 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: linux-bluetooth
Hey Marcel,
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,
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath3k for 2.6.33-rc6
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
0 siblings, 2 replies; 4+ messages in thread
From: Luis R. Rodriguez @ 2010-01-28 21:58 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Marcel Holtmann, linux-bluetooth, holtmann, lrodriguez
On Fri, Jan 22, 2010 at 04:52:29PM -0800, Luis R. Rodriguez wrote:
> Hey Marcel,
>
> 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,
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath3k for 2.6.33-rc6
2010-01-28 21:58 ` Luis R. Rodriguez
@ 2010-01-29 7:17 ` Marcel Holtmann
2010-02-03 15:35 ` Marcel Holtmann
1 sibling, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2010-01-29 7:17 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Luis R. Rodriguez, linux-bluetooth, lrodriguez
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,
I push the tree as soon as I get to Seattle. Just between flights right
now.
Regards
Marcel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath3k for 2.6.33-rc6
2010-01-28 21:58 ` Luis R. Rodriguez
2010-01-29 7:17 ` Marcel Holtmann
@ 2010-02-03 15:35 ` Marcel Holtmann
1 sibling, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2010-02-03 15:35 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Luis R. Rodriguez, linux-bluetooth, lrodriguez
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-02-03 15:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).