From: Fengguang Wu <fengguang.wu@intel.com>
To: Alexander Block <ablock84@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [ablock84-btrfs:btrfs-far 20/20] fs/btrfs/send.c:1683:51: sparse: incorrect type in argument 5 (different base types)
Date: Wed, 7 Nov 2012 08:22:48 +0800 [thread overview]
Message-ID: <20121107002248.GA5286@localhost> (raw)
In-Reply-To: <CAB9VWqBg-WFg=G1ogfGWCDW0rJaGce09X=ceTGeoSKY5mMvKuQ@mail.gmail.com>
On Tue, Nov 06, 2012 at 09:57:47PM +0100, Alexander Block wrote:
> On Tue, Nov 6, 2012 at 9:51 PM, kbuild test robot
> <fengguang.wu@intel.com> wrote:
> > tree: git://github.com/ablock84/linux-btrfs.git btrfs-far
> > head: f9a5bb450a8cc7aa5fd4f11d0306b3f48cf2771d
> > commit: f9a5bb450a8cc7aa5fd4f11d0306b3f48cf2771d [20/20] Btrfs: use libfarstream for btrfs send
> Sorry for the noise. For some reason that I currently don't understand
> there is a build robot subscribed to my github account which thinks
> that posting to the mailing list is a good idea...
Sorry about that. I've removed the CC list for your tree.
Thanks,
Fengguang
prev parent reply other threads:[~2012-11-07 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 20:51 [ablock84-btrfs:btrfs-far 20/20] fs/btrfs/send.c:1683:51: sparse: incorrect type in argument 5 (different base types) kbuild test robot
2012-11-06 20:57 ` Alexander Block
2012-11-07 0:22 ` Fengguang Wu [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=20121107002248.GA5286@localhost \
--to=fengguang.wu@intel.com \
--cc=ablock84@googlemail.com \
--cc=linux-btrfs@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.