From: Daniel Mack <zonque@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [PATCH 1/2] ALSA: snd-usb: mixer: coding style fixups
Date: Sat, 24 May 2014 10:49:35 +0200 [thread overview]
Message-ID: <53805D1F.3070107@gmail.com> (raw)
In-Reply-To: <s5h8uprftp3.wl%tiwai@suse.de>
On 05/24/2014 10:48 AM, Takashi Iwai wrote:
> At Fri, 23 May 2014 19:06:01 +0200,
> Daniel Mack wrote:
>>
>> Shorten some over-long lines, multi-line comments, spurious whitespaces,
>> curly brakets etc. No functional change.
>>
>> Signed-off-by: Daniel Mack <zonque@gmail.com>
>
> This didn't apply cleanly. Which tree/branch is it based on?
Oh, sorry. I'll check and resend.
Daniel
prev parent reply other threads:[~2014-05-24 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 17:06 [PATCH 1/2] ALSA: snd-usb: mixer: coding style fixups Daniel Mack
2014-05-23 17:06 ` [PATCH 2/2] ALSA: snd-usb: mixer: remove error messages on failed kmalloc() Daniel Mack
2014-05-24 8:48 ` [PATCH 1/2] ALSA: snd-usb: mixer: coding style fixups Takashi Iwai
2014-05-24 8:49 ` Daniel Mack [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=53805D1F.3070107@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox