public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "ihuguet@redhat.com" <ihuguet@redhat.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"jtornosm@redhat.com" <jtornosm@redhat.com>,
	"Ben Ami, Golan" <golan.ben.ami@intel.com>,
	"Sade, Jonathan" <jonathan.sade@intel.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"ltrivell@redhat.com" <ltrivell@redhat.com>
Subject: Re: iwlwifi: AC9560 firmware crash with iwlwifi-QuZ-a0-jf-b0 versions above 55
Date: Mon, 12 Dec 2022 10:18:47 +0000	[thread overview]
Message-ID: <806520543550b16201bf54b9be29920446ee3e8c.camel@intel.com> (raw)
In-Reply-To: <CACT4oufQsqHGp6bah2c4+jPn2wG1oZqY=UKa_TmPx=F6Lxng8Q@mail.gmail.com>

On Mon, 2022-12-12 at 11:06 +0100, Íñigo Huguet wrote:
> On Mon, Nov 21, 2022 at 5:35 PM Íñigo Huguet <ihuguet@redhat.com> wrote:
> > 
> > On Mon, Nov 21, 2022 at 12:08 PM Íñigo Huguet <ihuguet@redhat.com> wrote:
> > > > the fw 74 seems to be a different issue - could you post more info about
> > > > separately?
> > 
> > This was my fault: I was checking many different things, and I checked
> > this with an outdated kernel. With latest wireless tree and fw-74 it
> > works fine, both with the patch from this thread and without it. Sorry
> > for the noise.
> > 
> > So I will wait  for this patch to be posted so I can backport it to
> > RHEL, but using fw-74 also fixes the issue, as you said.
> 
> Hi Johannes, following with this: will anyone from Intel post this
> patch? I can do it on your behalf, but I thought you'd prefer to do it
> yourself.
Hi! Yes sure, I'll send this patch.
> 
> > 
> > Thanks
> > 
> > --
> > Íñigo Huguet
> 
> 
> 

Regards,
Gregory

      reply	other threads:[~2022-12-12 10:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 10:41 iwlwifi: AC9560 firmware crash with iwlwifi-QuZ-a0-jf-b0 versions above 55 Íñigo Huguet
2022-10-05  9:35 ` Johannes Berg
2022-10-05  9:50   ` Íñigo Huguet
2022-10-05 10:06     ` Johannes Berg
2022-10-05 10:09       ` Íñigo Huguet
2022-11-21  8:32       ` Íñigo Huguet
2022-11-21 10:42         ` Johannes Berg
2022-11-21 11:08           ` Íñigo Huguet
2022-11-21 16:35             ` Íñigo Huguet
2022-12-12 10:06               ` Íñigo Huguet
2022-12-12 10:18                 ` Greenman, Gregory [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=806520543550b16201bf54b9be29920446ee3e8c.camel@intel.com \
    --to=gregory.greenman@intel.com \
    --cc=golan.ben.ami@intel.com \
    --cc=ihuguet@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=jonathan.sade@intel.com \
    --cc=jtornosm@redhat.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ltrivell@redhat.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