From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: liam.r.girdwood@linux.intel.com, tiwai@suse.de,
alsa-devel@alsa-project.org, patches.audio@intel.com
Subject: Re: [PATCH 0/2] ASoC: Intel: skylake - match braces for if-else
Date: Thu, 9 Jul 2015 09:43:22 +0530 [thread overview]
Message-ID: <20150709041322.GC836@localhost> (raw)
In-Reply-To: <20150708182723.GX11162@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 833 bytes --]
On Wed, Jul 08, 2015 at 07:27:23PM +0100, Mark Brown wrote:
> On Tue, Jun 23, 2015 at 10:40:11PM +0530, Vinod Koul wrote:
> > Coding style mandates that if-else should match braces even if one of them
> > is a single line statement. Fix it in two places missed earlier
> >
> > Mark, you can also fold these two patches with SKL driver series (1st and
> > 2nd patch can fold in 1st and 2nd patch respectively) or apply independetly,
> > either way okay
>
> I really don't know what that series is any more, sorry. I've got two
> pending serieses both identified as Sky Lake and sent after this one.
Hi Mark,
For the last series you said you were okay but had noticed some style
inconsistencies, so I fixed those with this. The updated patchset (rebased)
has these folded in, so this can be ignored.
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-07-09 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 17:10 [PATCH 0/2] ASoC: Intel: skylake - match braces for if-else Vinod Koul
2015-06-23 17:10 ` [PATCH 1/2] ASoC: Intel: skl-pcm.c " Vinod Koul
2015-06-23 17:10 ` [PATCH 2/2] ASoC: Intel: skl.c " Vinod Koul
2015-07-08 18:27 ` [PATCH 0/2] ASoC: Intel: skylake - " Mark Brown
2015-07-09 4:13 ` Vinod Koul [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=20150709041322.GC836@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--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.