From: Greg KH <greg@kroah.com>
To: Dileep Sankhla <dileepsankhla.ds@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Identifying the initial bug within the x86 architecture subsystem
Date: Wed, 3 Jan 2024 08:03:06 +0100 [thread overview]
Message-ID: <2024010356-slightly-surpass-95e8@gregkh> (raw)
In-Reply-To: <CAHxc4bugoJuw=JwkrsWYphip8bkuQwJUtt4ipR3PwdxxY-JO_g@mail.gmail.com>
On Wed, Jan 03, 2024 at 11:12:57AM +0530, Dileep Sankhla wrote:
> Last night, I dedicated time to go through bugs on Bugzilla (see [1]),
> considering their priorities but I could not figure out which one to
> pick. While I found only a couple of bugs with the latest modification
> date, I lack the same hardware as the original poster (OP) to
> reproduce and fix those bugs. How can I identify the first bug in this
> subsystem? Given the relatively low number of bugs, should I consider
> reaching out to the maintainer of `arch/x86/boot` if I cannot find a
> suitable one to fix?
What do you mean by "first bug"? Why does the location in an
arbitrary list matter?
Also, bugzilla is not used by many kernel subsystems, so perhaps the
items there just aren't relevant for this one either?
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2024-01-03 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 5:42 Identifying the initial bug within the x86 architecture subsystem Dileep Sankhla
2024-01-03 7:03 ` Greg KH [this message]
2024-01-03 9:53 ` Dileep Sankhla
2024-01-03 9:58 ` Greg KH
2024-01-03 10:08 ` Dileep Sankhla
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=2024010356-slightly-surpass-95e8@gregkh \
--to=greg@kroah.com \
--cc=dileepsankhla.ds@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/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.