From: Darren Hart <dvhart@infradead.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asus-nb-wmi: Add wapf4 quirk for the X550VB
Date: Fri, 24 Oct 2014 22:11:16 -0700 [thread overview]
Message-ID: <20141025051116.GA53394@vmdeb7> (raw)
In-Reply-To: <20141022123252.GC1876@redhat.com>
On Wed, Oct 22, 2014 at 02:32:52PM +0200, Stanislaw Gruszka wrote:
Hi Stanislaw,
> As reported here: http://bugzilla.redhat.com/show_bug.cgi?id=1089731#c23
> the X550VB needs wapf=4 too.
>
Please provide a self sufficient changelog, that, independent of a bugzilla
link, provides enough information to understand what the problem is, and why
this is the correct fix.
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-10-25 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 12:32 [PATCH] asus-nb-wmi: Add wapf4 quirk for the X550VB Stanislaw Gruszka
2014-10-25 5:11 ` Darren Hart [this message]
2014-10-26 10:23 ` [PATCH v2] " Stanislaw Gruszka
2014-10-28 4:14 ` Darren Hart
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=20141025051116.GA53394@vmdeb7 \
--to=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sgruszka@redhat.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