linux-kernel - Re: [PATCH 0/2] Add dev_sysdata and use it for ACPI

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: <1163398066.4982.282.camel@localhost.localdomain>
Date:	Mon, 13 Nov 2006 17:07:45 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Greg KH <greg@...ah.com>, Cornelia Huck <cornelia.huck@...ibm.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH 0/2] Add dev_sysdata and use it for ACPI

On Mon, 2006-11-13 at 16:17 +1100, Paul Mackerras wrote:
> Greg KH writes:
> 
> > Care to respin these patches with this change?
> > 
> > And yes, I don't see a problem with such a change like this for 2.6.20,
> > it's pretty simple.
> 
> I need to put Ben's "Add arch specific dev_archdata to struct device"
> patch into my tree in the for-2.6.20 branch, because it creates
> include/asm-powerpc/device.h, and I have other patches queued up which
> touch include/asm-powerpc/device.h.
> 
> Greg, if you want you can drop that patch, and Linus' tree will get it
> via my tree, or if that's difficult, Linus' tree will get it from both
> directions.  I'm sure git will sort it out. :)

Greg: Note that the patch paulus has is the respin I posted on Saturday
with the name change and the use of include/asm-generic/ as suggested by
Steven.

Ben.


-
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/