All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Gilad Broner <gbroner@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
	linux-scsi-owner@vger.kernel.org, subhashj@codeaurora.org,
	ygardi@codeaurora.org, draviv@codeaurora.org,
	Lee Susman <lsusman@codeaurora.org>,
	Raviv Shvili <rshvili@codeaurora.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>
Subject: Re: [PATCH v7 2/3] scsi: ufs: add debugfs for ufs
Date: Fri, 27 Mar 2015 14:05:06 +0100	[thread overview]
Message-ID: <1427461506.2250.19.camel@HansenPartnership.com> (raw)
In-Reply-To: <1426175700-23152-3-git-send-email-gbroner@codeaurora.org>

On Thu, 2015-03-12 at 17:54 +0200, Gilad Broner wrote:
> From: Lee Susman <lsusman@codeaurora.org>
> 
> Adding debugfs capability for ufshcd.

This patch fails to build as a module because you aren't building
corectly:

ERROR: "ufsdbg_add_debugfs" [drivers/scsi/ufs/ufshcd.ko] undefined!
ERROR: "ufsdbg_remove_debugfs" [drivers/scsi/ufs/ufshcd.ko] undefined!
scripts/Makefile.modpost:90: recipe for target '__modpost' failed

CONFIG_DEBUG_FS is y in my system not m, so your Makefile fails.

James

  parent reply	other threads:[~2015-03-27 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 15:54 [PATCH v7 0/3] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-03-12 15:54 ` [PATCH v7 1/3] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-03-12 15:54   ` Gilad Broner
2015-03-18 13:17   ` Dov Levenglick
2015-03-12 15:54 ` [PATCH v7 2/3] scsi: ufs: add debugfs for ufs Gilad Broner
2015-03-18 13:19   ` Dov Levenglick
2015-03-18 13:19     ` Dov Levenglick
2015-03-27 13:05   ` James Bottomley [this message]
2015-03-12 15:55 ` [PATCH v7 3/3] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-03-12 16:13   ` Steven Rostedt
2015-03-18 13:20   ` Dov Levenglick
2015-03-18 13:20     ` Dov Levenglick

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=1427461506.2250.19.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=draviv@codeaurora.org \
    --cc=gbroner@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsusman@codeaurora.org \
    --cc=rshvili@codeaurora.org \
    --cc=santoshsy@gmail.com \
    --cc=subhashj@codeaurora.org \
    --cc=vinholikatti@gmail.com \
    --cc=ygardi@codeaurora.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 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.