All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Darbro <bdarbro@xevo.com>
To: "tiwai@suse.de" <tiwai@suse.de>, Luca Coelho <luca@coelho.fi>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"luca@coelho.fi" <luca@coelho.fi>,
	"emmanuel.grumbach@intel.com" <emmanuel.grumbach@intel.com>,
	"johannes.berg@intel.com" <johannes.berg@intel.com>,
	"jwboyer@kernel.org" <jwboyer@kernel.org>,
	"dor.shaish@intel.com" <dor.shaish@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression with the latest iwlwifi-9260-*-46.ucode
Date: Thu, 25 Jul 2019 21:20:17 +0000	[thread overview]
Message-ID: <19a71f97-511a-2459-13c0-097766208dae@xevo.com> (raw)
In-Reply-To: <adc640f5dc37e63283f48a9ce3c082cc8219638e.camel@xevo.com>

On 7/22/19 4:24 PM, Brandon Darbro wrote:
> Ubuntu bug tracking the same issue.
>
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836986
>
Hello Luca,

Any updated information on this iwlwifi-9260 firmware 46 issue?  Is 
there bug tracker or repo I should be looking to for following the 
progress on it?

--
Thank you,
Brandon

  reply	other threads:[~2019-07-25 21:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 15:35 Regression with the latest iwlwifi-9260-*-46.ucode Takashi Iwai
2019-07-19 16:36 ` Luciano Coelho
2019-07-19 18:07   ` Takashi Iwai
2019-07-20 20:42     ` Takashi Iwai
2019-07-20 20:49       ` Luca Coelho
2019-07-21 16:43         ` Takashi Iwai
2019-07-22 23:24           ` Brandon Darbro
2019-07-25 21:20             ` Brandon Darbro [this message]
2019-08-05  9:48           ` Luca Coelho
2019-08-05  9:53             ` Luca Coelho
2019-08-05 10:05               ` Takashi Iwai
2019-08-05 10:10                 ` Luca Coelho
2019-08-05 12:03                   ` Luca Coelho
2019-08-06 13:04                     ` Takashi Iwai
2019-08-09 19:00                       ` Thomas Backlund
2019-08-20 13:11                         ` Luca Coelho

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=19a71f97-511a-2459-13c0-097766208dae@xevo.com \
    --to=bdarbro@xevo.com \
    --cc=dor.shaish@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=tiwai@suse.de \
    /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.