public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Éric Piel" <Eric.Piel@tremplin-utc.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Samu Onkalo <samu.p.onkalo@nokia.com>,
	daniel@caiaq.de, pavel@ucw.cz, linux-kernel@vger.kernel.org,
	lm-sensors@lm-sensors.org
Subject: Re: [PATCH v2 00/10] LIS3: Feature updates and corrections
Date: Mon, 16 Nov 2009 21:37:24 +0100	[thread overview]
Message-ID: <4B01B804.6070809@tremplin-utc.net> (raw)
In-Reply-To: <20091116120327.7dd04a0d.akpm@linux-foundation.org>

Op 16-11-09 21:03, Andrew Morton schreef:
> On Sun, 15 Nov 2009 17:01:34 +0100
> __ric Piel<eric.piel@tremplin-utc.net>  wrote:
:
>> Andrew, maybe you could already queue the first 5 patches, as they all
>> look fine and are fixing bugs. So we are sure they are there for 2.6.33
>> :-) The rest of the patch series is useful but just "new feature" and
>> some need more work.
>
> OK, I merged the five.
>
> We could sneak some/all of them into 2.6.32 I guess, if you think
> that's warranted?
Well, if it's not too late, it would be worthy, as they are fixing bugs, 
some of them actually affecting users. At least the first 4 should be 
very safe.

> The ones which were From:yourself were missing Samu's Signed-off-by:.
> I added it.
Thanks
>
> "[PATCH v2 04/10] lis3: fix show rate for 8 bits chips" has a poor
> changelog.  "fix with 8 bits sensors".  It failed to tell us what the
> bug was, what its user-visible effects were, how it was fixed.
Yes, I actually resent it with a better changelog yesterday:
http://lkml.org/lkml/2009/11/15/91

I should have highlighted it in my previous email. Could you pick this 
one instead?

Thanks,
Eric

  reply	other threads:[~2009-11-16 20:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 12:41 [PATCH v2 00/10] LIS3: Feature updates and corrections Samu Onkalo
2009-11-10 12:41 ` [PATCH v2 01/10] LIS3LV02D: Send sync event Samu Onkalo
2009-11-10 12:41   ` [PATCH v2 02/10] LIS3LV02D: Correct memory leak in module unload Samu Onkalo
2009-11-10 12:41     ` [PATCH v2 03/10] lis3: Update documentation and comments Samu Onkalo
2009-11-10 12:41       ` [PATCH v2 04/10] lis3: fix show rate for 8 bits chips Samu Onkalo
2009-11-10 12:41         ` [PATCH v2 05/10] LIS3LV02D: Proper power on sequence Samu Onkalo
2009-11-10 12:41           ` [PATCH v2 06/10] LIS3LV02D: Selftest support Samu Onkalo
2009-11-10 12:41             ` [PATCH v2 07/10] LIS3LV02D: Remove calibaration functionality Samu Onkalo
2009-11-10 12:41               ` [PATCH v2 08/10] lis3: Sysfs entry for setting chip measurement rate Samu Onkalo
2009-11-10 12:41                 ` [PATCH v2 09/10] lis3: Scale output values to mg Samu Onkalo
2009-11-10 12:41                   ` [PATCH v2 10/10] LIS3: Update documentation to match latest changes Samu Onkalo
2009-11-15 15:43                     ` Éric Piel
2009-11-15 15:32                   ` [PATCH v2 09/10] lis3: Scale output values to mg Éric Piel
2009-11-15 18:04                     ` Pavel Machek
2009-11-15 15:20                 ` [PATCH v2 08/10] lis3: Sysfs entry for setting chip measurement rate Éric Piel
2009-11-15 15:54               ` [PATCH v2 07/10] LIS3LV02D: Remove calibaration functionality Éric Piel
2009-11-15 15:08             ` [PATCH v2 06/10] LIS3LV02D: Selftest support Éric Piel
2009-11-15 15:54           ` [PATCH v2 05/10] LIS3LV02D: Proper power on sequence Éric Piel
2009-11-15 15:53         ` [PATCH v2 04/10] lis3: fix show rate for 8 bits chips Éric Piel
2009-11-15 15:49     ` [PATCH v2 02/10] LIS3LV02D: Correct memory leak in module unload Éric Piel
2009-11-15 15:49   ` [PATCH v2 01/10] LIS3LV02D: Send sync event Éric Piel
2009-11-15 16:01 ` [PATCH v2 00/10] LIS3: Feature updates and corrections Éric Piel
2009-11-16 20:03   ` Andrew Morton
2009-11-16 20:37     ` Éric Piel [this message]
2009-11-17  6:04   ` samu.p.onkalo

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=4B01B804.6070809@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@caiaq.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=pavel@ucw.cz \
    --cc=samu.p.onkalo@nokia.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