All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Mainz, Roland" <R.Mainz@eckelmann.de>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Support for @(POSIX|NFSv4)-ACLs on UBIFS ?
Date: Mon, 16 Dec 2019 11:47:40 +0100	[thread overview]
Message-ID: <CAFLxGvxB_BCwBxJwA0Q1_Y63NbRUKdruiuLDnx_vpCuL8DRHMw@mail.gmail.com> (raw)
In-Reply-To: <882abf5cf5994b3db6a4d27b62b34b95@eckelmann.de>

On Mon, Dec 16, 2019 at 11:10 AM Mainz, Roland <R.Mainz@eckelmann.de> wrote:
> > -----Original Message-----
> > From: Richard Weinberger [mailto:richard.weinberger@gmail.com]
> > Sent: Monday, December 16, 2019 10:44 AM
> > To: Mainz, Roland <R.Mainz@eckelmann.de>
> > Cc: linux-mtd@lists.infradead.org
> > Subject: Re: Support for @(POSIX|NFSv4)-ACLs on UBIFS ?
> >
> > On Mon, Dec 16, 2019 at 10:09 AM Mainz, Roland <R.Mainz@eckelmann.de>
> > wrote:
> > > Are there any plans to support POSIX ACLs (or the extended NFSv4 set of
> > ACLs) on UBIFS ?
> >
> > Well, if there is need for it I can try to find time to implement it.
> > ...or better, you implement it and send patches :)
>
> Someone already send patches around, see https://lwn.net/Articles/657287/

Ah, 2015. This explains why nobody cared much. ;-\

Did you try the patches? ...and you can forward port them?

-- 
Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2019-12-16 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  9:09 Support for @(POSIX|NFSv4)-ACLs on UBIFS ? Mainz, Roland
2019-12-16  9:44 ` Richard Weinberger
2019-12-16 10:10   ` Mainz, Roland
2019-12-16 10:47     ` Richard Weinberger [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=CAFLxGvxB_BCwBxJwA0Q1_Y63NbRUKdruiuLDnx_vpCuL8DRHMw@mail.gmail.com \
    --to=richard.weinberger@gmail.com \
    --cc=R.Mainz@eckelmann.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.