All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
	David Sterba <dsterba@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Fix implicit inclusion of linux/uio.h
Date: Tue, 24 Mar 2015 14:43:01 +0100	[thread overview]
Message-ID: <20150324134301.GT20767@twin.jikos.cz> (raw)
In-Reply-To: <1427042775-8258-1-git-send-email-broonie@kernel.org>

On Sun, Mar 22, 2015 at 04:46:15PM +0000, Mark Brown wrote:
> The btrfs inode.c relies on implicit inclusion of linux/uio.h for
> definitions of struct iov_iter and iov_iter_alignment() which breaks the
> current ARM allmodconfig build where that implicit inclusion does not
> happen.  Add an explicit include to fix that.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>

Acked-by: David Sterba <dsterba@suse.cz>

      reply	other threads:[~2015-03-24 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 16:46 [PATCH] btrfs: Fix implicit inclusion of linux/uio.h Mark Brown
2015-03-24 13:43 ` David Sterba [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=20150324134301.GT20767@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=broonie@kernel.org \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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.