public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Dave Hansen <dave.hansen@intel.com>, Shuah Khan <shuah@kernel.org>
Cc: angquan yu <angquan21@gmail.com>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	Sohil Mehta <sohil.mehta@intel.com>,
	Yu-cheng Yu <yu-cheng.yu@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Valentin Obst <kernel@valentinobst.de>,
	linux-kselftest@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev, x86@kernel.org,
	Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang
Date: Thu, 30 May 2024 13:00:55 -0700	[thread overview]
Message-ID: <44428518-4d21-4de7-8587-04eceefb330d@nvidia.com> (raw)
In-Reply-To: <4d2c93e8-5ab0-4b28-af24-c00d57f359fe@intel.com>

On 5/30/24 12:46 PM, Dave Hansen wrote:
> On 5/27/24 14:00, John Hubbard wrote:
>> John Hubbard (6):
>>    selftests/x86: build test_FISTTP.c with clang
>>    selftests/x86: build fsgsbase_restore.c with clang
>>    selftests/x86: build sysret_rip.c with clang
>>    selftests/x86: avoid -no-pie warnings from clang during compilation
>>    selftests/x86: remove (or use) unused variables and functions
>>    selftests/x86: fix printk warnings reported by clang
> 
> John, could you and Muhammad have a chat and perhaps settle on a series
> series that gets acks from both of you?
> 
>> https://lore.kernel.org/all/20240501122918.3831734-1-usama.anjum@collabora.com/
> 
> I had Muhammad's in my queue and didn't realize we had two overlapping
> series' bouncing around until now.

Aha OK. Muhummad, after looking through this, I see that our
test_FISTTP.c fix is identical, and that's about it. My series goes
a bit deeper IMHO and completely fixes all the errors; the tradeoff
is that it is more intrusive. Which I think is appropriate.

Would you be OK with my posting v3 that uses your patch for
test_FISTTP.c [1], and the rest of my patches for the rest?


[1] 
https://lore.kernel.org/all/20240501122918.3831734-7-usama.anjum@collabora.com/

thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2024-05-30 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 21:00 [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang John Hubbard
2024-05-27 21:00 ` [PATCH v2 1/6] selftests/x86: build test_FISTTP.c with clang John Hubbard
2024-05-27 21:00 ` [PATCH v2 2/6] selftests/x86: build fsgsbase_restore.c " John Hubbard
2024-05-27 21:00 ` [PATCH v2 3/6] selftests/x86: build sysret_rip.c " John Hubbard
2024-05-27 21:00 ` [PATCH v2 4/6] selftests/x86: avoid -no-pie warnings from clang during compilation John Hubbard
2024-05-27 21:00 ` [PATCH v2 5/6] selftests/x86: remove (or use) unused variables and functions John Hubbard
2024-05-27 21:00 ` [PATCH v2 6/6] selftests/x86: fix printk warnings reported by clang John Hubbard
2024-05-30 14:58 ` [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang Shuah Khan
2024-05-30 19:21   ` John Hubbard
2024-05-30 19:46 ` Dave Hansen
2024-05-30 20:00   ` John Hubbard [this message]
2024-05-31  5:12     ` Muhammad Usama Anjum

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=44428518-4d21-4de7-8587-04eceefb330d@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=adobriyan@gmail.com \
    --cc=angquan21@gmail.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel@valentinobst.de \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=shuah@kernel.org \
    --cc=sohil.mehta@intel.com \
    --cc=usama.anjum@collabora.com \
    --cc=x86@kernel.org \
    --cc=yu-cheng.yu@intel.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