From: Shuah Khan <skhan@linuxfoundation.org>
To: Sean Young <sean@mess.org>, Matthew Wilcox <willy@infradead.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
kernel test robot <oliver.sang@intel.com>,
Alexei Starovoitov <ast@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
lkp@lists.01.org, kbuild test robot <lkp@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/ir: fix build with ancient kernel headers
Date: Tue, 1 Feb 2022 10:42:18 -0700 [thread overview]
Message-ID: <bb937121-64e4-ea34-e97b-a555ba283a5d@linuxfoundation.org> (raw)
In-Reply-To: <YflpnYECZE2Kxh+V@gofer.mess.org>
On 2/1/22 10:10 AM, Sean Young wrote:
> On Tue, Feb 01, 2022 at 04:58:48PM +0000, Matthew Wilcox wrote:
>> On Tue, Feb 01, 2022 at 04:53:11PM +0000, Sean Young wrote:
>>> +/* Support ancient lirc.h which does not have these values */
>>
>> Can we have a little more information here, such as "Can be removed once
>> RHEL 8 is no longer a relevant testing platform"? That will save people
>> doing archaology to find out when it's safe to remove.
>
> That totally makes sense.
>
> Having said that, I have no idea what platforms are being used for testing,
> so I don't know if RHEL 8 is the only one that needs this. Is there anyone
> who could shed some light on what platforms should be supported?
>
> Thanks,
>
> Sean
>
Sean,
It isn't important on platforms that get tested. We really don't have much
control over the platforms these tests get run.
Let's add a FIXME to remove and also add link to the kbuild thread where with
the discussion.
I am assuming this has to go through bpf since it fixes the commit already
in that tree:
With the change Matthew requested,
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Or I can take this through my tree.
thanks,
-- SHuah
prev parent reply other threads:[~2022-02-01 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 7:53 [tools headers UAPI] e2bcbd7769: kernel-selftests.ir.make_fail kernel test robot
2022-01-28 9:31 ` Sean Young
2022-01-28 16:49 ` Alexei Starovoitov
2022-01-28 17:27 ` Shuah Khan
2022-01-28 17:38 ` Sean Young
2022-01-28 17:57 ` Shuah Khan
2022-02-01 16:51 ` Sean Young
2022-02-01 16:53 ` [PATCH] selftests/ir: fix build with ancient kernel headers Sean Young
2022-02-01 16:58 ` Matthew Wilcox
2022-02-01 17:10 ` Sean Young
2022-02-01 17:42 ` Shuah Khan [this message]
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=bb937121-64e4-ea34-e97b-a555ba283a5d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=sean@mess.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox