public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Lerouge <julien.lerouge@m4x.org>
To: Len Brown <lenb@kernel.org>
Cc: corentincj@iksaif.net, linux-acpi@vger.kernel.org,
	sziwan@users.sourceforge.net
Subject: Re: [PATCH 0/22] acpi4asus sync with 0.31
Date: Wed, 20 Dec 2006 17:17:05 -0800	[thread overview]
Message-ID: <20061221011705.GG29711@debian> (raw)
In-Reply-To: <200612201749.32486.lenb@kernel.org>

Sorry Len, I should have told you earlier,

I have not been active for a long time, and don't plan to be, at least
not on this driver. Corentin is willing to maintain it. I don't know for
Karol, but you can remove me from the MAINTAINERS.

Also, Corentin should be added to the list of the MAINTAINERS for this
driver.

Thanks,
Julien

On Wed, Dec 20, 2006 at 05:49:32PM -0500, Len Brown wrote:
> Karol and Julien are listed as the MAINTAINERS for asus_acpi.
> Why do I not see their Signed-off-by or Acked-by lines on this patch series?

> On Wednesday 20 December 2006 05:02, Corentin CHARY wrote:
> > Le mercredi 20 décembre 2006 08:42, Len Brown a écrit :
> > > On Tuesday 19 December 2006 16:17, Corentin CHARY wrote:
> > > > Hi,
> > > > This set of patch is against 2.6.19. It add support for many
> > > > models, /sys/class/backlight/, Light Sens, etc ... There is also a lot of
> > > > cleanups. And the most important, a new system to handle unsupported
> > > > models.
> > > >
> > > > Patch from 0 to 10 are change and cleanups in the driver.
> > > > Patch from 11t to 21 add support for new models.
> > > >
> > > > All the following patchs are available here :
> > > > <http://xf.iksaif.net/acpi4asus/2.6.19/>
> > >

> > >
> > > When this series is formatted to apply, what tree is it supposed to apply
> > > to?
> > These patchs are done with asus_acpi.c from 2.6.19 . So it can be applied to 
> > 2.6.19 and 2.6.20-rc1 (as there is no change for asus_acpi in 2.6.20-rc1).
> > 
> > 
> > >
> > > How does it relate to the two asus_acpi patches in the mm tree right now --
> > > 13/19 and 19/19 that akpm forwarded to the list yesterday.
> > >
> > The change in the mm tree are :   
> > 	- Backlight support
> > 	=> It's nearly the same code (patch 10/22)
> > 	- no more useless cast
> > 	=> It's ok (patch 7/22)
> > 	- Add support for A6VA, M6V, W5F, V6V, A4S
> > 	=> It's ok, but more features are supported in my patchs.
> > 	And the implemention is cleaner, as I use my parse_method()
> > 	function instead of adding special case in get_lcd_status()
> > 	(see patch 5/22 and 6/22)
> > 	- Swap W5A and W3V
> > 	=> It's ok,  (patch 19/22)
> > 	- Invert wled status
> > 	=> I don't do it, as it's a mistake. I tested on A6T, A6J, F3JM, and the
> > 	wled value don't need to be inverted.

> So should we NAK the two patches that are proposed in -mm
> and ask Andrew to not accept asus_acpi patches and instead direct
> them to acpi4asus-user@lists.sourceforge.net?

> > > How does it relate to the acpi-test tree, which already includes
> > > the backlight patch to asus_acpi from Holger Macht?
> > The change in the acpi-test tree are :
> > 	- Backlight support
> > 	=> done
> > 	- no more useless cast
> > 	=> done

> Holger's patch is already queued for upstream -- having lived in -mm for some time now.
> When you resend the acpi4asus series such that it is properly formatted,
> please be sure it applies cleanly to what is in acpi release tree.
> (ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.20/acpi-release-20060707-2.6.20-rc1.diff.gz)

> thanks,
> -Len
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2006-12-21  1:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 21:17 [PATCH 0/22] acpi4asus sync with 0.31 Corentin CHARY
2006-12-20  7:42 ` Len Brown
2006-12-20 10:02   ` Corentin CHARY
2006-12-20 22:49     ` Len Brown
2006-12-20 23:36       ` Corentin CHARY
2006-12-21  1:17       ` Julien Lerouge [this message]
2006-12-23  2:11         ` Len Brown
2006-12-23 12:27           ` Corentin CHARY

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=20061221011705.GG29711@debian \
    --to=julien.lerouge@m4x.org \
    --cc=corentincj@iksaif.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sziwan@users.sourceforge.net \
    /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