linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Sassu <roberto.sassu@huawei.com>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Rob Landley <rob@landley.net>, "hpa@zytor.com" <hpa@zytor.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	Arvind Sankar <nivedita@alum.mit.edu>,
	"Mimi Zohar" <zohar@linux.ibm.com>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"linux-security-module@vger.kernel.org" 
	<linux-security-module@vger.kernel.org>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	"initramfs@vger.kernel.org" <initramfs@vger.kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bug-cpio@gnu.org" <bug-cpio@gnu.org>,
	"zohar@linux.vnet.ibm.com" <zohar@linux.vnet.ibm.com>,
	Silviu Vlasceanu <Silviu.Vlasceanu@huawei.com>,
	Dmitry Kasatkin <dmitry.kasatkin@huawei.com>,
	"takondra@cisco.com" <takondra@cisco.com>,
	"kamensky@cisco.com" <kamensky@cisco.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"james.w.mcmechan@gmail.com" <james.w.mcmechan@gmail.com>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	Dirk Behme <dirk.behme@de.bosch.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
Date: Fri, 10 Jun 2022 15:38:24 +0000	[thread overview]
Message-ID: <4bc349a59e4042f7831b1190914851fe@huawei.com> (raw)
In-Reply-To: <20220610153336.GA8881@lxhi-065>

> From: Eugeniu Rosca [mailto:erosca@de.adit-jv.com]
> Sent: Friday, June 10, 2022 5:34 PM
> Hello Roberto,
> 
> On Do, Jun 09, 2022 at 11:05:45 +0000, Roberto Sassu wrote:
> > > From: Eugeniu Rosca [mailto:erosca@de.adit-jv.com]
> > > Sent: Thursday, June 9, 2022 12:26 PM
> > > Dear Roberto,
> > > Cc: Yamada-san, linux-kbuild
> > >
> > > On Mi, Jul 24, 2019 at 05:34:53 +0200, Roberto Sassu wrote:
> > > > Is there anything I didn't address in this patch set, that is delaying
> > > > the review? I would appreciate if you can give me a feedback, positive
> > > > or negative.
> > > >
> > > > Thanks a lot!
> > > >
> > > > Roberto
> > >
> > > Some of our users have recently asked for this patch series.
> >
> > Hello
> >
> > thanks for your interest in this patch set.
> >
> > > Could you please feedback if this is the latest revision available or
> > > maybe there is a newer one developed and potentially not shared on LKML?
> >
> > Yes, it is the latest revision available. There might have been few
> > fixes in the final code. You may want to have a look at:
> 
> Many thanks for the links to the updated patch revisions. It looks
> like the new versions added a couple of bugfixes and refinements.
> 
> With more users now using this feature, do you think there is a higher
> chance for upstreaming, compared to 2019 (original submission date)?

Hello Eugeniu

I would be happy to address the remaining concerns, or take more
suggestions, and then develop a new version of the patch set.

Thanks

Roberto

HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
Managing Director: Li Peng, Yang Xi, Li He

  reply	other threads:[~2022-06-10 15:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 12:18 [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-05-23 12:18 ` [PATCH v4 1/3] initramfs: add file metadata Roberto Sassu
2022-06-15 17:54   ` Eugeniu Rosca
2019-05-23 12:18 ` [PATCH v4 2/3] initramfs: read metadata from special file METADATA!!! Roberto Sassu
2019-07-01 12:54   ` Mimi Zohar
2019-05-23 12:18 ` [PATCH v4 3/3] gen_init_cpio: add support for file metadata Roberto Sassu
2019-06-30 15:27   ` Mimi Zohar
2022-06-16 14:47   ` Eugeniu Rosca
2022-06-16 15:16   ` Eugeniu Rosca
2022-06-30 15:06     ` Roberto Sassu
2022-06-30 20:38       ` Eugeniu Rosca
2019-06-03  9:31 ` [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-06-03 18:32   ` Rob Landley
2019-06-26  8:15     ` Roberto Sassu
2019-06-30 15:39       ` Mimi Zohar
2019-07-01 13:42         ` Roberto Sassu
2019-07-01 14:31           ` Mimi Zohar
2019-07-15 16:54             ` Roberto Sassu
2019-07-24 15:34               ` Roberto Sassu
2022-06-09 10:26                 ` Eugeniu Rosca
2022-06-09 11:05                   ` Roberto Sassu
2022-06-10 15:33                     ` Eugeniu Rosca
2022-06-10 15:38                       ` Roberto Sassu [this message]
2022-06-15  9:27                         ` Eugeniu Rosca
2022-07-18 16:36                           ` Jim Baxter
2022-07-18 16:49                             ` Roberto Sassu
2022-07-18 18:08                               ` Jim Baxter
2022-07-19  6:55                                 ` Roberto Sassu
2022-07-19 11:50                                   ` Rob Landley
2022-07-19 12:26                                     ` Roberto Sassu
2022-07-19 14:14                                       ` Rob Landley
2022-07-20 11:52                                         ` Roberto Sassu
2022-07-29 10:37                                   ` Jim Baxter
2022-07-30  9:39                                     ` Rob Landley
2022-07-19 11:33                                 ` Rob Landley
2022-07-19 11:00                               ` Rob Landley
2019-07-01 13:22 ` Mimi Zohar
2022-06-15 15:50 ` Alexander Lobakin
2022-06-15 16:03   ` Roberto Sassu
2022-06-16 13:24 ` Eugeniu Rosca

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=4bc349a59e4042f7831b1190914851fe@huawei.com \
    --to=roberto.sassu@huawei.com \
    --cc=Silviu.Vlasceanu@huawei.com \
    --cc=arnd@arndb.de \
    --cc=bug-cpio@gnu.org \
    --cc=dirk.behme@de.bosch.com \
    --cc=dmitry.kasatkin@huawei.com \
    --cc=erosca@de.adit-jv.com \
    --cc=hpa@zytor.com \
    --cc=initramfs@vger.kernel.org \
    --cc=james.w.mcmechan@gmail.com \
    --cc=kamensky@cisco.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nivedita@alum.mit.edu \
    --cc=rob@landley.net \
    --cc=roscaeugeniu@gmail.com \
    --cc=takondra@cisco.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zohar@linux.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    /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).