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: Fri, 29 Jan 2010 08:17:00 +0100 [thread overview]
Message-ID: <1264749420.5591.248.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,
I push the tree as soon as I get to Seattle. Just between flights right
now.
Regards
Marcel
next prev parent reply other threads:[~2010-01-29 7:17 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 [this message]
2010-02-03 15:35 ` 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=1264749420.5591.248.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;
as well as URLs for NNTP newsgroup(s).