All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Narsimhulu Musini (nmusini)" <nmusini@cisco.com>
To: Boaz Harrosh <boaz@plexistor.com>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"hare@suse.de" <hare@suse.de>
Cc: "Sesidhar Baddela (sebaddel)" <sebaddel@cisco.com>
Subject: Re: [PATCH v6 9/9] snic:Add Makefile, patch Kconfig, MAINTAINERS
Date: Thu, 28 May 2015 09:49:08 +0000	[thread overview]
Message-ID: <D18CE1AF.26822%nmusini@cisco.com> (raw)
In-Reply-To: <5565A997.9070604@plexistor.com>

Hi Boaz, 

    Sure, I will incorporate the comments and suggestions in next patch
submittal.

Thanks
Narsimhulu

On 27/05/15 4:55 pm, "Boaz Harrosh" <boaz@plexistor.com> wrote:

>On 05/27/2015 01:02 PM, Narsimhulu Musini (nmusini) wrote:
><>
>>>> +ifeq ($(CONFIG_SCSI_SNIC_DEBUG_FS), y)
>>>> +ccflags-y += -DSNIC_DEBUG_FS
>>>
>>> Why do you need an extra define here just use
>>> CONFIG_SCSI_SNIC_DEBUG_FS in source code directly
>> Agree, I just want to use a shorter macro in the source.
>
>Don't do this. It is a convention that if a programmer
>sees a CONFIG_XXX he knows that this is settable by a
>Kconfig. By making it shorter the programmer will think that
>this is dead code because it is not set anywhere.
>
>>>
>>>> +snic-y += snic_debugfs.o \
>>>> +		snic_trc.o
>>>> +endif
>>>>
>>>
>>> snic-$(CONFIG_SCSI_SNIC_DEBUG_FS) += snic_debugfs.o
>> If CONFIG_SCSI_SNIC_DEBUGFS is not set, then it leaves a build variable
>> ³snic-" in build system. ifeq() avoids such thing.
>
>That is fine. This is done all over the Kernel Makefile.
>There are two tons of these "do nothing make variables"
>
>It the way we do it in the Kernel. (I actually like it)
>
>>>
>>> You do not the  ifeq () thing at all
>>>
>>> Cheers
>>> Boaz
>>>
>> Thanks
>> simha
>>>
>> 
>


  reply	other threads:[~2015-05-28  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  7:19 [PATCH v6 0/9] snic:initial submission of snic driver for Cisco SCSI HBA Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 1/9] snic: snic module infrastructure Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 2/9] snic:Add interrupt, resource firmware interfaces Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 3/9] snic:Add meta request, handling of meta requests Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 4/9] snic:Add snic target discovery Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 5/9] snic:add SCSI handling, AEN, and fwreset handling Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 6/9] snic:Add low level queuing interfaces Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 7/9] snic:Add sysfs entries to list stats and trace data Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 8/9] snic:Add event tracing to capture IO events Narsimhulu Musini
2015-05-27  7:19 ` [PATCH v6 9/9] snic:Add Makefile, patch Kconfig, MAINTAINERS Narsimhulu Musini
2015-05-27  9:17   ` Boaz Harrosh
2015-05-27 10:02     ` Narsimhulu Musini (nmusini)
2015-05-27 11:25       ` Boaz Harrosh
2015-05-28  9:49         ` Narsimhulu Musini (nmusini) [this message]
2015-05-28 13:42           ` Johannes Thumshirn
2015-05-28 17:59             ` Narsimhulu Musini (nmusini)
2015-05-28 13:55   ` James Bottomley
2015-05-28 18:01     ` Narsimhulu Musini (nmusini)

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=D18CE1AF.26822%nmusini@cisco.com \
    --to=nmusini@cisco.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=boaz@plexistor.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sebaddel@cisco.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.