linux-kernel - Re: Please pull ACPI tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080721150921.GA29543@basil.nowhere.org>
Date:	Mon, 21 Jul 2008 17:09:21 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andi Kleen <andi@...stfloor.org>, torvalds@...l.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Please pull ACPI tree

On Mon, Jul 21, 2008 at 04:23:43PM +0200, Ingo Molnar wrote:
> 
> * Andi Kleen <andi@...stfloor.org> wrote:
> 
> > This reverts some double commits and a trouble some FADT patch.
> 
> > Andi Kleen (4):
> >       Revert "dock: bay: Don't call acpi_walk_namespace() when ACPI is disabled."
> 
> in that commit log you say:
> 
>    Revert "dock: bay: Don't call acpi_walk_namespace() when ACPI is disabled."
>    Revert double commit by mistake. Noticed by Thomas Gleixner.
> 
> it wasnt just "noticed" by Thomas, he sent a reverter patch with commit 
> message and patch included. Why didnt you simply apply the patch from 
> Thomas?

Of course so that you have something to complain about. I know
that is your favorite pastime in the last months, so I didn't want to deny
you the fun.

Seriously, typing in git revert is the way to apply a revert.
I could have cut'n'pasted his commit message, but it didn't seem
to make much difference.

-Andi (who is amazed he has to write emails on trivialities like this) 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/