linux-kernel - Re: [RFC 0/2] remove BT references from TI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110121182749.GE2400@joana>
Date:	Fri, 21 Jan 2011 16:27:49 -0200
From:	"Gustavo F. Padovan" <padovan@...fusion.mobi>
To:	Pavan Savoy <pavan_savoy@...y.com>
Cc:	marcel@...tmann.org, linux-kernel@...r.kernel.org,
	linux-bluetooth@...r.kernel.org
Subject: Re: [RFC 0/2] remove BT references from TI_ST

Hi Pavan,

* Pavan Savoy <pavan_savoy@...y.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/