linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Sudeep Dutt <sudeep.dutt@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: mic: fix memory leak
Date: Tue, 13 Oct 2015 15:53:37 +0530	[thread overview]
Message-ID: <20151013102337.GA5825@sudip-pc> (raw)
In-Reply-To: <201510131717.lfbA1KxP%fengguang.wu@intel.com>

On Tue, Oct 13, 2015 at 05:50:12PM +0800, kbuild test robot wrote:
> Hi Sudip,
> 
> [auto build test WARNING on char-misc/char-misc-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
> 
> url:    https://github.com/0day-ci/linux/commits/Sudip-Mukherjee/misc-mic-fix-memory-leak/20151013-171026
> reproduce:
>         # apt-get install sparse
>         make ARCH=x86_64 allmodconfig
>         make C=1 CF=-D__CHECK_ENDIAN__
> 
> 
> sparse warnings: (new ones prefixed by >>)
> 
> >> drivers/misc/mic/scif/scif_nodeqp.c:439:6: sparse: symbol 'scif_deinit_p2p_info' was not declared. Should it be static?
> 
> Please review and possibly fold the followup patch.

Thanks. I have sent a v2.

regards
sudip

  reply	other threads:[~2015-10-13 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  9:08 [PATCH] misc: mic: fix memory leak Sudip Mukherjee
2015-10-13  9:50 ` kbuild test robot
2015-10-13 10:23   ` Sudip Mukherjee [this message]
2015-10-13  9:50 ` [RFC PATCH] misc: mic: scif_deinit_p2p_info() can be static kbuild test robot
2015-10-13 16:34 ` [PATCH] misc: mic: fix memory leak Sudeep Dutt
2015-10-13 17:16   ` Sudip Mukherjee
2015-10-13 17:25     ` Sudeep Dutt

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=20151013102337.GA5825@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=sudeep.dutt@intel.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 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).