From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V4] nvme: new package
Date: Sat, 16 Jan 2016 14:13:30 +0100 [thread overview]
Message-ID: <20160116141330.3af0deea@free-electrons.com> (raw)
In-Reply-To: <20160114110931.25590.46942.stgit@localhost.localdomain>
Dear Mamatha Inamdar,
On Thu, 14 Jan 2016 16:42:40 +0530, Mamatha Inamdar wrote:
> Add support for building NVME utility - a utility for interacting with
> standard NVM Express (optimized PCI Express SSD interface) devices.
>
> Signed-off-by: Mamatha Inamdar <mamatha4@linux.vnet.ibm.com>
> ---
> package/Config.in | 1 +
> package/nvme/Config.in | 6 ++++++
> package/nvme/nvme.hash | 2 ++
> package/nvme/nvme.mk | 23 +++++++++++++++++++++++
> 4 files changed, 32 insertions(+)
> create mode 100755 package/nvme/Config.in
> create mode 100644 package/nvme/nvme.hash
> create mode 100755 package/nvme/nvme.mk
Your patch does not apply:
Applying patch #567318 using 'git am -s -3'
Description: [V4] nvme: new package
Applying: nvme: new package
fatal: corrupt patch at line 72
error: could not build fake ancestor
Patch failed at 0001 nvme: new package
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Please make sure to use "git send-email" to submit your patch.
Also, you haven't included a patch that removes -Werror. Are you sure
the package builds properly? It wasn't building properly for me without
a patch removing -Werror.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-16 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 11:12 [Buildroot] [PATCH V4] nvme: new package Mamatha Inamdar
2016-01-16 13:13 ` Thomas Petazzoni [this message]
2016-01-18 7:27 ` 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=20160116141330.3af0deea@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.