From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] kpartx: support device names with spaces
Date: Wed, 20 Jan 2016 11:57:54 -0200 [thread overview]
Message-ID: <569F9262.90305@linux.vnet.ibm.com> (raw)
In-Reply-To: <CABr-GncCqpkdNcw4ShHxigHKqB+feesNDoUHHfkR_1vkJQ5BmA@mail.gmail.com>
Hi Christophe,
On 01/20/2016 05:15 AM, Christophe Varoqui wrote:
> shouldn't you either define the MAJOR and MINOR macros, or include the
> appropriate kernel header ? As is the build emits :
Oops. Apologies. I incorrectly submitted a backport of the patch.
I just submitted V2 w/ the right patch, which uses major()/minor()
as elsewhere in the file. The build and test-case are OK. Thanks!
Regards,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
prev parent reply other threads:[~2016-01-20 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 18:31 [PATCH] kpartx: support device names with spaces Mauricio Faria de Oliveira
2016-01-20 7:15 ` Christophe Varoqui
2016-01-20 13:57 ` Mauricio Faria de Oliveira [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=569F9262.90305@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox