mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Linux Networking <netdev@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
	Simon Horman <simon.horman@corigine.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Kalle Valo <kvalo@kernel.org>,
	sardonimous@hotmail.com
Subject: Re: After kernel 6.3.7 or 6.3.8 b43 driver fails
Date: Sat, 24 Jun 2023 10:50:23 +0200	[thread overview]
Message-ID: <20230624105023.146d99e0@barney> (raw)
In-Reply-To: <27829c69-515c-36a6-4beb-3210225f8936@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

On Sat, 24 Jun 2023 08:44:15 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> > I suspect change introduced when addressing a compiler warning
> > cased the error.
> > 
> > https://patchwork.kernel.org/project/linux-wireless/patch/20230516183442.536589-1-arnd%40kernel.org/


I doubt it.
This patch affects the device initialization code. But the crash is in
the transmit path.
Can you please double check by manually reverting the patch?

-- 
Michael Büsch
https://bues.ch/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-24  9:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  1:44 Fwd: " Bagas Sanjaya
2023-06-24  8:50 ` Michael Büsch [this message]
2023-06-24  9:29   ` Arnd Bergmann
2023-06-24 14:00     ` Linux regression tracking (Thorsten Leemhuis)
2023-06-24 16:22       ` Larry Finger
2023-06-24 21:32 ` Fwd: " Arnd Bergmann
     [not found]   ` <RO2P215MB193850DDADD38492BEC8CC2FA720A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM>
2023-06-25  0:50     ` Bagas Sanjaya
2023-06-25  2:09       ` Larry Finger
2023-06-25  4:41       ` Larry Finger
2023-06-25 16:58         ` Sardonimous
2023-06-25 18:12           ` Arnd Bergmann
2023-06-25 18:17             ` Larry Finger
2023-06-25 21:11               ` Sardonimous
2023-06-25 23:05                 ` Larry Finger
2023-06-26 12:44                   ` Sardonimous
2023-06-26 15:21                     ` Larry Finger
2023-06-26 21:33                       ` Sardonimous
2023-06-27  0:31                         ` Larry Finger
2023-07-03 17:35                         ` Larry Finger
2023-07-03 20:13                           ` Sardonimous
2023-07-04  8:30                             ` Linux regression tracking #update (Thorsten Leemhuis)

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=20230624105023.146d99e0@barney \
    --to=m@bues.ch \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arnd@arndb.de \
    --cc=bagasdotme@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sardonimous@hotmail.com \
    --cc=simon.horman@corigine.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

all inboxes | Powered by JetHome®