BPF List
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Alan Maguire <alan.maguire@oracle.com>,
	Potnuri Bharat Teja <bharat@chelsio.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Nilay Shroff <nilay@linux.ibm.com>
Subject: Re: Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_CHELSIO_T4=y (was CONFIG_KCSAN)
Date: Fri, 21 Nov 2025 09:22:10 -0800	[thread overview]
Message-ID: <452a2c4c-e9eb-40a0-922b-a1b99048ee08@acm.org> (raw)
In-Reply-To: <bc54daab-3b01-4a25-8032-52a123fa823f@oracle.com>

On 11/20/25 2:18 PM, Alan Maguire wrote:
> FYI I verified that changing sched_class to ch_sched_class like the
> following resolves the build issue:

Since the Chelsio cxgb4 maintainer has not yet responded, how about
posting these changes as a formal patch? If this change is posted as
a formal patch, feel free to add:

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

Thanks,

Bart.

  reply	other threads:[~2025-11-21 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 20:40 Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_KCSAN are enabled Bart Van Assche
2025-11-18 12:07 ` Alan Maguire
2025-11-18 16:47   ` Bart Van Assche
2025-11-20 14:20     ` Alan Maguire
2025-11-20 17:53       ` Kernel build fails if both CONFIG_DEBUG_INFO_BTF and CONFIG_CHELSIO_T4=y (was CONFIG_KCSAN) Alan Maguire
2025-11-20 18:05         ` Potnuri Bharat Teja
2025-11-20 22:18           ` Alan Maguire
2025-11-21 17:22             ` Bart Van Assche [this message]
2025-11-21 18:15               ` Alan Maguire
2025-11-24 11:48                 ` Potnuri Bharat Teja

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=452a2c4c-e9eb-40a0-922b-a1b99048ee08@acm.org \
    --to=bvanassche@acm.org \
    --cc=alan.maguire@oracle.com \
    --cc=bharat@chelsio.com \
    --cc=bpf@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=nilay@linux.ibm.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