From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 69A39C3DA6E for ; Wed, 3 Jan 2024 07:04:03 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96.2) (envelope-from ) id 1rKvHc-0001Wh-35; Wed, 03 Jan 2024 02:03:20 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1rKvHY-0001V7-0O for kernelnewbies@kernelnewbies.org; Wed, 03 Jan 2024 02:03:19 -0500 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 039A65C0151; Wed, 3 Jan 2024 02:03:08 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 03 Jan 2024 02:03:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1704265387; x=1704351787; bh=5F5KqB2f8N QFfQ35fWk/DuozRRHZogZIVQY0Vz20yHc=; b=OuP0nPGArzru4pvJ+7TA3WA43k 1UYCSA5A2IrEGFGXkCuLTUNnC3XAZTjCOUgnXPWFidC8TShpm/MM2F5+MdiTOdtf WdzZrEczc81ZlAHavSouPeu4O3kXEJlS3QbOHFUsFyP/NwTo9NV1oU9sN7K2w9W2 aaPONrw8MHFy4rnbZz48/D1dgpA25cot61ecAZ0sQgDhoU3zkVKtaY7Uhmzy1kiq Q/ic/ofsTQ7Mrj3v5bmyLnSlpCWz49rsbdhQiUWLtBisgD3ShJbbYSC+b3MNXwjs jZudLXeAcYSnw0mtkQBkjSbcnHkXdIHBVMqP1A939YYrNj/MlEwWi4cEinYg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1704265387; x=1704351787; bh=5F5KqB2f8NQFfQ35fWk/DuozRRHZ ogZIVQY0Vz20yHc=; b=50HNjWhcNz6iaAwIoZNICUr0W7BqjfytgKZEdZZ2EyKg wgANvjUuW0C7NpCzpKit8HUxU6ZvxHs3d+jVuxuEpgFUYGzHfzRSClAY71tMV8hn TfHYPjen82hvSJjgawr1rQtcV2yTLmyKODeGQZSvQzvAWitDLxmlTtEtfPT3DdE6 7CEEcZr8PQVvBAcMEg6Y1PCoqYxCluSWnGsQGHg6Gs1UDZ2FiiYk00/QuxQtikRf jC9715uPYLb+MFZ83TQ5EvmpxVF0pbsg/5UURiZJGV5GP9r2jo8LtNzCR91aOXi5 DEXW3JXe5ZjHJWxBcOQ7OzCOA4g9Zd+XEW6UlD+vnw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeggedguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkfhggtggujgesth dtredttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtgho mheqnecuggftrfgrthhtvghrnhepheegvdevvdeljeeugfdtudduhfekledtiefhveejke ejuefhtdeufefhgfehkeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 3 Jan 2024 02:03:07 -0500 (EST) Date: Wed, 3 Jan 2024 08:03:06 +0100 From: Greg KH To: Dileep Sankhla Subject: Re: Identifying the initial bug within the x86 architecture subsystem Message-ID: <2024010356-slightly-surpass-95e8@gregkh> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org 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