From: Jiri Slaby <jslaby@suse.cz>
To: Wang YanQing <udknight@gmail.com>,
gregkh@linuxfoundation.org, airlied@redhat.com,
akpm@linux-foundation.org, kilobyte@angband.pl,
peter@hurleysoftware.com, rosslagerwall@gmail.com, tiwai@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3]vt: use vc_allocate in con_init
Date: Mon, 06 Jan 2014 09:56:06 +0100 [thread overview]
Message-ID: <52CA6FA6.2090105@suse.cz> (raw)
In-Reply-To: <20140102074812.GA4713@udknight>
On 01/02/2014 08:48 AM, Wang YanQing wrote:
> After a5f4f52e82114e85aa1a066bd1a450acc19a464d
> ("vt: use kzalloc() instead of the bootmem allocator"),
> con_init began to use kzalloc to initialize vc_data,
> this patch convert con_init to use vc_allocate.
>
> The benefit we get:
> 1: reduce code duplication
> 2: vc_allocate is more robust
> 3: use kmalloc instead of kzalloc for vc_screenbuf
>
> Signed-off-by: Wang YanQing <udknight@gmail.com>
> ---
> Changes v2-v3:
> 1: fix warnings reported by checkpatch.pl
> 2: clarify changelog
>
> drivers/tty/vt/vt.c | 28 ++++++++++++++--------------
> drivers/tty/vt/vt_ioctl.c | 8 ++++----
> include/linux/vt_kern.h | 2 +-
> 3 files changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
> index 15aaa01..720a8f9 100644
> --- a/drivers/tty/vt/vt.c
> +++ b/drivers/tty/vt/vt.c
> @@ -748,7 +748,8 @@ static void visual_init(struct vc_data *vc, int num, int init)
> vc->vc_screenbuf_size = vc->vc_rows * vc->vc_size_row;
> }
>
> -int vc_allocate(unsigned int currcons) /* return 0 on success */
> +/* return 0 on success */
> +int vc_allocate(unsigned int currcons, int early)
Could you use
bool/true/false
instead of
int/1/0
please?
--
js
suse labs
prev parent reply other threads:[~2014-01-06 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 7:48 [PATCH v3]vt: use vc_allocate in con_init Wang YanQing
2014-01-06 8:56 ` 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=52CA6FA6.2090105@suse.cz \
--to=jslaby@suse.cz \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=rosslagerwall@gmail.com \
--cc=tiwai@suse.de \
--cc=udknight@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.