Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
Date:   Tue, 10 Oct 2023 01:16:03 +0100 (BST)
From:   "Maciej W. Rozycki" <macro@orcam.me.uk>
To:     "Guilherme G. Piccoli" <gpiccoli@igalia.com>
cc:     linux-alpha@vger.kernel.org, mattst88@gmail.com,
        linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
        kernel@gpiccoli.net, Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
        Richard Henderson <richard.henderson@linaro.org>,
        Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v5] alpha: Clean-up the panic notifier code
In-Reply-To: <20230902165725.3504046-1-gpiccoli@igalia.com>
Message-ID: <alpine.DEB.2.21.2310100109100.48714@angie.orcam.me.uk>
References: <20230902165725.3504046-1-gpiccoli@igalia.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Sat, 2 Sep 2023, Guilherme G. Piccoli wrote:

> So, let's clean the code and set the notifier to run as the
> latest, following the same approach other architectures are
> doing - also, remove the unnecessary include of a header already
> included indirectly.

 FWIW my understanding is our current policy is not to rely on indirect 
inclusions and if a given source relies on declarations or definitions 
provided by a header, then it is supposed to pull it explicitly.

 And in any case such an unrelated self-contained change is expected to be 
sent as a separate patch, in a series if there's a mechanical dependency.

  Maciej