From: Mark Brown <broonie@kernel.org>
To: Jeffy Chen <jeffy.chen@rock-chips.com>
Cc: linux-kernel@vger.kernel.org, dgreid@chromium.org,
heiko@sntech.de, briannorris@chromium.org, mka@chromium.org,
dianders@chromium.org, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-rockchip@lists.infradead.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v12 2/2] ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec
Date: Tue, 19 Sep 2017 13:46:13 +0100 [thread overview]
Message-ID: <20170919124613.egvojfhq74vhyvuh@sirena.co.uk> (raw)
In-Reply-To: <20170919025439.7107-2-jeffy.chen@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
On Tue, Sep 19, 2017 at 10:54:39AM +0800, Jeffy Chen wrote:
> Currently rt5514 dsp and rt5514 codec are sharing the same compatible.
> Use bus_type to distinguish rt5514 dsp from rt5514 codec.
This doens't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jeffy Chen <jeffy.chen@rock-chips.com>
Cc: alsa-devel@alsa-project.org, heiko@sntech.de,
Liam Girdwood <lgirdwood@gmail.com>,
briannorris@chromium.org, dianders@chromium.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
mka@chromium.org, Takashi Iwai <tiwai@suse.com>,
dgreid@chromium.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v12 2/2] ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec
Date: Tue, 19 Sep 2017 13:46:13 +0100 [thread overview]
Message-ID: <20170919124613.egvojfhq74vhyvuh@sirena.co.uk> (raw)
In-Reply-To: <20170919025439.7107-2-jeffy.chen@rock-chips.com>
[-- Attachment #1.1: Type: text/plain, Size: 260 bytes --]
On Tue, Sep 19, 2017 at 10:54:39AM +0800, Jeffy Chen wrote:
> Currently rt5514 dsp and rt5514 codec are sharing the same compatible.
> Use bus_type to distinguish rt5514 dsp from rt5514 codec.
This doens't apply against current code, please check and resend.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 2/2] ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec
Date: Tue, 19 Sep 2017 13:46:13 +0100 [thread overview]
Message-ID: <20170919124613.egvojfhq74vhyvuh@sirena.co.uk> (raw)
In-Reply-To: <20170919025439.7107-2-jeffy.chen@rock-chips.com>
On Tue, Sep 19, 2017 at 10:54:39AM +0800, Jeffy Chen wrote:
> Currently rt5514 dsp and rt5514 codec are sharing the same compatible.
> Use bus_type to distinguish rt5514 dsp from rt5514 codec.
This doens't apply against current code, please check and resend.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170919/d78ab1f9/attachment.sig>
next prev parent reply other threads:[~2017-09-19 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 2:54 [PATCH v12 1/2] ASoC: rt5514: Add devicetree binding support for rt5514-spi Jeffy Chen
2017-09-19 2:54 ` [PATCH v12 2/2] ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec Jeffy Chen
2017-09-19 2:54 ` Jeffy Chen
2017-09-19 12:46 ` Mark Brown [this message]
2017-09-19 12:46 ` Mark Brown
2017-09-19 12:46 ` Mark Brown
2017-09-19 13:04 ` jeffy
2017-09-19 13:04 ` jeffy
2017-09-19 13:04 ` jeffy
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=20170919124613.egvojfhq74vhyvuh@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jeffy.chen@rock-chips.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mka@chromium.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 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.