linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org,
	Steven Honeyman <stevenhoneyman@gmail.com>
Subject: Re: [PATCH] i8k: Add support for Dell Latitude E6440
Date: Fri, 24 Oct 2014 20:44:59 +0200	[thread overview]
Message-ID: <201410242044.59305@pali> (raw)
In-Reply-To: <20141018104056.GA8607@kroah.com>

[-- Attachment #1: Type: Text/Plain, Size: 855 bytes --]

On Saturday 18 October 2014 12:40:56 Greg Kroah-Hartman wrote:
> On Sat, Oct 18, 2014 at 12:23:39AM +0200, Pali Rohár wrote:
> > On Friday 10 October 2014 22:56:55 Guenter Roeck wrote:
> > > On 10/10/2014 02:12 AM, Pali Rohár wrote:
> > > > Dell Latitude E6440 needs same settings as E6540.
> > > > 
> > > > Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
> > > 
> > > Acked-by: Guenter Roeck <linux@roeck-us.net>
> > 
> > Greg, Arnd: PING
> > 
> > Can you apply also this patch for E6440? Support for E6540
> > is already in linus tree:
> > 06c88b0d7ad87540405aea7f91d98ef43be04c95
> 
> I can't apply anything to my trees until 3.18-rc1 is out, but
> will do this after that happens.
> 
> thanks,
> 
> greg k-h

Hi Greg!
I want to remind you patches, because v3.18-rc1 was released.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-10-24 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10  9:12 [PATCH] i8k: Add support for Dell Latitude E6440 Pali Rohár
2014-10-10 20:56 ` Guenter Roeck
2014-10-17 22:23   ` Pali Rohár
2014-10-18 10:40     ` Greg Kroah-Hartman
2014-10-24 18:44       ` Pali Rohár [this message]
2014-10-31 23:22         ` Pali Rohár

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=201410242044.59305@pali \
    --to=pali.rohar@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=stevenhoneyman@gmail.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;
as well as URLs for NNTP newsgroup(s).