From: Mark Brown <broonie@kernel.org>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
Cc: oder_chiou@realtek.com, jack.yu@realtek.com,
alsa-devel@alsa-project.org, seppo.ingalsuo@linux.intel.com,
lgirdwood@gmail.com, pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH v3] ASoC: rt1011: Fix 'I2S Reference' enum control caused error
Date: Wed, 13 Oct 2021 12:52:14 +0100 [thread overview]
Message-ID: <YWbIbnRVHGP82N+A@sirena.org.uk> (raw)
In-Reply-To: <b4f96793-de6f-0b0e-346d-f6a53633575f@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Tue, Oct 12, 2021 at 02:52:11PM +0300, Péter Ujfalusi wrote:
> On 12/10/2021 14:45, Mark Brown wrote:
> > [1/1] ASoC: rt1011: Fix 'I2S Reference' enum control caused error
> > commit: c3de683c4d1d68ff27f21606b921d92ffdea3352
> I have noted that this patch is not enough to fix the i2s reference
> support and a complete patch has been already sent:
> https://lore.kernel.org/alsa-devel/20211012063113.3754-1-peter.ujfalusi@linux.intel.com/
Are you sure this isn't just b4 thinking your later version matches the
earlier version when it's the later version that got applied (you'll
have got multiple mails with one for the later version as well)?
> What keyword should I use next time to 'block' a patch applied?
You can't, there's a gap between me queueing things and testing and
pushing out and mail sent in that time might not get seen.
You should also take care that when you're sending things you're doing
so in a standard fashion, occasionally I have seen people bury things in
the middle of threads or whatever which causes b4 to think an earlier
version is actually a later one.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-13 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 14:45 [PATCH v3] ASoC: rt1011: Fix 'I2S Reference' enum control caused error Peter Ujfalusi
2021-10-12 5:26 ` Péter Ujfalusi
2021-10-12 11:45 ` Mark Brown
2021-10-12 11:52 ` Péter Ujfalusi
2021-10-13 11:52 ` Mark Brown [this message]
2021-10-13 12:13 ` Péter Ujfalusi
2021-10-13 12:19 ` 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=YWbIbnRVHGP82N+A@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=seppo.ingalsuo@linux.intel.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.