X86 platform drivers
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@just42.net>
To: Micha?? K??pie?? <kernel@kempniu.pl>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/4][RFC] fujitsu-laptop: clean ups from Alan Jenkins
Date: Tue, 31 Jan 2017 08:53:23 +1030	[thread overview]
Message-ID: <20170130222323.GA3343@marvin.atrad.com.au> (raw)
In-Reply-To: <20170130142817.GA11056@ozzy.nask.waw.pl>

Hi Michael

On Mon, Jan 30, 2017 at 03:28:17PM +0100, Micha?? K??pie?? wrote:
> > This series of patches for the fujitsu-laptop driver was originally
> > submitted by Alan Jenkins in September 2009.  For various reasons which are
> > entirely my fault they were never acted upon.  To remedy this they have been
> > ported to the linux-platform-drivers-x86 git tree and compile-tested. 
> > Consequently this submission is a work in progress and is posted for
> > comments and feedback.
> 
> Thanks for posting these patches.  You wrote they were compile-tested,
> could you please shed some light on which git branch did you base them
> on?

Obviously the wrong one. :-(  I can't recall the git URL off-hand but will
check this evening when I am at my development box.

> Darren's testing branch in its current state does not work for me, neither
> does Linus' master.

Which of these should I use to fit in with your work (and what is the
respective URL)?  I'm not fussed either way.

On a related note, it's probably time I worked git out properly.  Do you
know of any documentation which illustrates the workflow which allows git to
track a multi-patch series like this?  It is, from what I have picked up,
capable of generating the patches ready for emailing automatically but I
don't know how it does this.  I haven't managed to find anything helpful so
would appreciate any pointers you might be able to give.  Currently I'm
doing it all manually, which doesn't scale.  Up until this series
fujitsu-laptop hasn't had a significant patch series like this so I haven't
needed to seriously pursue it.

> I will definitely take a look and submit my comments, though I might not
> have the time to do so until somewhere in the middle of next week.  I
> guess patches that have been queued for the past 7 years or so will not
> mind another week ;)

Precisely. :-)  That's fine.  Hopefully by then I'll have it based to the
right git repo.

Regards
  jonathan

  reply	other threads:[~2017-01-30 22:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 12:43 [PATCH 0/4][RFC] fujitsu-laptop: clean ups from Alan Jenkins Jonathan Woithe
2017-01-30 14:28 ` Michał Kępień
2017-01-30 22:23   ` Jonathan Woithe [this message]
2017-02-02 14:16     ` Michał Kępień
2017-01-31 11:59   ` Jonathan Woithe
2017-01-31 12:05     ` Andy Shevchenko
2017-01-31 12:29       ` Jonathan Woithe

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=20170130222323.GA3343@marvin.atrad.com.au \
    --to=jwoithe@just42.net \
    --cc=kernel@kempniu.pl \
    --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