linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tty: vc_screen: make vc_class constant
Date: Mon, 9 Oct 2023 07:28:03 +0200	[thread overview]
Message-ID: <68c4b7ee-345f-42e4-a69e-700384b711ad@kernel.org> (raw)
In-Reply-To: <2023100549-sixth-anger-ac34@gregkh>

On 05. 10. 23, 15:33, Greg Kroah-Hartman wrote:
> Now that the driver core allows for struct class to be in read-only
> memory, making all 'class' structures to be declared at build time
> placing them into read-only memory, instead of having to be dynamically
> allocated at load time.
> 
> Cc: Jiri Slaby <jirislaby@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>   drivers/tty/vt/vc_screen.c | 28 ++++++++++++++--------------
>   1 file changed, 14 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/tty/vt/vc_screen.c b/drivers/tty/vt/vc_screen.c
> index 829c4be66f3b..b16ea517bb17 100644
> --- a/drivers/tty/vt/vc_screen.c
> +++ b/drivers/tty/vt/vc_screen.c
...
> @@ -811,11 +810,12 @@ int __init vcs_init(void)
>   
>   	if (register_chrdev(VCS_MAJOR, "vcs", &vcs_fops))
>   		panic("unable to get major %d for vcs device", VCS_MAJOR);
> -	vc_class = class_create("vc");
> +	if (class_register(&vc_class))
> +		panic("unable to create vc_class");

FWIW it's no longer "create". Now it's "register".

Anyway, for the sake of archives:
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>

regards,
-- 
js
suse labs


      reply	other threads:[~2023-10-09  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 13:33 [PATCH 1/2] tty: vt: make vtconsole_class constant Greg Kroah-Hartman
2023-10-05 13:33 ` [PATCH 2/2] tty: vc_screen: make vc_class constant Greg Kroah-Hartman
2023-10-09  5:28   ` 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=68c4b7ee-345f-42e4-a69e-700384b711ad@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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).