All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:58:55 +0100	[thread overview]
Message-ID: <2024010337-claw-overdrawn-2c36@gregkh> (raw)
In-Reply-To: <CAHxc4bsa2L5wM78YGZ-aJ3wTJnWatXRrqK5CFa4NEdHzs1zmRA@mail.gmail.com>

On Wed, Jan 03, 2024 at 03:23:13PM +0530, Dileep Sankhla wrote:
> On Wed, Jan 3, 2024 at 12:33 PM Greg KH <greg@kroah.com> wrote:
> > What do you mean by "first bug"?  Why does the location in an
> > arbitrary list matter?
> 
> Hello Greg,
> 
> >From "first bug" I meant the initial bug for me to solve under this subsystem.
> 
> > Also, bugzilla is not used by many kernel subsystems, so perhaps the
> > items there just aren't relevant for this one either?
> 
> I looked for the bugs in the subsystem's mailing list but did not find
> anything beginning with the subject line "PROBLEM: ".

I have never seen a bug report for the kernel come in with that in the
subject line, sorry.  So that would be one reason why you might not find
anything.

And maybe there are no x86-specific bugs at the moment?  Try running
linux-next and see if you have any issues with any subsystem, if so, try
working on that.

good luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2024-01-03  9:59 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
2024-01-03  9:53   ` Dileep Sankhla
2024-01-03  9:58     ` Greg KH [this message]
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=2024010337-claw-overdrawn-2c36@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.