Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 17 Jul 2023 12:55:04 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Chin Yik Ming <yikming2222@gmail.com>
Cc:     mingo@redhat.com, juri.lelli@redhat.com,
        vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
        rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
        bristot@redhat.com, vschneid@redhat.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Fixed typo in comment
Message-ID: <20230717105504.GG4253@hirez.programming.kicks-ass.net>
References: <20230717064952.2804-1-yikming2222@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230717064952.2804-1-yikming2222@gmail.com>
Precedence: bulk

On Mon, Jul 17, 2023 at 02:49:52PM +0800, Chin Yik Ming wrote:
> task_struct's state member is prefixed by "__"

This isn't a typo, the member got renamed long after these comments were
written.

Also, nobody should be accessing task->__state, so it being spelled
wrong in a comment doesn't seem like a problem to me.