linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git sysv pile
Date: Fri, 26 May 2023 15:25:18 +0200	[thread overview]
Message-ID: <2886258.e9J7NaK4W3@suse> (raw)
In-Reply-To: <5939173.lOV4Wx5bFT@suse>

On venerdì 26 maggio 2023 12:32:59 CEST Fabio M. De Francesco wrote:
> On giovedì 25 maggio 2023 22:10:46 CEST Jan Kara wrote:
> > On Mon 27-03-23 12:29:56, Fabio M. De Francesco wrote:
> > > On lunedì 20 marzo 2023 13:47:25 CEST Jan Kara wrote:
> > > > On Mon 20-03-23 12:18:38, Fabio M. De Francesco wrote:
> > > > > On giovedì 16 marzo 2023 11:30:21 CET Fabio M. De Francesco wrote:
> > > > > > On giovedì 16 marzo 2023 10:00:35 CET Jan Kara wrote:
> > > > > > > On Wed 15-03-23 19:08:57, Fabio M. De Francesco wrote:
> > > > > > > > On mercoledì 1 marzo 2023 15:14:16 CET Al Viro wrote:
> > > [snip]
> > > 
> > > > > > > > > I think I've pushed a demo patchset to vfs.git at some point
> > > > > > > > > back
> > > 
> > > in
> > > 
> > > > > > > > > January... Yep - see #work.ext2 in there; completely 
untested,
> > > > > > > > > though.
> > > 
> > > Al,
> > > 
> > > I reviewed and tested your patchset (please see below).
> > > 
> > > I think that you probably also missed Jan's last message about how you
> > > prefer
> > > they to be treated.
> > > 
> > > Jan asked you whether you will submit these patches or he should just 
pull
> > > your branch into his tree.
> > > 
> > > Please look below for my tags and Jan's question.
> > 
> > Ok, Al didn't reply
> 
> I noticed it...
> 
> > so I've just pulled the patches from Al's tree,
> 
> Thank you very much for doing this :-)
> 
> > added
> > your Tested-by tag
> 
> Did you also notice the Reviewed-by tags?
> 

Well, it looks like you missed my Reviewed-by tags at https://lore.kernel.org/
lkml/3019063.4lk9UinFSI@suse/

FWIW, I'd just like to say that I did the review of Al's patchset because I 
know the code that is modeled after a similar series to fs/sysv, which in turn 
I made following Al's suggestions.

However, I suppose it's up to you to decide whether or not is worth mentioning 
my reviews :-)

Thanks,

Fabio

> > and push out the result into linux-next.
> 
> Great!
> Again thanks,
> 
> Fabio
> 
> 
> Honza
> 
> > --
> > Jan Kara <jack@suse.com>
> > SUSE Labs, CR





  reply	other threads:[~2023-05-26 13:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  3:26 [git pull] vfs.git sysv pile Al Viro
2023-02-25  3:40 ` pr-tracker-bot
2023-03-01 11:20 ` Fabio M. De Francesco
2023-03-01 13:00   ` Jan Kara
2023-03-01 13:21     ` Fabio M. De Francesco
2023-03-01 14:14     ` Al Viro
2023-03-02  9:59       ` Jan Kara
2023-03-02 11:31         ` Fabio M. De Francesco
2023-03-02 19:35           ` Al Viro
2023-03-02 22:35             ` Al Viro
2023-03-03  5:10               ` Fabio M. De Francesco
2023-03-03  4:58             ` Fabio M. De Francesco
2023-03-08 17:40             ` Fabio M. De Francesco
2023-03-09 13:45               ` Fabio M. De Francesco
2023-03-02 19:26         ` Al Viro
2023-03-03  9:24           ` Jan Kara
2023-03-15 18:08       ` Fabio M. De Francesco
2023-03-16  9:00         ` Jan Kara
2023-03-16 10:30           ` Fabio M. De Francesco
2023-03-20 11:18             ` Fabio M. De Francesco
2023-03-20 12:47               ` Jan Kara
2023-03-27 10:29                 ` Fabio M. De Francesco
2023-05-25 20:10                   ` Jan Kara
2023-05-26 10:32                     ` Fabio M. De Francesco
2023-05-26 13:25                       ` Fabio M. De Francesco [this message]
2023-05-29  9:02                         ` Jan Kara

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=2886258.e9J7NaK4W3@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).