From: Fengguang Wu <fengguang.wu@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: fs/btrfs/extent-tree.c:8430:9: error: format not a string literal and no format arguments
Date: Thu, 21 Nov 2013 09:03:12 +0800 [thread overview]
Message-ID: <20131121010312.GA8841@localhost> (raw)
In-Reply-To: <CAGXu5jLXf=aOQa7XnvJ21n4VaVcNOUxhLGcFFdWOPXDam6sZ8g@mail.gmail.com>
On Wed, Nov 20, 2013 at 08:04:58AM -0800, Kees Cook wrote:
> On Tue, Nov 19, 2013 at 8:05 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > On Tue, Nov 19, 2013 at 07:56:35PM -0800, Kees Cook wrote:
> >> Hi!
> >>
> >> Which tree is 'devel-snb'? I don't see that on the kernel.org trees.
> >
> > It's my local merge branch, based on the latest upstream release.
>
> Hm, which release? I don't see it in 3.12, Linus's tree, nor linux-next.
'devel-snb' is one of my private branch, starting from v3.12, merging
several public git branches (eg. btrfs-next, kees/format-security, ...)
and finally do compile tests on top of it. This effectively tests
all of the merged public branches in one go. :)
Thanks,
Fengguang
next prev parent reply other threads:[~2013-11-21 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528c09f9.S0ecVwNN2c+fnUkv%fengguang.wu@intel.com>
[not found] ` <CAGXu5jLoG00u2svBW6W5h9QsfYw1zZwYhZ1k4HG2UsvcWPHxuQ@mail.gmail.com>
2013-11-20 4:05 ` fs/btrfs/extent-tree.c:8430:9: error: format not a string literal and no format arguments Fengguang Wu
2013-11-20 16:04 ` Kees Cook
2013-11-21 1:03 ` Fengguang Wu [this message]
2013-11-20 17:30 ` Chris Mason
2013-11-20 18:05 ` Jeff Mahoney
2013-11-20 18:37 ` Kees Cook
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=20131121010312.GA8841@localhost \
--to=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--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.