From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=95.215.58.245 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793782583; b=nuHl46nwIaty0UfI2ZPzcke9qGkOiDy+q4Mwdvc0RknFufNsZMQU8kpMhKOrGFNW5es5 /Az8WlBCOCxvu7CEXJqPWBGwNRkKAtJvRT5WtsWi0bz467YzOZtU800DiYbIyQeLfSfZb 9Rg3VqNbIn0smaqVLErfQmMcy1XPLK2l5fmxH5ovUGESuF70dcxD5AvmWt0Yav1OXWbVu 5npjScNvjRqL7Xb6PefvQY832542IPUovuFrIdnQOsxy12bvgR0Bt/EwseTJ6TUEuxeVw saljyzBvpZAvBKuRc+nindoN7EGoAC7oaiiWIzZ2nBQlCrSm0+UoGc5XomHTzHAcPkA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793782583; h=DMARC-Filter:X-Envelope-To:DKIM-Signature:X-Envelope-To:Received: X-Mizu-Trace-ID:X-Migadu-Flow:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=qQVf7f8PLUUHBAmAuq6jyGQHg8S9QNMMQm8JtMB1S4U=; b=Y9YeplIKrO6XYH3ZwAEsNC8vO2LfmRczER5CtdXMo9GhQxMxby9eL1t+mLY5RMjzsVYq 4vd5HYxfnIorrgffAcD4Qvc4FS5ASD2znDsuuchDL+LTdSPN14mggR93AlJ3crm+Nw4QW Cfr9KFgeecasiWrXL5/V+jiu04o/iTmnfkpChbQkfLxvbgDmUccDxrBreYMSQLd9Dv+nt uxws1ghHArZJx9sYtKIinZgdPeix+Qz/MGTt6e4Lf/q8nW9uDL9gQL5sTdxXWSBnj6L09 QG2Jsoh+wSELyoctagRE/70m+4utyb/LtLe4aL82dEYbO0yUm0NcDqivoBmztjlVnGg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=wyuan.org; spf=pass smtp.mailfrom=wyuan.org; dkim=pass header.d=wyuan.org header.i=@wyuan.org header.a=rsa-sha256 header.s=key1 header.b="mu/vzX2e"; arc=none smtp.remote-ip=95.215.58.245 Received: from mta1.migadu.com (out-245.mta1.migadu.com [95.215.58.245]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CB716606A326 for ; Wed, 4 Nov 2026 08:56:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org CB716606A326 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=wyuan.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=wyuan.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=wyuan.org header.i=@wyuan.org header.a=rsa-sha256 header.s=key1 header.b=mu/vzX2e X-Envelope-To: linux-doc@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=SqR9VFOeiKuAqJ+nLJmdz88eGFRmKKQAFSp14MozLnw=; c=simple/simple; d=wyuan.org; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1793782575; v=1; x=1794387375; b=mu/vzX2egO4H0XxpgFl7mSyNARjp+fHTHsrx4JNMo2YK8QTutryukhmv1zONKDtiFOe9EV3f qWsS7XHPkZuWsjq37wfTvQKv0CeosFFMq4ounwaa7IaMMTvhaVTbyXXHsIY30U86VExVZ+sPlOb uMtvtTY01LNh5N6t7D7xjmXCKuY0Gjyvebt9P9ei8e5CGHc5r00jga1rDo8vchmJqWRFoHzVS5a 5QmS2ONcim5tk2g6K1t9zLdSqVkWYdt13HDHDu5aUXAuLHkBStoeQQ6dF+uHaqzA71LYWtbXRj4 GfsvZDcOJetyCB/A9udH6VpbJXJMeI5d6Ncyu9v4lkZbQ== X-Envelope-To: linux-doc@vger.kernel.org Received: by smtp.migadu.com with ESMTPS id 36180429a31982d8; Wed, 04 Nov 2026 08:56:15 +0000 X-Mizu-Trace-ID: 36180429a31982d8 X-Migadu-Flow: FLOW_OUT Date: Wed, 4 Nov 2026 16:56:12 +0800 From: Weijie Yuan To: Jonathan Corbet Cc: Weijie Yuan , Dongliang Mu , Alex Shi , Yanteng Si , Shuah Khan , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: How to attempt to gradually eliminate the compilation output? Message-ID: References: <87y0b99i6p.fsf@trenco.lwn.net> <87tslx9ee9.fsf@trenco.lwn.net> X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87tslx9ee9.fsf@trenco.lwn.net> Jonathan Corbet writes: > Weijie Yuan writes: > > > Jonathan Corbet writes: > > > >> Weijie Yuan writes: > >> > >> > Recently I've sent several patches to fix warnings. But since I am not > >> > familiar with the actual codes of theirs, I'm not confident enough to > >> > touch some parts, but only the most obvious ones. > >> > > >> > Since this is a goal that Jon has spent years for, I'm wondering if it's > >> > possible to periodically send out some email notifications, which will > >> > use the file paths from the compiled output to find the recipients and > >> > kindly ask them to to deal with these annoying outputs? Perhaps we could > >> > use a script to do this.? > >> > >> I think that nagging others to fix warnings is not going to make anybody > >> happy. > > > > That's sure and that wasn't what I intended. > > > > I'd be happy to do the work, but putting myself in their shoes, I worry > > they might think, "Someone from nowhere, who isn't familiar with our > > development process/workflow, is sending patches and just adding noise. > > It would be quicker and easier if they simply pointed out the problems > > and let us fix them ourselves." > > > > For example, last week I was about to send a small patch when, > > fortunately, I searched lore one more time and found that an equivalent > > patch had already been posted to their list, but hadn't been merged yet. > > > > These warnings span many subsystems, and I worry that sending patches > > before I understand their respective workflows might come across as a > > bit impolite: "We already have this fix in our development tree; you > > should have checked first." > > Well-intentioned patches are rarely seen as impolite. > > It's always worth looking at linux-next before trying to fix something; > if there is a fix in their tree, it should really be there as well. Thanks, learned a lot indeed. It turns out that what I was worried about already had a solution. Will take a look at linux-next each time later. Thanks!