public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@just42.net>
To: Micha?? K??pie?? <kernel@kempniu.pl>
Cc: Darren Hart <dvhart@infradead.org>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] fujitsu-laptop: acpi_fujitsu_notify() cleanup
Date: Tue, 17 Jan 2017 21:49:35 +1030	[thread overview]
Message-ID: <20170117111935.GC22965@marvin.atrad.com.au> (raw)
In-Reply-To: <20170117110735.2543-1-kernel@kempniu.pl>

Hi Michael

On Tue, Jan 17, 2017 at 12:07:33PM +0100, Micha?? K??pie?? wrote:
> Here are two minor cleanups for acpi_fujitsu_notify() that I came up
> with while preparing the sparse keymap migration.  They can be reviewed
> and applied independently of the other series for fujitsu-laptop I
> posted recently.

Ok.

> Jonathan, I decided to post this after re-reading the subjects of Alan
> Jenkins' cleanup patches - I believe his work should not overlap with
> this series.  In case it does, feel free to ignore or postpone this
> series.  Also, there is no rush to apply these, they are just a base for
> the upcoming sparse keymap patches.

I understand.  Thanks for posting these.  Like the earlier patch series they
look fairly innoculous but I would like to run them up on my hardware just
to be sure.  I do not have the hardware with me at linux.conf.au so this can
only be done early next week.  Apologies for the delay.

Regards
  jonathan

  parent reply	other threads:[~2017-01-17 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 11:07 [PATCH 0/2] fujitsu-laptop: acpi_fujitsu_notify() cleanup Michał Kępień
2017-01-17 11:07 ` [PATCH 1/2] platform/x86: fujitsu-laptop: decrease indentation in acpi_fujitsu_notify() Michał Kępień
2017-01-17 11:07 ` [PATCH 2/2] platform/x86: fujitsu-laptop: simplify brightness key event generation logic Michał Kępień
2017-01-17 11:19 ` Jonathan Woithe [this message]
2017-02-03 14:08   ` [PATCH 0/2] fujitsu-laptop: acpi_fujitsu_notify() cleanup Michał Kępień

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=20170117111935.GC22965@marvin.atrad.com.au \
    --to=jwoithe@just42.net \
    --cc=dvhart@infradead.org \
    --cc=kernel@kempniu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --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