From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/2] btrfs-progs: more statics & removals
Date: Tue, 06 Aug 2013 20:01:33 -0500 [thread overview]
Message-ID: <52019C6D.9050308@redhat.com> (raw)
2 patches, one for shared kernel files, one for pure userspace.
In kernelspace, lots of unused functions purged. Some functions
which could be static are left alone if they aren't marked static
in kernelspace.
userspace only has a couple removals, mostly just marking static
& removing prototypes in headers as appropriate.
Thanks,
-Eric
next reply other threads:[~2013-08-07 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 1:01 Eric Sandeen [this message]
2013-08-07 1:03 ` [PATCH 1/2] btrfs-progs: mark static & remove unused from shared kernel code Eric Sandeen
2013-08-07 1:05 ` [PATCH 2/2] btrfs-progs: mark static & remove unused from non-kernel code Eric Sandeen
2013-08-07 3:49 ` Eric Sandeen
2013-08-07 7:54 ` Stefan Behrens
2013-08-07 15:17 ` Eric Sandeen
2013-08-09 14:10 ` David Sterba
2013-08-09 14:39 ` Stefan Behrens
2013-08-09 20:20 ` [PATCH 2/2 V2] " Eric Sandeen
2013-08-09 22:48 ` David Sterba
2013-08-09 23:16 ` Eric Sandeen
2013-08-09 23:25 ` 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=52019C6D.9050308@redhat.com \
--to=sandeen@redhat.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 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).