All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 1/2] xfs_io: include headers for preadv/pwritev
Date: Thu, 11 Oct 2012 15:40:47 -0500	[thread overview]
Message-ID: <50772ECF.5050308@sgi.com> (raw)
In-Reply-To: <50749EE2.6070408@redhat.com>

On 10/09/12 17:02, Eric Sandeen wrote:
> We need to include uio.h to avoid:
>
>      [CC]     pread.o
> pread.c: In function ‘do_pread’:
> pread.c:198: warning: implicit declaration of function ‘preadv’
>      [CC]     pwrite.o
> pwrite.c: In function ‘do_pwrite’:
> pwrite.c:85: warning: implicit declaration of function ‘pwritev’
>
> Signed-off-by: Eric Sandeen<sandeen@redhat.com>
> ---

I had a problem downloading this patch. It was small, so I recreated.
I hope it was correct.

Committed to git://oss.sgi.com/xfs/cmds/xfsprogs.git, master branch.

--Mark.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2012-10-11 20:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 22:02 [PATCH 1/2] xfs_io: include headers for preadv/pwritev Eric Sandeen
2012-10-09 22:08 ` [PATCH 2/2] xfs_io: configure tests for preadv/pwritev & sync_file_range Eric Sandeen
2012-10-09 22:28   ` Dave Chinner
2012-10-09 22:32     ` Eric Sandeen
2012-10-09 22:56       ` Dave Chinner
2012-10-09 22:57         ` Eric Sandeen
2012-10-09 23:05           ` Dave Chinner
2012-10-10  3:40   ` [PATCH 2/2 V2] " Eric Sandeen
2012-10-10 23:25     ` Dave Chinner
2012-10-09 22:21 ` [PATCH 1/2] xfs_io: include headers for preadv/pwritev Dave Chinner
2012-10-10  3:37 ` [PATCH 1/2 V2] " Eric Sandeen
2012-10-10 23:24   ` Dave Chinner
2012-10-11 20:40 ` Mark Tinguely [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=50772ECF.5050308@sgi.com \
    --to=tinguely@sgi.com \
    --cc=sandeen@redhat.com \
    --cc=xfs@oss.sgi.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 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.