Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rojewski, Cezary" <cezary.rojewski@intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	Jie Yang <yang.jie@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v1] catpt: Switch to use list_entry_is_head() helper
Date: Mon, 14 Dec 2020 17:37:29 +0200	[thread overview]
Message-ID: <20201214153729.GK4077@smile.fi.intel.com> (raw)
In-Reply-To: <7b7ad24505604110aeeebb2a0b30e573@intel.com>

On Mon, Dec 14, 2020 at 09:14:13AM +0000, Rojewski, Cezary wrote:
> On 2020-12-08 11:26 AM, Andy Shevchenko wrote:
> > Since we got list_entry_is_head() helper in the generic header,
> > we may switch catpt to use it. It removes the need in additional variable.
> 
> Thanks for the patch, Andy. One nitpick below.

...

> >   	struct catpt_dev *cdev = dev_get_drvdata(dai->dev);
> >   	struct snd_soc_component *component = dai->component;
> > -	struct snd_kcontrol *pos, *kctl = NULL;
> >   	const char *name;
> >   	int ret;
> >   	u32 id = stream->info.stream_hw_id;
> > +	struct snd_kcontrol *pos;
> 
> Shouldn't structs be declared before any primitive-types?

Good question. I consider the length of the line is more important
(to keep reversed xmas tree order).

If you think we should leave as is tell me, I'll send v2.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-12-14 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 10:26 [PATCH v1] catpt: Switch to use list_entry_is_head() helper Andy Shevchenko
2020-12-14  9:14 ` Rojewski, Cezary
2020-12-14 15:37   ` Andy Shevchenko [this message]
2020-12-14 16:26     ` Rojewski, Cezary
2020-12-28 16:03 ` Mark Brown

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=20201214153729.GK4077@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=yang.jie@linux.intel.com \
    /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