linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Bastian Rieck <bastian@rieck.me>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	grzegorz.alibozek@gmail.com, andrew.co@free.fr,
	meven29@gmail.com, pchernik@gmail.com, jorge.cep.mart@gmail.com,
	danielmorgan@disroot.org, bernie@codewiz.org,
	saipavanchitta1998@gmail.com, rubin@starset.net,
	maniette@gmail.com, nate@kde.org
Subject: Re: [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume
Date: Fri, 7 Oct 2022 13:04:51 +0300	[thread overview]
Message-ID: <Yz/5w5faKmnJNPut@kuha.fi.intel.com> (raw)
In-Reply-To: <11781567.uqkIggiGGz@nimue>

On Fri, Oct 07, 2022 at 12:00:16PM +0200, Bastian Rieck wrote:
> Dear Heikki, dear all,
> 
> I am still unable to reproduce the previous error messages I 
> mentioned. In the meantime, the UCSI issues disappeared with 5.19.9 
> for me (!). I think this is related to a revert by Takashi Iwai  [1] 
> in 5.19.8.
> 
> Given these data, would it be useful to test your patch against 
> 5.19.9 or a more recent version?

No need. I'm just about to resend these.

thanks,

-- 
heikki

      reply	other threads:[~2022-10-07 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 11:56 [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume Heikki Krogerus
2022-09-07 11:56 ` [RFC PATCH 1/2] usb: typec: ucsi: Check the " Heikki Krogerus
2022-09-07 11:56 ` [RFC PATCH 2/2] usb: typec: ucsi: acpi: Add PM hooks Heikki Krogerus
2022-09-07 21:33 ` [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume Grzegorz Alibożek
2022-09-08  5:01 ` Bastian Rieck
2022-09-09  6:22   ` Heikki Krogerus
2022-09-16 10:46     ` Heikki Krogerus
2022-10-07 10:00       ` Bastian Rieck
2022-10-07 10:04         ` Heikki Krogerus [this message]

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=Yz/5w5faKmnJNPut@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andrew.co@free.fr \
    --cc=bastian@rieck.me \
    --cc=bernie@codewiz.org \
    --cc=danielmorgan@disroot.org \
    --cc=grzegorz.alibozek@gmail.com \
    --cc=jorge.cep.mart@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=maniette@gmail.com \
    --cc=meven29@gmail.com \
    --cc=nate@kde.org \
    --cc=pchernik@gmail.com \
    --cc=rubin@starset.net \
    --cc=saipavanchitta1998@gmail.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;
as well as URLs for NNTP newsgroup(s).