From: Mark Brown <broonie@kernel.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>,
Jean-Francois Moine <moinejf@free.fr>,
alsa-devel@alsa-project.org,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: kirkwood: change the compatible string of the kirkwood-i2s driver
Date: Thu, 5 Sep 2013 18:18:13 +0100 [thread overview]
Message-ID: <20130905171813.GA2839@sirena.org.uk> (raw)
In-Reply-To: <20130905190341.4a4a7820@skate>
[-- Attachment #1.1: Type: text/plain, Size: 636 bytes --]
On Thu, Sep 05, 2013 at 07:03:41PM +0200, Thomas Petazzoni wrote:
> not exactly the same. Should this error interrupt become useful in the
> driver, it should be done only for Dove, so it makes sense to have two
> different compatible strings.
In general it's reasonable to add compatible strings for the SoCs anyway
since even if we don't know of any reason why we'd want to distingush
between them right now it's possible that in the future some reason
might be discovered (such as an erratum being found). Worst case the
kernel just treats both compatible strings identically which isn't a
great loss. It's not essential though.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-09-05 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 12:56 [PATCH] ASoC: kirkwood: change the compatible string of the kirkwood-i2s driver Thomas Petazzoni
2013-09-05 16:54 ` Jean-Francois Moine
2013-09-05 17:03 ` Thomas Petazzoni
2013-09-05 17:18 ` Mark Brown [this message]
2013-09-05 17:24 ` Jean-Francois Moine
2013-09-06 9:31 ` 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=20130905171813.GA2839@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alior@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=rob.herring@calxeda.com \
--cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).