From: Valdis.Kletnieks@vt.edu
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, chris.mason@oracle.com
Subject: Re: [PATCH] btrfs/extent_map.c: quiet sparse noise
Date: Fri, 23 Sep 2011 14:58:37 -0400 [thread overview]
Message-ID: <25617.1316804317@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 22 Sep 2011 18:45:56 PDT." <201109221845.56204.hartleys@visionengravers.com>
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
On Thu, 22 Sep 2011 18:45:56 PDT, H Hartley Sweeten said:
> Quiet the sparse noise:
>
> warning: symbol '__lookup_extent_mapping' was not declared. Should it be static?
Patch itself is correct, changelog is bad. You're not quieting sparse noise,
you're making a declaration static because it doesn't need external visibility.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-09-23 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 1:45 [PATCH] btrfs/extent_map.c: quiet sparse noise H Hartley Sweeten
2011-09-23 18:58 ` Valdis.Kletnieks [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=25617.1316804317@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=chris.mason@oracle.com \
--cc=hartleys@visionengravers.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).