From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: alsa-devel@alsa-project.org, timur@tabi.org,
max.krummenacher@toradex.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, caleb@crome.org, tiwai@suse.com,
mpa@pengutronix.de, broonie@kernel.org,
Arnaud Mouiche <arnaud.mouiche@invoxia.com>,
fabio.estevam@nxp.com, mail@maciej.szmigiero.name,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number
Date: Sat, 25 Nov 2017 16:36:23 -0800 [thread overview]
Message-ID: <20171126003622.GA7276@Asurada> (raw)
In-Reply-To: <20171125232921.01994d72@jawa>
On Sat, Nov 25, 2017 at 11:29:48PM +0100, Lukasz Majewski wrote:
> Nicolin, do you know what happened with this patch? I couldn't find it
> in current linux/master.
>
> Has it been applied to any asoc tree for being upstreamed?
A similar patch with an updated subject got applied:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20171124&id=b0a7043d5c2ccdd306959f295bf1a62be025cbf5
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Arnaud Mouiche <arnaud.mouiche@invoxia.com>,
broonie@kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, alsa-devel@alsa-project.org,
tiwai@suse.com, perex@perex.cz, lgirdwood@gmail.com,
fabio.estevam@nxp.com, timur@tabi.org, caleb@crome.org,
max.krummenacher@toradex.com, mpa@pengutronix.de,
mail@maciej.szmigiero.name
Subject: Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number
Date: Sat, 25 Nov 2017 16:36:23 -0800 [thread overview]
Message-ID: <20171126003622.GA7276@Asurada> (raw)
In-Reply-To: <20171125232921.01994d72@jawa>
On Sat, Nov 25, 2017 at 11:29:48PM +0100, Lukasz Majewski wrote:
> Nicolin, do you know what happened with this patch? I couldn't find it
> in current linux/master.
>
> Has it been applied to any asoc tree for being upstreamed?
A similar patch with an updated subject got applied:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20171124&id=b0a7043d5c2ccdd306959f295bf1a62be025cbf5
next prev parent reply other threads:[~2017-11-26 0:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 5:23 [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number Nicolin Chen
2017-09-08 5:23 ` Nicolin Chen
2017-09-08 5:42 ` Nicolin Chen
2017-09-08 5:42 ` Nicolin Chen
2017-09-08 6:14 ` Arnaud Mouiche
2017-09-08 8:41 ` Łukasz Majewski
2017-09-12 14:35 ` Arnaud Mouiche
2017-09-12 21:32 ` Nicolin Chen
2017-09-12 21:32 ` Nicolin Chen
2017-09-13 8:02 ` Arnaud Mouiche
2017-09-13 8:02 ` Arnaud Mouiche
2017-09-13 23:01 ` Nicolin Chen
2017-11-25 22:29 ` Lukasz Majewski
2017-11-25 22:29 ` Lukasz Majewski
2017-11-26 0:36 ` Nicolin Chen [this message]
2017-11-26 0:36 ` Nicolin Chen
2017-11-26 20:22 ` Lukasz Majewski
2017-11-26 20:22 ` Lukasz Majewski
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=20171126003622.GA7276@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=broonie@kernel.org \
--cc=caleb@crome.org \
--cc=fabio.estevam@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukma@denx.de \
--cc=mail@maciej.szmigiero.name \
--cc=max.krummenacher@toradex.com \
--cc=mpa@pengutronix.de \
--cc=timur@tabi.org \
--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.