From: sfjro@users.sourceforge.net
To: tg@mirbsd.de
Cc: aufs-users@lists.sourceforge.net, debian-kernel@lists.debian.org,
linux-m68k@vger.kernel.org
Subject: [PATCH 0/2] aufs: headers (Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt)
Date: Tue, 3 Jan 2012 14:21:20 +0900 [thread overview]
Message-ID: <1325568082-25540-1-git-send-email-sfjro@users.sourceforge.net> (raw)
In-Reply-To: <Pine.BSM.4.64L.1201021735430.29291@herc.mirbsd.org>
From: J. R. Okajima <hooanon05@yahoo.co.jp>
Thorsten Glaser:
> Please send patches that _should_ apply against what=E2=80=99s in Debian.
> I don=E2=80=99t have time to play the merge game at the moment.
Which version of debian?
As you might know, the aufs module in the debian stable squeeze is out
of my control.
Anyway, this patch series is against the aufs2.2-35 branch in
aufs2-standalone.git.
J. R. Okajima (2):
aufs: headers 1/2, bugfix, where the pr_fmt macro definition
aufs: headers 2/2, simply refined
fs/aufs/Makefile | 4 ++--
fs/aufs/branch.c | 1 -
fs/aufs/branch.h | 2 --
fs/aufs/cpup.c | 2 --
fs/aufs/cpup.h | 4 ----
fs/aufs/dbgaufs.h | 3 ---
fs/aufs/dcsub.h | 1 -
fs/aufs/debug.c | 1 -
fs/aufs/debug.h | 8 --------
fs/aufs/dentry.h | 1 -
fs/aufs/dir.c | 1 -
fs/aufs/dir.h | 1 -
fs/aufs/dynop.h | 4 ----
fs/aufs/export.c | 1 -
fs/aufs/f_op.c | 2 --
fs/aufs/f_op_sp.c | 1 -
fs/aufs/file.c | 3 ---
fs/aufs/file.h | 1 -
fs/aufs/finfo.c | 1 -
fs/aufs/fstype.h | 1 -
fs/aufs/hfsplus.c | 1 -
fs/aufs/i_op.c | 2 --
fs/aufs/inode.h | 2 --
fs/aufs/ioctl.c | 1 -
fs/aufs/opts.c | 2 --
fs/aufs/opts.h | 3 ---
fs/aufs/rdu.c | 2 --
fs/aufs/rwsem.h | 1 -
fs/aufs/sbinfo.c | 1 -
fs/aufs/spl.h | 4 ----
fs/aufs/super.c | 3 +--
fs/aufs/super.h | 1 -
fs/aufs/sysaufs.c | 2 --
fs/aufs/sysaufs.h | 2 --
fs/aufs/sysfs.c | 3 ---
fs/aufs/sysrq.c | 3 ---
fs/aufs/vdir.c | 1 -
fs/aufs/vfsub.c | 2 --
fs/aufs/whout.c | 1 -
fs/aufs/whout.h | 1 -
fs/aufs/wkq.h | 4 ----
fs/aufs/xino.c | 2 --
include/linux/aufs_type.h | 20 ++++++++++++++------
43 files changed, 17 insertions(+), 90 deletions(-)
--
1.7.2.5
next prev parent reply other threads:[~2012-01-03 5:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 17:06 [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt Ben Hutchings
2011-12-31 4:46 ` sfjro
2011-12-31 8:01 ` Geert Uytterhoeven
2011-12-31 16:31 ` Thorsten Glaser
2012-01-02 2:58 ` sfjro
2012-01-02 3:40 ` Ben Hutchings
2012-01-02 4:01 ` sfjro
2012-01-02 2:04 ` sfjro
2011-12-31 22:18 ` Thorsten Glaser
2011-12-31 22:31 ` Thorsten Glaser
2012-01-01 1:15 ` Thorsten Glaser
2012-01-02 6:45 ` sfjro
2012-01-02 10:31 ` Thorsten Glaser
2012-01-02 13:15 ` sfjro
2012-01-02 13:30 ` Thorsten Glaser
2012-01-02 13:53 ` sfjro
2012-01-02 16:14 ` Thorsten Glaser
2012-01-02 16:53 ` sfjro
2012-01-02 17:36 ` Thorsten Glaser
2012-01-03 5:21 ` sfjro [this message]
2012-01-03 5:21 ` [PATCH 1/2] aufs: headers 1/2, bugfix, where the pr_fmt macro definition sfjro
2012-01-03 5:21 ` [PATCH 2/2] aufs: headers 2/2, simply refined sfjro
2011-12-31 22:55 ` [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt Thorsten Glaser
2012-01-01 8:47 ` Geert Uytterhoeven
2012-01-01 14:48 ` Thorsten Glaser
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=1325568082-25540-1-git-send-email-sfjro@users.sourceforge.net \
--to=sfjro@users.sourceforge.net \
--cc=aufs-users@lists.sourceforge.net \
--cc=debian-kernel@lists.debian.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/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