From: Dan Carpenter <dan.carpenter@oracle.com>
To: Darren Hart <dvhart@infradead.org>
Cc: "Gabriele Mazzotta" <gabriele.mzt@gmail.com>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
kbuild@01.org, platform-driver-x86@vger.kernel.org,
"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: [patch] dell-laptop: fix kbd_timeout handling
Date: Thu, 4 Dec 2014 11:30:17 +0300 [thread overview]
Message-ID: <20141204083017.GV5048@mwanda> (raw)
In-Reply-To: <20141203073324.GA8568@vmdeb7>
On Tue, Dec 02, 2014 at 11:33:25PM -0800, Darren Hart wrote:
>
> Dan, any objection to Pali rolling this into another revision?
No problem, that's fine.
regards,
dan carpenter
next prev parent reply other threads:[~2014-12-04 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1417597233.14672.2.camel@Pali-Nokia-N900>
2014-12-03 10:01 ` [patch] dell-laptop: fix kbd_timeout handling Dan Carpenter
2014-12-03 7:33 ` Darren Hart
2014-12-04 8:30 ` Dan Carpenter [this message]
2014-12-04 9:42 ` Pali Rohár
2014-12-04 10:58 ` Gabriele Mazzotta
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=20141204083017.GV5048@mwanda \
--to=dan.carpenter@oracle.com \
--cc=dvhart@infradead.org \
--cc=gabriele.mzt@gmail.com \
--cc=kbuild@01.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@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