From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Pavan Savoy <pavan_savoy@sify.com>
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 0/2] remove BT references from TI_ST
Date: Fri, 21 Jan 2011 16:27:49 -0200 [thread overview]
Message-ID: <20110121182749.GE2400@joana> (raw)
In-Reply-To: <AANLkTimGNjfMtf+6XBMfKHo_F0sEnAJVdWjobfxDWoe7@mail.gmail.com>
Hi Pavan,
* Pavan Savoy <pavan_savoy@sify.com> [2011-01-21 23:10:28 +0530]:
> >> > If this is alright, I will send out a modified patch with updated
> >> > subject to lkml/Greg for linux-next.
> >
> > Ok. Go ahead. Then tell me when I'll be able to apply your patch. (I need to
> > have the core modifications in my tree first). Or I just ack the patch and it
> > finds its way to mainline through Greg's tree.
>
> Yes, I will post a patch to lkml against linux-next to greg KH, and
> based on that send a
> separate patch to linux-bluetooth for the btwilink..
Actually send everything to Greg KH, will work out better. Otherwise you will
have to one release cycle to merge it here (until the other patches reach my
tree). Then I just Ack it.
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-01-21 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 10:59 [RFC 0/2] remove BT references from TI_ST pavan_savoy
2011-01-04 10:59 ` [RFC 1/2] drivers:misc:ti-st: change protocol parse logic pavan_savoy
2011-01-04 10:59 ` [RFC 2/2] Bluetooth: btwilink driver pavan_savoy
2011-01-21 17:57 ` Gustavo F. Padovan
2011-01-19 18:26 ` [RFC 0/2] remove BT references from TI_ST Pavan Savoy
2011-01-21 17:18 ` Gustavo F. Padovan
2011-01-21 17:40 ` Pavan Savoy
2011-01-21 18:27 ` Gustavo F. Padovan [this message]
2011-01-21 21:10 ` Pavan Savoy
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=20110121182749.GE2400@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavan_savoy@sify.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