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/4] fujitsu_init() cleanup
Date: Tue, 24 Jan 2017 22:23:41 +1030	[thread overview]
Message-ID: <20170124115341.GE4013@marvin.atrad.com.au> (raw)
In-Reply-To: <20170113131915.GA745@ozzy.nask.waw.pl>

On Fri, Jan 13, 2017 at 02:19:15PM +0100, Micha?? K??pie?? wrote:
> > It might be worth glancing through these because the resulting renames in
> > particular definitely improved the clarity of the driver:
> > 
> >   Date: Thu, 17 Sep 2009
> >   From: Alan Jenkins
> >   Subject: [PATCH 1/4] fujitsu-laptop: renames and cleanup
> >            [PATCH 2/4] fujitsu-laptop: restructure initialisation
> >            [PATCH 3/4] fujitsu-laptop: autodetect lcd interface on unknown models
> >            [PATCH 4/4] fujitsu-laptop: simplify modalias (autoload)
> 
> These subjects suggest that it makes little sense for me to duplicate
> Alan's work.  I have a lot more cleanups on my todo list, but the more I
> change, the less sense Alan's patches will make.  I guess the most
> reasonable course of action would be for you to go through Alan's series
> after all so that I will only need to send fixes for whatever he has
> missed.  Feel free to suggest otherwise, though.

That certainly seems like a good way forward.  I am now back from travel and
will try to get onto these patches as soon as possible.  Hopefully I will
have something to report soon.

Regards
  jonathan

  reply	other threads:[~2017-01-24 11:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 11:02 [PATCH 0/4] fujitsu_init() cleanup Michał Kępień
2017-01-13 11:02 ` [PATCH 1/4] platform/x86: fujitsu-laptop: simplify acpi_bus_register_driver() error handling Michał Kępień
2017-01-13 11:02 ` [PATCH 2/4] platform/x86: fujitsu-laptop: register backlight device in a separate function Michał Kępień
2017-01-13 11:02 ` [PATCH 3/4] platform/x86: fujitsu-laptop: sync backlight power status in acpi_fujitsu_hotkey_add() Michał Kępień
2017-01-13 11:02 ` [PATCH 4/4] platform/x86: fujitsu-laptop: cleanup error labels in fujitsu_init() Michał Kępień
2017-01-13 12:17 ` [PATCH 0/4] fujitsu_init() cleanup Jonathan Woithe
2017-01-13 13:19   ` Michał Kępień
2017-01-24 11:53     ` Jonathan Woithe [this message]
2017-02-03 14:06     ` Michał Kępień
2017-02-03 14:13       ` Andy Shevchenko
2017-02-04  0:44         ` Darren Hart
2017-02-04  6:21           ` Michał Kępień
2017-02-04 14:11             ` Andy Shevchenko
2017-02-27  7:19       ` Michał Kępień
2017-02-28  6:17         ` Darren Hart
2017-02-28  8:07           ` Greg Kroah-Hartman
2017-02-28  8:33             ` Michał Kępień
2017-02-28 11:24               ` Jonathan Woithe
2017-02-28 13:24                 ` Michał Kępień
2017-02-28 14:01                   ` Greg Kroah-Hartman
2017-02-28 14:40                     ` Andy Shevchenko
2017-03-01  3:19                     ` Darren Hart
2017-02-28 11:14             ` Jonathan Woithe
2017-02-28 12:33               ` Greg Kroah-Hartman

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=20170124115341.GE4013@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