From: Jiri Slaby <jirislaby@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] tty: hvc: remove HVC_IUCV_MAGIC
Date: Fri, 16 Sep 2022 08:52:19 +0200 [thread overview]
Message-ID: <28f755d8-822c-99ce-831b-d9f68ae53173@kernel.org> (raw)
In-Reply-To: <8c8a2c9dfc1bfbe6ef3f3237368e483865fc1c29.1663288066.git.nabijaczleweli@nabijaczleweli.xyz>
On 16. 09. 22, 3:55, наб wrote:
> According to Greg, in the context of magic numbers as defined in
> magic-number.rst, "the tty layer should not need this and I'll gladly
> take patches"
>
> This stretches that definition slightly, since it multiplexes it with
> the terminal number as a constant offset, but is equivalent
>
> Ref: https://lore.kernel.org/linux-doc/YyMlovoskUcHLEb7@kroah.com/
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Acked-by: Jiri Slaby <jirislaby@kernel.org>
> ---
> drivers/tty/hvc/hvc_iucv.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/tty/hvc/hvc_iucv.c b/drivers/tty/hvc/hvc_iucv.c
> index 32366caca662..7d49a872de48 100644
> --- a/drivers/tty/hvc/hvc_iucv.c
> +++ b/drivers/tty/hvc/hvc_iucv.c
> @@ -29,7 +29,6 @@
>
>
> /* General device driver settings */
> -#define HVC_IUCV_MAGIC 0xc9e4c3e5
> #define MAX_HVC_IUCV_LINES HVC_ALLOC_TTY_ADAPTERS
> #define MEMPOOL_MIN_NR (PAGE_SIZE / sizeof(struct iucv_tty_buffer)/4)
>
> @@ -131,9 +130,9 @@ static struct iucv_handler hvc_iucv_handler = {
> */
> static struct hvc_iucv_private *hvc_iucv_get_private(uint32_t num)
> {
> - if ((num < HVC_IUCV_MAGIC) || (num - HVC_IUCV_MAGIC > hvc_iucv_devices))
> + if (num > hvc_iucv_devices)
> return NULL;
> - return hvc_iucv_table[num - HVC_IUCV_MAGIC];
> + return hvc_iucv_table[num];
> }
>
> /**
> @@ -1072,8 +1071,8 @@ static int __init hvc_iucv_alloc(int id, unsigned int is_console)
> priv->is_console = is_console;
>
> /* allocate hvc device */
> - priv->hvc = hvc_alloc(HVC_IUCV_MAGIC + id, /* PAGE_SIZE */
> - HVC_IUCV_MAGIC + id, &hvc_iucv_ops, 256);
> + priv->hvc = hvc_alloc(id, /* PAGE_SIZE */
> + id, &hvc_iucv_ops, 256);
> if (IS_ERR(priv->hvc)) {
> rc = PTR_ERR(priv->hvc);
> goto out_error_hvc;
> @@ -1371,7 +1370,7 @@ static int __init hvc_iucv_init(void)
>
> /* register the first terminal device as console
> * (must be done before allocating hvc terminal devices) */
> - rc = hvc_instantiate(HVC_IUCV_MAGIC, IUCV_HVC_CON_IDX, &hvc_iucv_ops);
> + rc = hvc_instantiate(0, IUCV_HVC_CON_IDX, &hvc_iucv_ops);
> if (rc) {
> pr_err("Registering HVC terminal device as "
> "Linux console failed\n");
--
js
suse labs
prev parent reply other threads:[~2022-09-16 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <476d024cd6b04160a5de381ea2b9856b60088cbd.1663288066.git.nabijaczleweli@nabijaczleweli.xyz>
2022-09-16 1:55 ` [PATCH 5/5] tty: hvc: remove HVC_IUCV_MAGIC наб
2022-09-16 6:52 ` Jiri Slaby [this message]
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=28f755d8-822c-99ce-831b-d9f68ae53173@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=rdunlap@infradead.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).