linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	Corentin Chary <corentincj@iksaif.net>
Subject: Re: [PATCH] Revert "rfkill: remove dead code"
Date: Mon, 13 Aug 2012 14:47:49 -0400	[thread overview]
Message-ID: <20120813184749.GC10529@tuxdriver.com> (raw)
In-Reply-To: <CAMz9Wg8eMTJcmd5tcxBURP3Rmuu4siEFTBDqW1aK8rqdZ8utqA@mail.gmail.com>

Is this all sorted?  Is this patch going through the platform tree?

On Thu, Jul 26, 2012 at 02:19:23PM +0800, AceLan Kao wrote:
> Dear Julian,
> 
> Yes, I have said that the asus-wmi patch needs this commit
> and CC'd the asus-wmi maintainer, Corentin Chary, here in this rfkill patch.
> 
> Best regards,
> AceLan Kao.
> 
> 2012/7/26 Julian Calaby <julian.calaby@gmail.com>:
> > Hi AceLan,
> >
> > On Thu, Jul 26, 2012 at 3:55 PM, AceLan Kao <acelan.kao@canonical.com> wrote:
> >> Dear Julian,
> >>
> >> I just submitted a patch to platform-x86 for asus-wmi.
> >> And the patch needs to use rfkill_set_led_trigger_name() function
> >> to bind the wlan led to rfkill event.
> >
> > That's what I wanted to know.
> >
> > I assume that you've added a note to the ASUS-WMI patch so people know
> > that it needs this one first. (I can't see it here so I don't know)
> >
> > Thanks,
> >
> > --
> > Julian Calaby
> >
> > Email: julian.calaby@gmail.com
> > Profile: http://www.google.com/profiles/julian.calaby/
> > .Plan: http://sites.google.com/site/juliancalaby/
> 
> 
> 
> -- 
> Chia-Lin Kao(AceLan)
> http://blog.acelan.idv.tw/
> E-Mail: acelan.kaoATcanonical.com (s/AT/@/)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-08-13 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26  1:51 [PATCH] Revert "rfkill: remove dead code" AceLan Kao
2012-07-26  5:25 ` Julian Calaby
2012-07-26  5:55   ` AceLan Kao
2012-07-26  6:09     ` Julian Calaby
2012-07-26  6:19       ` AceLan Kao
2012-08-13 18:47         ` John W. Linville [this message]
2012-08-14  0:33           ` AceLan Kao
2012-08-20  2:11             ` AceLan Kao
2012-08-20 10:33               ` Johannes Berg
2012-08-21 18:35                 ` John W. Linville

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=20120813184749.GC10529@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=acelan.kao@canonical.com \
    --cc=corentincj@iksaif.net \
    --cc=johannes@sipsolutions.net \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).