public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-acpi@vger.kernel.org, ibm-acpi-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] ibm-acpi: more updates
Date: Thu, 8 Mar 2007 22:59:55 -0500	[thread overview]
Message-ID: <200703082259.55832.lenb@kernel.org> (raw)
In-Reply-To: <11723292823837-git-send-email-hmh@hmh.eng.br>

Henrique,
If you could refresh this on to of the latest acpi-test,
that would be great.  (ibm-acpi changes in acpi-test are
headed for 2.6.21).

note also that you have some whitespace violations.
Space in indent is followed by a tab.
.dotest/patch:41:                                            led * led_exp_hlbl[ind]);
Space in indent is followed by a tab.
.dotest/patch:46:                                            led * led_exp_hlcl[ind]);

probably the simplest way to stay on top of these is
to maintain the driver as Lindent free upon every patch.
eg. run Lindent after every patch to make sure it doesn't
introduce any violations.

you can also use git-apply --whitespace=strip

thanks,
-Len

On Saturday 24 February 2007 10:01, Henrique de Moraes Holschuh wrote:
> Len,
> 
> Please pull from:
> git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
> branch for-upstream/acpi-test
> 
> to receive the following patches:
> 
> Henrique de Moraes Holschuh (5):
>       ACPI: ibm-acpi: rename some identifiers
>       ACPI: ibm-acpi: add header file
>       ACPI: ibm-acpi: organize code
>       ACPI: ibm-acpi: update copyright notice
>       ACPI: ibm-acpi: update documentation
> 
> It has a lot of code shuffling, which I did while cleaning up and preparing for
> a sysfs conversion.  It would be helpful to me if it is merged in acpi-test, as
> that means it will be much faster for me to keep my working tree and what is in
> acpi-test and mainline in sync.  The rest are just minor doc updates.
> 
> This patch set should not change any functionality.
> 
> I just added the patches on top of what I had already sent you (and that you
> have already merged).  If you'd prefer it to be based on something else, just
> say so.
> 
> 
> -
> 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:[~2007-03-09  4:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 15:01 [GIT PULL] ibm-acpi: more updates Henrique de Moraes Holschuh
     [not found] ` <11723292823837-git-send-email-hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
     [not found]   ` <bde16e404cce89ebfe6d9b143d979f0c6fe5434b.1172327581.git.hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-02-24 15:01     ` [PATCH 1/5] ACPI: ibm-acpi: rename some identifiers Henrique de Moraes Holschuh
     [not found]     ` <b5817781c14e13765fe3e8565498182edcfd6c2f.1172327581.git.hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-02-24 15:01       ` [PATCH 2/5] ACPI: ibm-acpi: add header file Henrique de Moraes Holschuh
     [not found]     ` <4787dcfed44cf6917db2ca185da606b4a0427d23.1172327581.git.hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-02-24 15:01       ` [PATCH 3/5] ACPI: ibm-acpi: organize code Henrique de Moraes Holschuh
     [not found]     ` <1ae587639cc41f32d5652f15a650df14775925c3.1172327581.git.hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-02-24 15:01       ` [PATCH 4/5] ACPI: ibm-acpi: update copyright notice Henrique de Moraes Holschuh
     [not found]     ` <d23ebd8421c3593ed659e16d6aa41a59dedc561c.1172327581.git.hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-02-24 15:01       ` [PATCH 5/5] ACPI: ibm-acpi: update documentation Henrique de Moraes Holschuh
     [not found] ` <bde16e404cce89ebfe6d9b143d979f0c6fe5434b.1172327581.git.hmh@hmh.eng.br>
2007-02-24 15:01   ` [PATCH 1/5] ACPI: ibm-acpi: rename some identifiers Henrique de Moraes Holschuh
     [not found]   ` <b5817781c14e13765fe3e8565498182edcfd6c2f.1172327581.git.hmh@hmh.eng.br>
2007-02-24 15:01     ` [PATCH 2/5] ACPI: ibm-acpi: add header file Henrique de Moraes Holschuh
     [not found]   ` <4787dcfed44cf6917db2ca185da606b4a0427d23.1172327581.git.hmh@hmh.eng.br>
2007-02-24 15:01     ` [PATCH 3/5] ACPI: ibm-acpi: organize code Henrique de Moraes Holschuh
     [not found]   ` <1ae587639cc41f32d5652f15a650df14775925c3.1172327581.git.hmh@hmh.eng.br>
2007-02-24 15:01     ` [PATCH 4/5] ACPI: ibm-acpi: update copyright notice Henrique de Moraes Holschuh
     [not found]   ` <d23ebd8421c3593ed659e16d6aa41a59dedc561c.1172327581.git.hmh@hmh.eng.br>
2007-02-24 15:01     ` [PATCH 5/5] ACPI: ibm-acpi: update documentation Henrique de Moraes Holschuh
2007-03-09  3:59 ` Len Brown [this message]
     [not found]   ` <200703082259.55832.lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2007-03-10 17:16     ` [GIT PULL] ibm-acpi: more updates Henrique de Moraes Holschuh
2007-03-11 19:34       ` Len Brown
2007-03-12  1:26         ` Henrique de Moraes Holschuh

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=200703082259.55832.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-acpi@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