All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <chris@printf.net>
To: Avi Shchislowski <Avi.Shchislowski@sandisk.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Alex Lemberg <Alex.Lemberg@sandisk.com>,
	Yaniv Agman <Yaniv.Agman@sandisk.com>
Subject: Re: [PATCH 1/1 v2] mmc_utils: add ffu support
Date: Fri, 26 Feb 2016 14:50:59 +0000	[thread overview]
Message-ID: <86vb5bcyp8.fsf@void.printf.net> (raw)
In-Reply-To: <86ziuncyz2.fsf@void.printf.net> (Chris Ball's message of "Fri, 26 Feb 2016 14:45:05 +0000")

Hi,

On Fri, Feb 26 2016, Chris Ball wrote:
> Thanks for resending.  I'm getting some compile errors, any ideas?
>
> mmc_cmds.c: In function ‘do_ffu’:
> mmc_cmds.c:2076:31: error: invalid application of ‘sizeof’ to incomplete type ‘struct mmc_ioc_multi_cmd’
>   multi_cmd = calloc(1, sizeof(struct mmc_ioc_multi_cmd) +
>                                ^
>
> mmc_cmds.c:2126:11: error: dereferencing pointer to incomplete type ‘struct mmc_ioc_multi_cmd’
>   multi_cmd->num_of_cmds = 3;
>            ^
>
> mmc_cmds.c:2162:23: error: ‘MMC_IOC_MULTI_CMD’ undeclared (first use in this function)
>    ret = ioctl(dev_fd, MMC_IOC_MULTI_CMD, multi_cmd);
>                        ^

Oh, I bet it's because we include <linux/mmc/ioctl.h>, and now that
needs to be coming from Linux 4.4+ to include the new ioctl.

Putting a compile-dependency on Linux 4.4+ seems very tough, though.
mmc-utils is built on many distributions (e.g. Debian repository build
machines, ChromeOS build machines) where it may not be possible to
upgrade the system kernel headers.

Please could we get some #ifdefs on MMC_IOC_MULTI_CMD around the
FFU code?

Thanks!

- Chris.
-- 
Chris Ball   <http://printf.net/>

      reply	other threads:[~2016-02-26 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 11:27 [PATCH 1/1 v2] mmc_utils: add ffu support Avi Shchislowski
2016-02-26 14:45 ` Chris Ball
2016-02-26 14:50   ` Chris Ball [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=86vb5bcyp8.fsf@void.printf.net \
    --to=chris@printf.net \
    --cc=Alex.Lemberg@sandisk.com \
    --cc=Avi.Shchislowski@sandisk.com \
    --cc=Yaniv.Agman@sandisk.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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.