LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: eeepc-laptop rfkill, stupid question #4
Date: Tue, 4 Nov 2008 13:48:32 -0200	[thread overview]
Message-ID: <20081104134832.6c596d54@doriath.conectiva> (raw)
In-Reply-To: <20081103163311.GA2417@khazad-dum.debian.net>

Em Mon, 3 Nov 2008 14:33:11 -0200
Henrique de Moraes Holschuh <hmh@hmh.eng.br> escreveu:

| On Mon, 03 Nov 2008, Matthew Garrett wrote:
| > On Mon, Nov 03, 2008 at 01:02:29PM -0200, Henrique de Moraes Holschuh wrote:
| > > Right now, you should still rfkill_force_state().  Please wait for an hour
| > > or two while I clean up that broken resume handling, and I will tell you for
| > > sure.
| > 
| > Cool. I'll hold off posting my cleanups until then in that case.
| 
| Ok, two bugs reproduced, the fixes are ready and tested, and I will be
| sending it now to linux-wireless.  You're in the CC, so you will get them.
| 
| I will also need to send patches for -stable, as the ones for mainline won't
| apply to -stable.

 Great.

 Do the patches have anything to do with the problem I have reported?

 Rafael has opened a bugzilla ticket for it:

http://bugzilla.kernel.org/show_bug.cgi?id=11928

-- 
Luiz Fernando N. Capitulino

  parent reply	other threads:[~2008-11-04 15:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 17:09 eeepc-laptop rfkill, stupid question #4 and 5 Alan Jenkins
2008-10-31 17:11 ` Matthew Garrett
2008-10-31 17:27   ` Alan Jenkins
2008-10-31 20:54     ` Alan Jenkins
2008-11-02  4:00       ` Henrique de Moraes Holschuh
2008-11-02 11:17         ` eeepc-laptop rfkill, stupid question #4 Alan Jenkins
2008-11-02 13:06           ` Matthew Garrett
2008-11-02 13:25             ` Alan Jenkins
2008-11-02 13:26               ` Matthew Garrett
2008-11-03 14:47               ` Henrique de Moraes Holschuh
2008-11-03 14:16             ` Henrique de Moraes Holschuh
2008-11-03 14:18               ` Matthew Garrett
2008-11-03 14:29                 ` Alan Jenkins
2008-11-03 14:51                   ` Henrique de Moraes Holschuh
2008-11-03 14:55                     ` Matthew Garrett
2008-11-03 15:02                       ` Henrique de Moraes Holschuh
2008-11-03 15:08                         ` Matthew Garrett
2008-11-03 16:33                           ` Henrique de Moraes Holschuh
2008-11-03 18:00                             ` rfkill, stupid question #6 Alan Jenkins
2008-11-03 19:06                               ` Henrique de Moraes Holschuh
2008-11-04 15:48                             ` Luiz Fernando N. Capitulino [this message]
2008-11-04 15:57                               ` eeepc-laptop rfkill, stupid question #4 Alan Jenkins
2008-11-02  3:46   ` eeepc-laptop rfkill, stupid question #4 and 5 Henrique de Moraes Holschuh
2008-11-02  9:21     ` Matthew Garrett

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=20081104134832.6c596d54@doriath.conectiva \
    --to=lcapitulino@mandriva.com.br \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --subject='Re: eeepc-laptop rfkill, stupid question #4' \
    /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

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).