From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Takashi Iwai <tiwai@suse.de>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel
Date: Wed, 29 Mar 2023 15:40:44 +0700 [thread overview]
Message-ID: <ZCP5jOTNypwG4xK6@debian.me> (raw)
In-Reply-To: <652a9a96-f499-f31f-2a55-3c80b6ac9c75@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Tue, Mar 28, 2023 at 04:39:01PM +0200, Paul Menzel wrote:
> Does openSUSE Tumbleweed make it easy to bisect the regression at least on
> “rc level”? It be great if narrow it more down, so we know it for example
> regressed in 6.2-rc7.
>
Alternatively, can you do bisection using kernel sources from Linus's
tree (git required)?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-29 8:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:40 [REGRESSION] e1000e probe/link detection fails since 6.2 kernel Takashi Iwai
2023-03-28 14:39 ` [Intel-wired-lan] " Paul Menzel
2023-03-28 15:16 ` Takashi Iwai
2023-03-29 8:40 ` Bagas Sanjaya [this message]
2023-03-29 8:48 ` Takashi Iwai
2023-03-29 19:12 ` Jakub Kicinski
2023-03-30 6:30 ` Takashi Iwai
2023-03-30 10:35 ` Takashi Iwai
2023-04-02 7:38 ` Neftin, Sasha
2023-03-29 8:43 ` Bagas Sanjaya
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=ZCP5jOTNypwG4xK6@debian.me \
--to=bagasdotme@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--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 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).