From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3] tty: Partially revert the removal of the Cyclades public API
Date: Wed, 26 Jan 2022 14:50:13 +0100 [thread overview]
Message-ID: <YfFRlbKw4cV+ISfk@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2201260733430.11348@tpp.orcam.me.uk>
On Wed, Jan 26, 2022 at 09:22:54AM +0000, Maciej W. Rozycki wrote:
> Fix a user API regression introduced with commit f76edd8f7ce0 ("tty:
> cyclades, remove this orphan"), which removed a part of the API and
> caused compilation errors for user programs using said part, such as
> GCC 9 in its libsanitizer component[1]:
>
> .../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:160:10: fatal error: linux/cyclades.h: No such file or directory
> 160 | #include <linux/cyclades.h>
> | ^~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[4]: *** [Makefile:664: sanitizer_platform_limits_posix.lo] Error 1
>
> As the absolute minimum required bring `struct cyclades_monitor' and
> ioctl numbers back then so as to make the library build again. Add a
> preprocessor warning as to the obsolescence of the features provided.
>
> References:
>
> [1] GCC PR sanitizer/100379, "cyclades.h is removed from linux kernel
> header files", <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100379>
>
> Signed-off-by: Maciej W. Rozycki <macro@embecosm.com>
> Fixes: f76edd8f7ce0 ("tty: cyclades, remove this orphan")
> Cc: stable@vger.kernel.org # v5.13+
> ---
> Changes from v2:
>
> - Add #warning directives.
Thanks, that looks good, now queued up.
greg k-h
next prev parent reply other threads:[~2022-01-26 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:22 [PATCH v3] tty: Partially revert the removal of the Cyclades public API Maciej W. Rozycki
2022-01-26 13:43 ` Christoph Hellwig
2022-01-26 13:50 ` Greg Kroah-Hartman [this message]
2022-01-26 14:07 ` kernel test robot
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=YfFRlbKw4cV+ISfk@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@embecosm.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).