From: Daniel Mack <daniel@zonque.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ALSA: soundcore: coding style fixes
Date: Thu, 05 Jun 2014 15:59:03 +0200 [thread overview]
Message-ID: <539077A7.1080007@zonque.org> (raw)
In-Reply-To: <s5hegz31mz0.wl%tiwai@suse.de>
On 06/05/2014 03:53 PM, Takashi Iwai wrote:
> At Thu, 5 Jun 2014 14:12:25 +0200,
> Daniel Mack wrote:
>>
>> sound/sounc_core.c has a larger number of style issues. Fix them to make the
>> code more readable. No functional change.
>>
>> Signed-off-by: Daniel Mack <zonque@gmail.com>
>
> Thanks for the patches, but are you going to fix anything in these
> codes along with them? Such coding style fixes just stir git history,
> which make often annoying for backporting or reviewing. So, basically
> I'd take such cleanup patches only if the real fixes will come
> together.
Yeah, I know that code is legacy. I was just skimming over the sources
to trace a bug report on alsa-user, and stumbled over so many style
issues that made reading the code harder than necessary that I couldn't
resist fixing them :)
Hence, I don't know yet. Maybe there will be a fix as well at some late
point. Feel free to ignore the patches for now. I'll stash and resend
them along with real fixes in case there are any.
Thanks,
Daniel
next prev parent reply other threads:[~2014-06-05 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:12 [PATCH 1/2] ALSA: soundcore: coding style fixes Daniel Mack
2014-06-05 12:12 ` [PATCH 2/2] ALSA: sound_firmware: fix style issues Daniel Mack
2014-06-05 13:38 ` Takashi Sakamoto
2014-06-05 13:37 ` [PATCH 1/2] ALSA: soundcore: coding style fixes Takashi Sakamoto
2014-06-05 13:53 ` Takashi Iwai
2014-06-05 13:59 ` Daniel Mack [this message]
2014-06-05 14:12 ` Takashi Iwai
2014-06-05 14:14 ` Daniel Mack
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=539077A7.1080007@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.