From: Mark Brown <broonie@kernel.org>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: kuninori.morimoto.gx@renesas.com, patch@alsa-project.org,
twischer@de.adit-jv.com, perex@perex.cz, tiwai@suse.com,
Jiada Wang <jiada_wang@mentor.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: rsnd: dma: fix SSI9 4/5/6/7 busif dma address
Date: Tue, 22 Oct 2019 17:53:37 +0100 [thread overview]
Message-ID: <20191022165337.GX5554@sirena.co.uk> (raw)
In-Reply-To: <20191022164607.GA20665@vmlxhi-102.adit-jv.com>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Tue, Oct 22, 2019 at 06:46:07PM +0200, Eugeniu Rosca wrote:
> On Tue, Oct 22, 2019 at 05:35:01PM +0100, Mark Brown wrote:
> > On Tue, Oct 22, 2019 at 05:49:04PM +0200, Eugeniu Rosca wrote:
> > > It still applies cleanly to v5.4-rc4-18-g3b7c59a1950c.
> > > Any chance to see it in vanilla?
> > Someone would need to resend it. No idea what the issues are but I
> > don't have it any more.
> How about downloading it from [1] by pressing on the "mbox" button and
> applying it with "git am"? This will also include any
> "*-by: Name <E-mail>" signatures found in the thread.
> If this doesn't match your workflow, I can resend it.
This doesn't match either my workflow or the kernel's workflow in
general, please resend - that means that not only I but also other
people on the list have the chance to see the patch and review it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-22 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 8:23 twischer
2019-02-25 1:15 ` Kuninori Morimoto
2019-02-25 1:18 ` Kuninori Morimoto
2019-10-22 15:49 ` [alsa-devel] " Eugeniu Rosca
2019-10-22 16:35 ` Mark Brown
2019-10-22 16:46 ` Eugeniu Rosca
2019-10-22 16:53 ` Mark Brown [this message]
2019-10-22 18:59 ` Eugeniu Rosca
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=20191022165337.GX5554@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=erosca@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patch@alsa-project.org \
--cc=perex@perex.cz \
--cc=roscaeugeniu@gmail.com \
--cc=tiwai@suse.com \
--cc=twischer@de.adit-jv.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
all inboxes | Powered by JetHome®