All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
	linux-btrfs@vger.kernel.org, Josef Bacik <jbacik@fb.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] btrfs: fix size_t format string
Date: Mon, 9 Mar 2015 12:49:14 +0100	[thread overview]
Message-ID: <20150309114914.GD5841@twin.jikos.cz> (raw)
In-Reply-To: <2448187.keuqSF9F23@wuerfel>

On Mon, Mar 09, 2015 at 12:39:36PM +0100, Arnd Bergmann wrote:
> This warning has been rather annoying because it shows up in every
> 'allmodconfig' build. I assume others have reported it before, but
> please apply some fix for it, ideally before 4.0.

Sorry about that, we're aware of the warning and Chris will push the
patch to the next rc.

WARNING: multiple messages have this Message-ID (diff)
From: dsterba@suse.cz (David Sterba)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] btrfs: fix size_t format string
Date: Mon, 9 Mar 2015 12:49:14 +0100	[thread overview]
Message-ID: <20150309114914.GD5841@twin.jikos.cz> (raw)
In-Reply-To: <2448187.keuqSF9F23@wuerfel>

On Mon, Mar 09, 2015 at 12:39:36PM +0100, Arnd Bergmann wrote:
> This warning has been rather annoying because it shows up in every
> 'allmodconfig' build. I assume others have reported it before, but
> please apply some fix for it, ideally before 4.0.

Sorry about that, we're aware of the warning and Chris will push the
patch to the next rc.

  reply	other threads:[~2015-03-09 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 11:39 [PATCH] btrfs: fix size_t format string Arnd Bergmann
2015-03-09 11:39 ` Arnd Bergmann
2015-03-09 11:49 ` David Sterba [this message]
2015-03-09 11:49   ` David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2018-07-17 13:52 Arnd Bergmann
2018-07-17 14:33 ` Qu Wenruo
2018-07-17 16:02   ` Arnd Bergmann
2018-07-17 15:04 ` David Sterba
2018-07-23 17:07   ` Randy Dunlap
2018-07-24  8:19     ` David Sterba

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=20150309114914.GD5841@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=arnd@arndb.de \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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.