From: Mamatha Inamdar <mamatha4@linux.vnet.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V8] package/nvme: new package
Date: Sun, 14 Feb 2016 16:27:34 +0530 [thread overview]
Message-ID: <56C05D9E.8050701@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160212144408.7ac40a76@free-electrons.com>
Hi Thomas,
Yes nvme V0.3 will solve all compilation issues,
updated your comments and sending
new version of the patch.
On 02/12/2016 07:14 PM, Thomas Petazzoni wrote:
> Dear Mamatha Inamdar,
>
> On Fri, 12 Feb 2016 16:58:30 +0530, Mamatha Inamdar wrote:
>> Add support for building NVME utility - a utility for interacting with
>> standard NVM Express (optimized PCI Express SSD interface) devices.
>>
>> Changes in V8:
>> /package/nvme/Makefile patch not added:
>> CFLAGS changes in nvme/Makefile is not required because I did not see
>> any compilation errors after adding "depend on BR2_powerpc64 || BR2_powerpc64le"
>> line in nvme/Config.in for this I have to enable 64-bit arch in config file.
>> after enabling 64-bit arch I do not see any compilation errors in nvme code.
> I know Arnout asked you to add the PowerPC64 dependency, but I
> disagree. I don't see anything in this tool that is PowerPC64 specific.
>
> Moreover, the -m64 that was causing problem has been removed upstream,
> as part of commit
> https://github.com/linux-nvme/nvme-cli/commit/3686759d04825d35fb8d9667c3d4a14e880f5b4d.
>
> In fact, I believe this commit from upstream probably solves a lot of
> cross-compilation problems, so please use v0.3 instead of v0.2, since
> v0.3 includes this commit.
>
>> diff --git a/package/nvme/Config.in b/package/nvme/Config.in
>> new file mode 100644
>> index 0000000..878bed3
>> --- /dev/null
>> +++ b/package/nvme/Config.in
>> @@ -0,0 +1,10 @@
>> +config BR2_PACKAGE_NVME
>> + bool "nvme"
>> + depends on BR2_powerpc64 || BR2_powerpc64le
> Remove this dependency.
>
>> +
> And this empty line/
>
>> + help
>> + Add support for building NVME utility - a utility
> "Add support" is not a proper wording to describe a package. Instead,
> you should just have something like:
>
> NVME utility, a utility for interacting with standard NVM
> Express ...
>
>> + for interacting with standard NVM Express
>> + (optimized PCI Express SSD interface) devices.
>> +
>> + https://github.com/linux-nvme/nvme-cli
> Thanks,
>
> Thomas
prev parent reply other threads:[~2016-02-14 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 11:28 [Buildroot] [PATCH V8] package/nvme: new package Mamatha Inamdar
2016-02-12 13:44 ` Thomas Petazzoni
2016-02-14 10:57 ` Mamatha Inamdar [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=56C05D9E.8050701@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