Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: John Hubbard <jhubbard@nvidia.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>,
	Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Valentin Obst <kernel@valentinobst.de>,
	linux-kselftest@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev, x86@kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 0/7] selftests/x86: fix build errors and warnings found via clang
Date: Tue, 9 Jul 2024 14:51:39 -0600	[thread overview]
Message-ID: <78c3ed1e-32b2-43aa-9979-0479fa524018@linuxfoundation.org> (raw)
In-Reply-To: <49c14f8f-0c08-41e0-b987-7c4253edf6de@nvidia.com>

On 7/9/24 14:40, John Hubbard wrote:
> On 7/9/24 1:34 PM, Shuah Khan wrote:
>> On 7/4/24 01:24, John Hubbard wrote:
> ...>> Muhammad Usama Anjum (1):
>>>    selftests: x86: test_FISTTP: use fisttps instead of ambiguous fisttp
>>
>>
>> Usama and John,
>>
>> I am seeing checkpatch warnings in this series.
>>
>> v4-3-7
>> WARNING: externs should be avoided in .c files
>> #210: FILE: tools/testing/selftests/x86/fsgsbase_restore.c:46:
>> +unsigned int dereference_seg_base(void);

This one looked new though.

thanks,
-- Shuah

  reply	other threads:[~2024-07-09 20:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  7:24 [PATCH v4 0/7] selftests/x86: fix build errors and warnings found via clang John Hubbard
2024-07-04  7:24 ` [PATCH v4 1/7] selftests/x86: fix Makefile dependencies to work with clang John Hubbard
2024-07-04  7:24 ` [PATCH v4 2/7] selftests: x86: test_FISTTP: use fisttps instead of ambiguous fisttp John Hubbard
2024-07-04  7:24 ` [PATCH v4 3/7] selftests/x86: build fsgsbase_restore.c with clang John Hubbard
2024-07-04  7:24 ` [PATCH v4 4/7] selftests/x86: build sysret_rip.c " John Hubbard
2024-07-04  7:24 ` [PATCH v4 5/7] selftests/x86: avoid -no-pie warnings from clang during compilation John Hubbard
2024-07-04  7:24 ` [PATCH v4 6/7] selftests/x86: remove (or use) unused variables and functions John Hubbard
2024-07-04  7:24 ` [PATCH v4 7/7] selftests/x86: fix printk warnings reported by clang John Hubbard
2024-07-09 20:34 ` [PATCH v4 0/7] selftests/x86: fix build errors and warnings found via clang Shuah Khan
2024-07-09 20:40   ` John Hubbard
2024-07-09 20:51     ` Shuah Khan [this message]
2024-07-09 20:55       ` Shuah Khan

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=78c3ed1e-32b2-43aa-9979-0479fa524018@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=adobriyan@gmail.com \
    --cc=angquan21@gmail.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jhubbard@nvidia.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