From: Peter Feuerer <peter@piie.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lenb@kernel.org, linux-kernel@vger.kernel.org, andi@lisas.de,
petkovbb@googlemail.com
Subject: Re: [PATCH] Acerhdf: fix fan control for AOA150 model
Date: Tue, 14 Jul 2009 09:07:08 +0200 [thread overview]
Message-ID: <cone.1247555228.809275.18208.1000@arca> (raw)
In-Reply-To: 20090713160614.521c932a.akpm@linux-foundation.org
Hi Andrew,
Andrew Morton writes:
> On Sun, 12 Jul 2009 23:21:04 +0200
> Peter Feuerer <peter@piie.net> wrote:
…
>> Changed:
>> o Applied Borislav Petkov's patch (convert the fancmd[] array to a real
>> struct thus disambiguating command handling and making code more readable.)
>> o Added BIOS product to BIOS table as AOA110 and AOA150 have
>> different register values
>> o Added force_product parameter to allow forcing different
>> product
>> o fixed linker warning caused by "acerhdf_drv" not being named
>> "acerhdf_driver"
>>
>> Signed-off-by: Peter Feuerer <peter@piie.net>
>
> It looks like this work should have been presented as four separate patches.
I'm not that familiar with git in general and sending patches yet. How do
you do this in an effective way? Diffing all changes via git and then
splitting up the "all-in-one-patch" to four smaller patches manually?
> Inclusion of Borislav's Signed-off-by: would be appropriate.
I wasn't sure whether I'm allowed to send the patch with his signed-off, as
there were other things in the patch, he didn't review. But next time I'll
send such a patch splitted up and then it's clear.
Thanks for your honesty,
kind regards,
--peter
next prev parent reply other threads:[~2009-07-14 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 21:21 [PATCH] Acerhdf: fix fan control for AOA150 model Peter Feuerer
2009-07-13 23:06 ` Andrew Morton
2009-07-14 7:07 ` Peter Feuerer [this message]
2009-07-15 15:44 ` Borislav Petkov
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=cone.1247555228.809275.18208.1000@arca \
--to=peter@piie.net \
--cc=akpm@linux-foundation.org \
--cc=andi@lisas.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.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