linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: akshay st <akshayts@yahoo.co.in>
To: Artem.Bityutskiy@nokia.com
Cc: linux-mtd@lists.infradead.org
Subject: UBIFS and mkfs.ubifs Security Extended attribute support patch available?
Date: Thu, 3 Jun 2010 01:08:28 -0700 (PDT)	[thread overview]
Message-ID: <439695.63477.qm@web94901.mail.in2.yahoo.com> (raw)

Hi Artem,
Sending message again, because i had to send in plain text.
I was looking for a patch to support Security extended attribute
support for UBIFS in kernel and mkfs.ubifs. Also i dont understand
what security extended attribute to write in mkfs.ubifs. Can u give me
some insight, or if there is some link which tells the same.
If there is no patch available i was looking to implement it. Can u please advise me.

Warm Regards,
Akshay




             reply	other threads:[~2010-06-03  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03  8:08 akshay st [this message]
2010-06-03 14:28 ` UBIFS and mkfs.ubifs Security Extended attribute support patch available? Artem Bityutskiy
     [not found] <934572.90077.qm@web94913.mail.in2.yahoo.com>
2010-06-04  5:15 ` Artem Bityutskiy

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=439695.63477.qm@web94901.mail.in2.yahoo.com \
    --to=akshayts@yahoo.co.in \
    --cc=Artem.Bityutskiy@nokia.com \
    --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 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).