linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Rashika Kheria <rashika.kheria@gmail.com>
Cc: linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	sfi-devel@simplefirmware.org
Subject: Re: [PATCH 1/2] drivers: sfi: Include appropriate headers in sfi_acpi.c
Date: Tue, 17 Dec 2013 08:35:02 -0800	[thread overview]
Message-ID: <20131217163502.GC737@leaf> (raw)
In-Reply-To: <c351cee2521c4728d60810eb0212e8f307c79ac6.1387283325.git.rashika.kheria@gmail.com>

On Tue, Dec 17, 2013 at 06:02:14PM +0530, Rashika Kheria wrote:
> Include header file include/linux/sfi_acpi.h in sfi_acpi.c because
> function sfi_acpi_table_parse() has its prototype declaration in
> include/linux/sfi_acpi.h. Also, include include/linux/acpi.h because it
> contains declarations necessary for include/linux/sfi_acpi.h.
> 
> This eliminates the following warning in sfi_acpi.c:
> drivers/sfi/sfi_acpi.c:154:5: warning: no previous prototype for ‘sfi_acpi_table_parse’ [-Wmissing-prototypes]
> 
> Signed-off-by: Rashika Kheria <rashika.kheria@gmail.com>

Reviewed-by: Josh Triplett <josh@joshtriplett.org>

>  drivers/sfi/sfi_acpi.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/sfi/sfi_acpi.c b/drivers/sfi/sfi_acpi.c
> index f5b4ca5..95023f9 100644
> --- a/drivers/sfi/sfi_acpi.c
> +++ b/drivers/sfi/sfi_acpi.c
> @@ -60,6 +60,8 @@
>  #define pr_fmt(fmt) KMSG_COMPONENT ": " fmt
>  
>  #include <linux/kernel.h>
> +#include <linux/acpi.h>
> +#include <linux/sfi_acpi.h>
>  #include <acpi/acpi.h>
>  
>  #include <linux/sfi.h>
> -- 
> 1.7.9.5
> 

      parent reply	other threads:[~2013-12-17 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 12:32 [PATCH 1/2] drivers: sfi: Include appropriate headers in sfi_acpi.c Rashika Kheria
2013-12-17 12:34 ` [PATCH 2/2] drivers: sfi: Mark functions as static in sfi_core.c Rashika Kheria
2013-12-17 16:35   ` Josh Triplett
2013-12-17 16:35 ` Josh Triplett [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=20131217163502.GC737@leaf \
    --to=josh@joshtriplett.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rashika.kheria@gmail.com \
    --cc=sfi-devel@simplefirmware.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).