From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Hsiang <Peter.Hsiang@maxim-ic.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: tabs versus space fill
Date: Fri, 10 Dec 2010 21:54:40 +0000 [thread overview]
Message-ID: <20101210215440.GA8896@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B2150E1E4418E1438554A300EA5040E40D579D15E8@ITSVLEX06.it.maxim-ic.internal>
On Fri, Dec 10, 2010 at 01:25:10PM -0800, Peter Hsiang wrote:
[Please fix to word wrap within paragraphs, I've reflowed the text below.]
> I noticed that in the latest version of the kernel (next), the
> formatting of the soc sound driver file max98088.c had been changed.
> Someone had changed all the tabs to space-fill. I thought the kernel
> coding standard encourages the use of tabs. Is the use of space-fill
> the new formatting preference for the kernel?
No, everything should use raw tabs.
> I did not see this patch change on alsa-devel list.
> How do I find out where and when this was changed?
There's been no change in the kernel here - looking at the original mail
from you adding the driver that used spaces rather than tabs. I expect
that this was caused by a configuration issue in your mail system which
caused it to rewrite the content, either the user agent or something on
the server side.
prev parent reply other threads:[~2010-12-10 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 16:23 [RFC 2.6.38] ASoC: Fix bias power down of non-DAPM codec Jarkko Nikula
2010-12-10 17:42 ` Mark Brown
2010-12-10 18:53 ` [PATCH 2.6.37] " Jarkko Nikula
2010-12-10 18:54 ` [RFC 2.6.38] ASoC: Fix build error caused by merging a fix for 2.6.37 into 2.6.38 Jarkko Nikula
2010-12-10 23:02 ` Liam Girdwood
2010-12-13 16:47 ` Mark Brown
2010-12-10 23:02 ` [PATCH 2.6.37] ASoC: Fix bias power down of non-DAPM codec Liam Girdwood
2010-12-13 16:37 ` Mark Brown
2010-12-10 21:25 ` tabs versus space fill Peter Hsiang
2010-12-10 21:35 ` Vasily Khoruzhick
2010-12-10 21:54 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101210215440.GA8896@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox