LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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
Date: Wed, 11 May 2022 07:32:02 +0200	[thread overview]
Message-ID: <YntKUn8AZKpLbBTp@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2205102341030.52331@angie.orcam.me.uk>

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

  reply	other threads:[~2022-05-11  5:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 21:58 Stephen Rothwell
2022-05-10 22:46 ` Maciej W. Rozycki
2022-05-11  5:32   ` Greg KH [this message]
2022-05-13 22:47     ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2022-06-14  6:47 Stephen Rothwell
2018-03-15  6:43 Stephen Rothwell
2018-03-15 17:34 ` Greg KH
2015-03-10  5:37 Stephen Rothwell
2010-12-21  7:11 Stephen Rothwell
2010-12-21 19:42 ` Greg KH
2011-01-10  0:49   ` Stephen Rothwell
2011-01-10  0:51     ` Kay Sievers
2011-01-10  0:56     ` Greg KH
2011-01-10  1:59       ` Stephen Rothwell
2011-01-10  5:49         ` Greg KH
2011-01-10 14:55         ` Kay Sievers

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=YntKUn8AZKpLbBTp@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: build warnings after merge of the tty tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).