| 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
| ||
|
Message-ID: <fa686aa40911020856u1dba88feib46cb40dce7de6dc@mail.gmail.com> Date: Mon, 2 Nov 2009 09:56:21 -0700 From: Grant Likely <grant.likely@...retlab.ca> To: Nathan Fontenot <nfont@...tin.ibm.com> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/6 v5] Kernel DLPAR Infrastructure On Mon, Nov 2, 2009 at 9:47 AM, Nathan Fontenot <nfont@...tin.ibm.com> wrote: > Grant Likely wrote: >> >> On Mon, Nov 2, 2009 at 9:27 AM, Nathan Fontenot <nfont@...tin.ibm.com> >> wrote: >>> >>> I saw that Grant Likely is doing updates to all of the of_* stuff right >>> now, >>> would it be ok to have these routines here, renamed as dlpar_*, and look >>> to merge them in with Grant's updates when he finishes? >> >> No because then we're stuck with renaming the API at a later date. >> Name it what it is, and put it where it belongs. I'll deal with any >> merge breakage as it occurs. >> > > ok. Would this be better off in powerpc code, or should I go ahead and put > it > in something like drivers/of/dynamic.c? drivers/of/dynamic.c sounds fine to me. I can always move them if it find a better place. Send the patch to me and cc: the devicetree-discuss@...ts.ozlabs.org mailing list. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- 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/
Powered by blists - more mailing lists