From: Mark Brown <broonie@kernel.org>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: fsl: Fix error handling in pcm030_fabric_probe
Date: Wed, 20 Apr 2022 14:41:21 +0100 [thread overview]
Message-ID: <YmANgcO9BMxp8PLC@sirena.org.uk> (raw)
In-Reply-To: <4e3309d9-879f-3385-3e8e-0fa1a31ddd9a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Wed, Apr 20, 2022 at 09:35:55PM +0800, Miaoqian Lin wrote:
> On 2022/4/20 21:00, Mark Brown wrote:
> >> - rebase on top of commit 559089e0a93d ("vmalloc: replace VM_NO_HUGE_VMAP with VM_ALLOW_HUGE_VMAP")
> > Why rebase on top of that seemingly random commit? Is there some sort
> > of dependency here?
> Hi, it the head of master in when I made this patch. It's because you pointed out
> that patch v1 doesn't apply against current code. But I am not sure what's the problem.
> So I ensure the codebase is up-to-date. If this patch have no conflict, you can ignore it.
Current code here is my git tree (-next is often a fair approximation) -
if people have been making changes since the merge window then often
code written against mainline won't apply and things need to be based on
people's current work. You're looking for
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-20 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:53 [PATCH] " Miaoqian Lin
2022-03-02 13:44 ` Mark Brown
2022-04-20 2:18 ` [PATCH v2] " Miaoqian Lin
2022-04-20 13:00 ` Mark Brown
2022-04-20 13:35 ` Miaoqian Lin
2022-04-20 13:41 ` Mark Brown [this message]
2022-04-20 13:45 ` Miaoqian Lin
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=YmANgcO9BMxp8PLC@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.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 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®