All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: linux-kernel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Latchesar Ionkov <lucho@ionkov.net>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] 9p: add myself as reviewer to MAINTAINERS
Date: Tue, 04 Jan 2022 15:21:57 +0100	[thread overview]
Message-ID: <2284086.ouBcKq9vr7@silver> (raw)
In-Reply-To: <YdRQWtQNO/DA02VW@codewreck.org>

On Dienstag, 4. Januar 2022 14:49:14 CET Dominique Martinet wrote:
> Christian Schoenebeck wrote on Tue, Jan 04, 2022 at 01:53:59PM +0100:
> > Volunteering as reviewer for 9p patches. As I am quite familiar with the
> > 9p code base in the Linux kernel already, plus being current maintainer
> > of 9p in QEMU this move probably makes sense.
> 
> There honestly isn't much coming in, but it'll be a pleasure to have you
> help when you can, I'll push this to Linus with other 5.17 changes in a
> couple of weeks :)

I know, it is the same with 9p on QEMU side. But I felt you were currently the 
only person providing service at this end, so I thought a bit of help might 
not hurt.

> I didn't reply to your series for bigger msize, I doubt I'll have time
> to do any useful tests for it this round but I'm thinking of taking the
> first patch first now as it makes sense independantly.

Sure!

> I feel that the rest needs more attention and will be for next cycle,
> sorry for the delay

Yeah, that code definitely still needs some decantation time. No rush. Maybe 
some other people find some time for review or testing in the meantime.

Thanks Dominique!

Best regards,
Christian Schoenebeck



      reply	other threads:[~2022-01-04 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 12:53 [PATCH] 9p: add myself as reviewer to MAINTAINERS Christian Schoenebeck
2022-01-04 13:49 ` Dominique Martinet
2022-01-04 14:21   ` Christian Schoenebeck [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=2284086.ouBcKq9vr7@silver \
    --to=linux_oss@crudebyte.com \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@gmail.com \
    --cc=groug@kaod.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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.