[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805291940.09563.IvDoorn@gmail.com>
Date: Thu, 29 May 2008 19:40:09 +0200
From: Ivo van Doorn <ivdoorn@...il.com>
To: Henrique de Moraes Holschuh <hmh@....eng.br>
Cc: linux-kernel@...r.kernel.org, Thomas Renninger <trenn@...e.de>,
Dmitry Torokhov <dtor@...l.ru>
Subject: Re: [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions (v2)
On Thursday 29 May 2008, Henrique de Moraes Holschuh wrote:
> On Thu, 29 May 2008, Ivo van Doorn wrote:
> > On Thursday 29 May 2008, Henrique de Moraes Holschuh wrote:
> > > On Thu, 29 May 2008, Ivo van Doorn wrote:
> > > > > This version better documents *_RFKILL_ALL. Is it good enough for an
> > > > > ACK for patch 14 of 15?
> > > >
> > > > Yes, you can put my ack on patch 14.
> > > > Thanks for the documentation update. :)
> > >
> > > Then, this entire batch is ready for merging. Now, if only Len would
> > > come back from wherever he disappeared to, in order to merge the two
> > > thinkpad-acpi patches, I could send it to netdev for merge.
> >
> > Actually, I believe the correct merge order would through wireless-dev,
> > which means the patches should go to John Linville and linux-wireless in the CC.
>
> Noted. At merge time (which will be as soon as the thinkpad-acpi
> changes hit mainline), I will send them to you, John, and
> linux-wireless.
>
> Unless you want me to send them all right now to linux-wireless to see
> if there are any comments?
Well why wait with merging it into wireless-dev until thinkpad-acpi is merged?
I don't think there are real dependencies other then the SW_RFKILL_ALL define.
Perhaps you could send the rfkill patches with SW_RADIO instead of SW_RFKILL_ALL
and make the rename after the thinkpad and rfkill series have both been merged.
That would probably be the fastest route for this patch series.
Ivo
--
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/
Powered by blists - more mailing lists