All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Hector Martin <marcan@marcan.st>
Cc: alsa-devel@alsa-project.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sound updates for 5.14-rc1
Date: Sat, 03 Jul 2021 20:47:50 +0200	[thread overview]
Message-ID: <s5hbl7j9quh.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5heecf9rgb.wl-tiwai@suse.de>

On Sat, 03 Jul 2021 20:34:44 +0200,
Takashi Iwai wrote:
> 
> On Sat, 03 Jul 2021 14:06:36 +0200,
> Hector Martin wrote:
> > 
> > On 03/07/2021 16.56, Takashi Iwai wrote:
> > > Unfortunately I can't test much right now in my side as I'm traveling
> > > (until the next Tuesday).  So, Linus, Hector, please let me know if
> > > this works.  Once when it's confirmed to work, I'll prepare the new PR
> > > including the fix later in today.
> > 
> > Works for me on top of the for-next branch that was previously
> > deadlocking. I can't get it to crash any more.
> > 
> > Tested-by: Hector Martin <marcan@marcan.st>
> 
> Great, thanks for quick testing!

And now I saw that Linus reverted the commit already in his tree, so
no hurry for pushing the fix up for now.

I'll try to check the fix more closely in my side in the next week.
Hopefully everything will be sorted out and the new feature is enabled
again in the next PR.


thanks,

Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Hector Martin <marcan@marcan.st>
Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 5.14-rc1
Date: Sat, 03 Jul 2021 20:47:50 +0200	[thread overview]
Message-ID: <s5hbl7j9quh.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5heecf9rgb.wl-tiwai@suse.de>

On Sat, 03 Jul 2021 20:34:44 +0200,
Takashi Iwai wrote:
> 
> On Sat, 03 Jul 2021 14:06:36 +0200,
> Hector Martin wrote:
> > 
> > On 03/07/2021 16.56, Takashi Iwai wrote:
> > > Unfortunately I can't test much right now in my side as I'm traveling
> > > (until the next Tuesday).  So, Linus, Hector, please let me know if
> > > this works.  Once when it's confirmed to work, I'll prepare the new PR
> > > including the fix later in today.
> > 
> > Works for me on top of the for-next branch that was previously
> > deadlocking. I can't get it to crash any more.
> > 
> > Tested-by: Hector Martin <marcan@marcan.st>
> 
> Great, thanks for quick testing!

And now I saw that Linus reverted the commit already in his tree, so
no hurry for pushing the fix up for now.

I'll try to check the fix more closely in my side in the next week.
Hopefully everything will be sorted out and the new feature is enabled
again in the next PR.


thanks,

Takashi

  reply	other threads:[~2021-07-03 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:29 [GIT PULL] sound updates for 5.14-rc1 Takashi Iwai
2021-07-02 22:37 ` pr-tracker-bot
2021-07-03  1:36 ` Linus Torvalds
2021-07-03  4:37   ` Linus Torvalds
2021-07-03  5:19     ` Linus Torvalds
2021-07-03  5:19       ` Linus Torvalds
2021-07-03  6:38       ` Takashi Sakamoto
2021-07-03  6:38         ` Takashi Sakamoto
2021-07-03  7:56         ` Takashi Iwai
2021-07-03  7:56           ` Takashi Iwai
2021-07-03 12:06           ` Hector Martin
2021-07-03 12:06             ` Hector Martin
2021-07-03 18:34             ` Takashi Iwai
2021-07-03 18:34               ` Takashi Iwai
2021-07-03 18:47               ` Takashi Iwai [this message]
2021-07-03 18:47                 ` Takashi Iwai

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=s5hbl7j9quh.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=torvalds@linux-foundation.org \
    /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.