Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mamatha Inamdar <mamatha4@linux.vnet.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V3] Adding support for NVME utils
Date: Wed, 13 Jan 2016 16:35:22 +0530	[thread overview]
Message-ID: <56962F72.60007@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160112212700.01ce8859@free-electrons.com>


Hi Thomas,

Thanks for reviewing the patch.

I have worked on all your comments,facing some issue while building nvme.
Will check and send new version of patch soon.


On 01/13/2016 01:57 AM, Thomas Petazzoni wrote:
> Dear Mamatha,
>
> Thanks for your contribution!
>
> On Tue, 12 Jan 2016 11:22:06 +0530, Mamatha wrote:
>> Add support for building NVME utility - a utility for interacting with
>> standard NVM Express (optimized PCI Express SSD interface) devices.
> For all patches on packages, we prefer to have the title of the commit
> comply with the following format:
>
> 	<package>: <description>
>
> So in your case, it should be:
>
> 	nvme: new package
>
>> Signed-off-by: Mamatha <mamatha4@linux.vnet.ibm.com>
> Sorry if I'm not familiar with naming practices in your part of the
> world, but we require a full name (i.e first name + last name). Is
> Mamatha your full name ?
>
>> ---
>>   package/Config.in      |    1 +
>>   package/nvme/Config.in |    6 ++++++
>>   package/nvme/nvme.mk   |   23 +++++++++++++++++++++++
>>   3 files changed, 30 insertions(+)
>>   create mode 100755 package/nvme/Config.in
>>   create mode 100755 package/nvme/nvme.mk
>>
>> diff --git a/package/Config.in b/package/Config.in
>> index e0c2e2a..014debd 100644
>> --- a/package/Config.in
>> +++ b/package/Config.in
>> @@ -1399,6 +1399,7 @@ endif
>>   	source "package/openvmtools/Config.in"
>>   	source "package/polkit/Config.in"
>>   	source "package/powerpc-utils/Config.in"
>> +	source "package/nvme/Config.in"
> You should respect alphabetic ordering here when including
> nvme/Config.in. Also I believe this package better belongs to the
> "Hardware handling" menu rather than "System tools".
>
>>   if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
>>   	source "package/procps-ng/Config.in"
>>   	source "package/psmisc/Config.in"
>> diff --git a/package/nvme/Config.in b/package/nvme/Config.in
>> new file mode 100755
>> index 0000000..a3c8ada
>> --- /dev/null
>> +++ b/package/nvme/Config.in
>> @@ -0,0 +1,6 @@
>> +config BR2_PACKAGE_NVME
>> +	bool "nvme"
>> +	help
>> +	  System utilities for standard NVME Express devices
>> +
>> +	  https://github.com/linux-nvme/nvme-cli
>> diff --git a/package/nvme/nvme.mk b/package/nvme/nvme.mk
>> new file mode 100755
>> index 0000000..43bec67
>> --- /dev/null
>> +++ b/package/nvme/nvme.mk
>> @@ -0,0 +1,23 @@
>> +################################################################################
>> +#
>> +# nvme
>> +#
>> +################################################################################
>> +
>> +NVME_VERSION = 0.1
>> +NVME_SITE = https://github.com/linux-nvme/nvme-cli.git
>> +NVME_SITE_METHOD = git
> You should use the github helper. See also
> https://buildroot.org/downloads/manual/manual.html#github-download-url.
>
>> +NVME_LICENSE = GPLv2
> The license is GPLv2+
>
>> +NVME_LICENSE_FILES = COPYING
>> +
>> +define NVME_BUILD_CMDS
>> +	$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) \
>> +		INCLUDEDIR="-I." all
> Why do you explicitly specify "all" here ? It is going to build the
> documentation, while if you leave it out, it will only build the first
> target, which is named "default" in nvme's Makefile, and it will only
> build the nvme binary.
>
> Also, when calling $(MAKE), please pass $(TARGET_MAKE_ENV) in the
> environment:
>
> 	$(TARGET_MAKE_ENV) $(MAKE) ...
>
>> +endef
>> +
>> +define NVME_INSTALL_TARGET_CMDS
>> +	$(INSTALL) -D -m 0755 $(@D)/nvme $(TARGET_DIR)/sbin/nvme
> Why you don't you use the install-bin target ? Like this:
>
> 	$(TARGET_MAKE_ENV) $(MAKE) -C (@D) DESTDIR=$(TARGET_DIR) install-bin
>
> Also, could you add a hash file, as explained in
> https://buildroot.org/downloads/manual/manual.html#adding-packages-hash ?
>
> Could you rework your patch to take into account those comments and
> send an updated version ?
>
> Thanks!
>
> Thomas

  reply	other threads:[~2016-01-13 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  5:52 [Buildroot] [PATCH V3] Adding support for NVME utils Mamatha
2016-01-12 20:27 ` Thomas Petazzoni
2016-01-13 11:05   ` Mamatha Inamdar [this message]
2016-01-13 11:38     ` Thomas Petazzoni
     [not found]       ` <569720FF.6020807@linux.vnet.ibm.com>
2016-01-14  9:04         ` Thomas Petazzoni
2016-01-14 11:15           ` Mamatha Inamdar

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=56962F72.60007@linux.vnet.ibm.com \
    --to=mamatha4@linux.vnet.ibm.com \
    --cc=buildroot@busybox.net \
    /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