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
| ||
|
Date: Sun, 15 Nov 2009 20:54:06 +0300 From: Alexey Starikovskiy <aystarik@...il.com> To: Daniel Walker <dwalker@...o99.com> CC: Felipe Contreras <felipe.contreras@...il.com>, linux-kernel@...r.kernel.org, Len Brown <lenb@...nel.org>, Len Brown <len.brown@...el.com>, Lin Ming <ming.m.lin@...el.com>, Bob Moore <robert.moore@...el.com>, Andi Kleen <ak@...ux.intel.com>, linux-acpi@...r.kernel.org Subject: Re: [PATCH 4/5] acpi: fix trivial warning You've made changes to automatically generated files, so all the style changes would be overwritten when next time these files are generated -- all the files go through Lindent, and almost all your changes were introduced by it. If you really want to make style changes to ACPICA files, try to play with Lindent, so it produce what you want. If you have anything beside style patches, please submit them separately Regards, Alex. Daniel Walker wrote: > On Sun, 2009-11-15 at 19:27 +0200, Felipe Contreras wrote: > >> On Sun, Nov 15, 2009 at 7:15 PM, Daniel Walker <dwalker@...o99.com> wrote: >> >>> On Fri, 2009-11-13 at 22:28 +0200, Felipe Contreras wrote: >>> >>>> That doesn't seem too positive. Or at least there's no indication that >>>> somebody will pick it up. >>>> >>> I'd re-submit with a better description of the patch. You should always >>> try to describe what your doing as accurately as possible so the >>> maintainer doesn't have to work very hard to know what your doing. >>> >> There's nothing to add. It's a patch to cleanup the coding style, that's it. >> > > How do you know the coding style isn't correct? Did you just visually > inspect it? > > >>> That >>> particular patch just has a one liner description that wasn't very >>> informative .. Either that or re-submit your series without that patch >>> if you don't have confidence in it. >>> >> All of my patches have been picked up, except the ones for ACPI. I >> haven't received a single comment from them, which would explain the >> current state of the code. >> >> If somebody raised the hand and said; I'll merge this, please resend, >> I'd do that, otherwise I think it's a waste of time. >> > > Patches often times aren't accepted in the first submission, could be > for lots of reasons. It's your series tho .. > > Daniel > > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- 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