linux-kernel - Re: emacs and "linux" coding style

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]

Message-Id: <20100717065146.732f5449.rdunlap@xenotime.net>
Date:	Sat, 17 Jul 2010 06:51:46 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	Dimitrios Apostolou <jimis@....net>, linux-kernel@...r.kernel.org,
	Dan Nicolaescu <dann@....org>
Subject: Re: emacs and "linux" coding style

On Sat, 17 Jul 2010 11:21:03 +0200 Krzysztof Halasa wrote:

> Dimitrios Apostolou <jimis@....net> writes:
> 
> > static void update_group_shares_cpu(struct task_group *tg, int cpu,
> >                                     unsigned long sd_shares,
> >                                     unsigned long sd_rq_weight,
> >                                     unsigned long *usd_rq_weight)
> > {
> 
> From a technical POV the above should not have any tabs, the parameters
> should be aligned with spaces only.

fwiw, it seems that you agree with Ted.

> The tabs should be used for (syntactic) indentation only.
> 
> This way we can display the code correctly with any tab length.

but we know what the tab length is.  ;)

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/