All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: mingo@elte.hu, hpa@zytor.com, tglx@linutronix.de,
	andi@firstfloor.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.orgAndi Kleen <andi@firstfloor.org>
Subject: Re: [patch 1/5] x86: ACPI - add checking for NULL early param
Date: Tue, 22 Jul 2008 02:53:32 -0700	[thread overview]
Message-ID: <20080722025332.afddd49b.akpm@linux-foundation.org> (raw)
In-Reply-To: <486f61a9.2135440a.0d16.ffffbd7f@mx.google.com>

On Sat, 05 Jul 2008 15:53:35 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
> ---
> 
> Index: linux-2.6.git/drivers/acpi/tables.c
> ====================================================================
> --- linux-2.6.git.orig/drivers/acpi/tables.c	2008-01-21 23:14:47.000000000 +0300
> +++ linux-2.6.git/drivers/acpi/tables.c	2008-07-05 12:24:16.000000000 +0400
> @@ -300,6 +300,8 @@ int __init acpi_table_init(void)
>  
>  static int __init acpi_parse_apic_instance(char *str)
>  {
> +	if (!str)
> +		return -EINVAL;
>  
>  	acpi_apic_instance = simple_strtoul(str, NULL, 0);
>  

Could you please explain this patch?

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: mingo@elte.hu, hpa@zytor.com, tglx@linutronix.de,
	andi@firstfloor.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [patch 1/5] x86: ACPI - add checking for NULL early param
Date: Tue, 22 Jul 2008 02:53:32 -0700	[thread overview]
Message-ID: <20080722025332.afddd49b.akpm@linux-foundation.org> (raw)
In-Reply-To: <486f61a9.2135440a.0d16.ffffbd7f@mx.google.com>

On Sat, 05 Jul 2008 15:53:35 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
> ---
> 
> Index: linux-2.6.git/drivers/acpi/tables.c
> ====================================================================
> --- linux-2.6.git.orig/drivers/acpi/tables.c	2008-01-21 23:14:47.000000000 +0300
> +++ linux-2.6.git/drivers/acpi/tables.c	2008-07-05 12:24:16.000000000 +0400
> @@ -300,6 +300,8 @@ int __init acpi_table_init(void)
>  
>  static int __init acpi_parse_apic_instance(char *str)
>  {
> +	if (!str)
> +		return -EINVAL;
>  
>  	acpi_apic_instance = simple_strtoul(str, NULL, 0);
>  

Could you please explain this patch?

  reply	other threads:[~2008-07-22  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080705115334.892720771@gmail.com>
2008-07-05 11:53 ` [patch 1/5] x86: ACPI - add checking for NULL early param Cyrill Gorcunov
2008-07-22  9:53   ` Andrew Morton [this message]
2008-07-22  9:53     ` Andrew Morton
2008-07-22 10:19     ` Cyrill Gorcunov
2008-07-05 11:53 ` [patch 2/5] x86: idle process " Cyrill Gorcunov
2008-07-05 11:53 ` [patch 3/5] x86: io delay " Cyrill Gorcunov
2008-07-05 11:53 ` [patch 4/5] x86: smpboot maxcpus " Cyrill Gorcunov
2008-07-05 11:53 ` [patch 5/5] x86: e820 memmap " Cyrill Gorcunov

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=20080722025332.afddd49b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.orgAndi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.