From: Marc Kleine-Budde <mkl@pengutronix.de>
To: linux-mtd@lists.infradead.org
Cc: kernel@pengutronix.de
Subject: [PATCH v2 0/5] mkfs.ubifs: cleanups + extended attribute support
Date: Thu, 12 Nov 2015 10:31:23 +0100 [thread overview]
Message-ID: <1447320688-3086-1-git-send-email-mkl@pengutronix.de> (raw)
Hello,
this series applies to current git master. The first 3 patches are cleanup
patches, in the 4th adds extended attributes support. Patch 5 adds a option to
write the used inode number to an extended attribute, so that other offline
tools like IMA, that process the inode number can work. See description of
patch 5 for a detailed explanation.
regards,
Marc
changes since v1:
- add Daniel Walter's reviewed by to patches 1-3
- add option to build without xattr support - patches 4,5 (as Daniel suggested)
- switch from dynamically allocated attr value buffer to fixed size array on stack,
as inode numbers where not stable between mkfs.ubifs invocations - patch 4
next reply other threads:[~2015-11-12 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 9:31 Marc Kleine-Budde [this message]
2015-11-12 9:31 ` [PATCH v2 1/5] mkfs.ubifs: change add_directory argument to 'existing' Marc Kleine-Budde
2015-11-12 9:31 ` [PATCH v2 2/5] mkfs.ubifs: use xmalloc/xzalloc for allocating memory Marc Kleine-Budde
2015-11-12 9:31 ` [PATCH v2 3/5] mkfs.ubifs: simplify make_path with xasprintf Marc Kleine-Budde
2015-11-12 9:31 ` [PATCH v2 4/5] mkfs.ubifs: Add extended attribute support Marc Kleine-Budde
2015-11-12 9:31 ` [PATCH v2 5/5] mkfs.ubifs: Optionally create extended attribute with inode number Marc Kleine-Budde
2015-11-12 9:53 ` [PATCH v2 0/5] mkfs.ubifs: cleanups + extended attribute support Richard Weinberger
2015-11-12 9:56 ` Marc Kleine-Budde
2015-11-12 18:40 ` Brian Norris
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=1447320688-3086-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.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.