Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Krause <minipli@googlemail.com>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Mathias Krause <minipli@googlemail.com>,
	Len Brown <lenb@kernel.org>
Subject: [PATCH 0/4] ASoC: constification patches
Date: Sat, 13 Jun 2015 14:25:12 +0200	[thread overview]
Message-ID: <1434198316-8400-1-git-send-email-minipli@googlemail.com> (raw)

Hi Liam, Mark,

this series constifies a few variables in the SoC code that are only
read, namely struct reg_default and struct acpi_device_id.

Please apply!


Mathias Krause (4):
  ASoC: max98090: Constify ACPI device ids and register map
  ASoC: rt5640: Constify ACPI device ids and register map
  ASoC: rt5670: Constify ACPI device ids and register map
  ASoC: intel: Constify ACPI device ids

 sound/soc/codecs/max98090.c       |    4 ++--
 sound/soc/codecs/rt5640.c         |    5 ++---
 sound/soc/codecs/rt5670.c         |    5 ++---
 sound/soc/intel/common/sst-acpi.c |    2 +-
 4 files changed, 7 insertions(+), 9 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2015-06-13 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 12:25 Mathias Krause [this message]
2015-06-13 12:25 ` [PATCH 1/4] ASoC: max98090: Constify ACPI device ids and register map Mathias Krause
2015-06-13 12:25 ` [PATCH 2/4] ASoC: rt5640: " Mathias Krause
2015-06-15 10:19   ` Mark Brown
2015-06-15 17:50     ` Mathias Krause
2015-06-13 12:25 ` [PATCH 3/4] ASoC: rt5670: " Mathias Krause
2015-06-13 12:25 ` [PATCH 4/4] ASoC: intel: Constify ACPI device ids Mathias Krause
2015-06-15 13:07   ` Jarkko Nikula
2015-06-15 10:32 ` [PATCH 0/4] ASoC: constification patches Mark Brown
2015-06-15 17:59   ` Mathias Krause
2015-06-15 19:17     ` 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=1434198316-8400-1-git-send-email-minipli@googlemail.com \
    --to=minipli@googlemail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lenb@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=rjw@rjwysocki.net \
    /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