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] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Feb 2009 11:23:59 +0100
From:	Patrick Ohly <patrick.ohly@...el.com>
To:	Johannes Weiner <hannes@...xchg.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm] documentation: update CodingStyle tips for Emacs
	users

On Wed, 2009-02-18 at 09:59 +0000, Johannes Weiner wrote:
[formatting of line continuation in argument list]
> Unfortunately, this seems to depend on the maintainer.  Both styles
> are used all over the kernel but Documentation/CodingStyle and
> scripts/checkpatch.pl prefer what the above emacs configuration does.

checkpatch.pl didn't seem to mind either way. I haven't seen this
particular aspect mentioned in the CodingStyle either.

> I doubt that people do tab tab tab space space space space space by
> hand, so I strongly suspect that the tab-only zealots don't use emacs
> which does this adjustment automatically.
> 
> You should probably add linux-davem to the above or something.  Or
> name the coding style after the text-editor the target maintainer
> uses :-)

One could also get really fancy and extend the path matching to pick the
right style depending on the subdirectory ;-)

Thanks for the clarification. In the future I'll pay closer attention to
existing code and turn the macro on or off accordingly.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ