mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] tty: Revert the removal of the Cyclades public API
Date: Sat, 15 Jan 2022 09:17:19 +0100	[thread overview]
Message-ID: <YeKDD6imTh1Y6GuN@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2201141832330.11348@tpp.orcam.me.uk>

On Fri, Jan 14, 2022 at 08:54:05PM +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

So all we need is an empty header file?  Why bring back all of the
unused structures?

> Any part of the public API is a contract between the kernel and the 
> userland and therefore once there it must not be removed even if its 
> implementation side has gone and any relevant calls will now fail 
> unconditionally.

Does this code actually use any of these structures?

> Revert the part of the commit referred then that affects the user API, 
> bringing the most recent version of <linux/cyclades.h> back verbatim 
> modulo the removal of trailing whitespace which used to be there, and 
> updating <linux/major.h> accordingly.

Why major.h?  What uses that?  No userspace code should care about that.

Also, your text here is full of trailing whitespace, so I couldn't take
this commit as-is anyway :(

thanks,

greg k-h

  reply	other threads:[~2022-01-15  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 20:54 Maciej W. Rozycki
2022-01-15  8:17 ` Greg Kroah-Hartman [this message]
2022-01-17 17:55   ` Maciej W. Rozycki
2022-01-17 18:13     ` Greg Kroah-Hartman
2022-01-23 13:32       ` Maciej W. Rozycki

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=YeKDD6imTh1Y6GuN@kroah.com \
    --to=gregkh@linuxfoundation.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

all inboxes | Powered by JetHome®