From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Maciej W. Rozycki" <macro@embecosm.com>,
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.current tree
Date: Thu, 27 Jan 2022 08:31:46 +0100 [thread overview]
Message-ID: <YfJKYj3UOYQIHsb0@kroah.com> (raw)
In-Reply-To: <YfJIUIj1mDcShwpV@kroah.com>
On Thu, Jan 27, 2022 at 08:22:56AM +0100, Greg KH wrote:
> On Thu, Jan 27, 2022 at 09:18:00AM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tty.current tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> > In file included from <command-line>:
> > ./usr/include/linux/cyclades.h:6:2: warning: #warning "Support for features provided by this header has been removed" [-Wcpp]
> > 6 | #warning "Support for features provided by this header has been removed"
> > | ^~~~~~~
> > ./usr/include/linux/cyclades.h:7:2: warning: #warning "Please consider updating your code" [-Wcpp]
> > 7 | #warning "Please consider updating your code"
> > | ^~~~~~~
> >
> >
> > Introduced by commit
> >
> > f23653fe6447 ("tty: Partially revert the removal of the Cyclades public API")
> >
> > This is a bit annoying :-(
>
> Sorry, odd it doesn't show up in my builds, nor in 0-day.
Ah, 0-day reported it on the original patch, but not once it was in my
tree. odd.
next prev parent reply other threads:[~2022-01-27 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:18 linux-next: build warnings after merge of the tty.current tree Stephen Rothwell
2022-01-27 7:22 ` Greg KH
2022-01-27 7:31 ` Greg KH [this message]
2022-01-27 7:36 ` Greg KH
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=YfJKYj3UOYQIHsb0@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@embecosm.com \
--cc=sfr@canb.auug.org.au \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox