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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F8BDC61DA7 for ; Thu, 26 Jan 2023 22:54:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233075AbjAZWyp (ORCPT ); Thu, 26 Jan 2023 17:54:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233000AbjAZWye (ORCPT ); Thu, 26 Jan 2023 17:54:34 -0500 Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D53D74FAFF for ; Thu, 26 Jan 2023 14:54:29 -0800 (PST) Received: by mail-il1-x131.google.com with SMTP id g15so1444540ild.3 for ; Thu, 26 Jan 2023 14:54:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=4YOljWyGQiSDuWcg4PQG6vSllKDFhB9jVbes21tjtGs=; b=YK8qP085Bvta3Nfw6rwSlDN3b2YCnwzGBK+SlpHBmCm8Cca5p1UcVmiO+CgBRuaGru mtfMKh8eO+ltKfPoOwqCC75A8aJdkaTZuhM62ADET+LG21AOPi513wU1nIdR1YqTtU1t SNKUbHOdlwb8sHPb32SqisRbzaLS7k8Y2LK1M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4YOljWyGQiSDuWcg4PQG6vSllKDFhB9jVbes21tjtGs=; b=u1w6YRX44ZB0m/YtpgVUDHO46fTz7gZRB+mKFE/mtM00GtPElLWxY0uY8g76K/62x3 LxYb3AmgNh/xqXGulFar+3lS3te+I7xVd/G/3U512Ka9Ge3feGZ1rbYXpUQQZBqm+epF 2BCSoZ05HvWljopiEVmPpr9+lKxqR4bq4LLhUm/LYMoVSyqSwX1Qu9gnFNbxfbbcRt06 IUJZomexJqdeeHDVoX1xwpxyI9kDyBJW3bMtHCeaRRKhU+Wk66wFau1ooZv6hTu5Q3+T tK6AgJ+71peYrEFAWtdFwREVwQ6y3Pw6uHDlcVoFIKMaMfxjwR4SsRIupRiNxm3ZdZpS cCpw== X-Gm-Message-State: AO0yUKUImCDJ7vHlzftIATbilcIPX+QfAkSA90j5T4xmEDQ2Lr4zEQ0+ NvrwBcqDX1DQZ+jMpOvmGA8JAg== X-Google-Smtp-Source: AK7set9imA/gYnoLNO9UwE1NbKQQNZm5PPCorp0iwwdfhgwKqUaGGLBLOCuzHOqwTIU1hvJsLx611Q== X-Received: by 2002:a92:6810:0:b0:310:9adc:e1bb with SMTP id d16-20020a926810000000b003109adce1bbmr1453260ilc.0.1674773669138; Thu, 26 Jan 2023 14:54:29 -0800 (PST) Received: from [192.168.1.128] ([38.15.45.1]) by smtp.gmail.com with ESMTPSA id h31-20020a022b1f000000b00363f8e0ab41sm836828jaa.152.2023.01.26.14.54.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Jan 2023 14:54:28 -0800 (PST) Message-ID: <604dc49a-fd03-4407-0e13-d16022ba81c4@linuxfoundation.org> Date: Thu, 26 Jan 2023 15:54:27 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [RFC PATCH] selftests: Fix: search kernel headers in $(KHDR_INCLUDES) Content-Language: en-US To: Mathieu Desnoyers , Shuah Khan Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, Ingo Molnar , stable@vger.kernel.org, Shuah Khan References: <20230117201724.11869-1-mathieu.desnoyers@efficios.com> From: Shuah Khan In-Reply-To: <20230117201724.11869-1-mathieu.desnoyers@efficios.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/17/23 13:17, Mathieu Desnoyers wrote: > Use $(KHDR_INCLUDES) as lookup path for kernel headers. This prevents > building against kernel headers from the build environment in scenarios > where kernel headers are installed into a specific output directory > (O=...). > The change looks good to me. > [ Hopefully I did not break too many things with this selftests-wide > change. Additional testing would be welcome before merging, especially > given that whenever we get this wrong, it appears to fall-back on the > build environment system headers, which hides issues. This applies on > top of v6.2-rc3. ] > One concern with treewide change is the merge conflicts. Selftests go through several trees as you may already know. Would it be possible for you send patch series instead? Patch series will help us avoid merge conflict issues. I will run tests on this patch and let you know in the meatime. thanks, -- Shuah