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:   Wed, 11 May 2022 07:32:02 +0200
From:   Greg KH <greg@kroah.com>
To:     "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the tty tree
Message-ID: <YntKUn8AZKpLbBTp@kroah.com>
References: <20220511075804.79c5b697@canb.auug.org.au>
 <alpine.DEB.2.21.2205102341030.52331@angie.orcam.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.21.2205102341030.52331@angie.orcam.me.uk>
Precedence: bulk

On Tue, May 10, 2022 at 11:46:26PM +0100, Maciej W. Rozycki wrote:
> On Wed, 11 May 2022, Stephen Rothwell wrote:
> 
> > After merging the tty tree, yesterday's linux-next build (htmldocs) produced
> > these warnings:
> 
>  Umm, sorry about that.  I wasn't even aware files under Documentation/ 
> are meant to be processed somehow other than through eyeballs nowadays!
> 
>  I'll see how to fix the file up and will make the necessary corrections, 
> but how shall I post the update?  A replacement patch or an incremental 
> change?

Incremental change as I can't rebase my tree.

thanks,

greg k-h