All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH ubdsrv] tgt_null: Return number of sectors read/written
Date: Mon, 27 Jun 2022 15:46:35 +0800	[thread overview]
Message-ID: <YrlgW8qz5aEVfegR@T590> (raw)
In-Reply-To: <87k0983bw1.fsf@collabora.com>

On Wed, Jun 22, 2022 at 12:23:42PM -0400, Gabriel Krisman Bertazi wrote:
> Ming Lei <ming.lei@redhat.com> writes:
> 
> > On Tue, Jun 21, 2022 at 06:48:39PM -0400, Gabriel Krisman Bertazi wrote:
> >> Hi Ming,
> >> 
> >> I wrote this against your devel-v3 branch.  I'm wondering if you plan to
> >> send a new version of the kernel patch soon? From the latest
> >
> > Yeah, that is on my todo list:
> >
> > https://github.com/ming1/linux/commits/my_for-5.19-ubd-devel_v3
> >
> > there has lots cleanup & improvement.
> >
> >> discussions, I don't think there were major issues found on review. :)
> >
> > One problem is the driver name, and Christoph thought we have
> > 'arch/um/drivers/ubd*.c'. Not thought of one good candidate yet.
> 
> Hi Ming,
> 
> Thanks for the info, and sorry for not noticing the fix merged on Jun, 3rd
> on the master branch.  I will follow that branch when testing and submit
> fixes I find along the way.

That is great!

> 
> I guess you have considered a lot of names, but I'd suggest any of:
> 
>  * blkuser,
>  * ublk
>  * BUSE (as in Block FUSE, though there is another non-upstream
> project with that name),
>  * UBIO (as in UIO, but for Block IO)
>  * B2U (Block IO Backed by userspace) :-P
> 
> TBH, my favorite is ublk.

Me too, will change to it in v3 if no one objects.

Thanks,
Ming


      reply	other threads:[~2022-06-27  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 22:48 [PATCH ubdsrv] tgt_null: Return number of sectors read/written Gabriel Krisman Bertazi
2022-06-22  0:19 ` Ming Lei
2022-06-22 16:23   ` Gabriel Krisman Bertazi
2022-06-27  7:46     ` Ming Lei [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=YrlgW8qz5aEVfegR@T590 \
    --to=ming.lei@redhat.com \
    --cc=hch@lst.de \
    --cc=krisman@collabora.com \
    --cc=linux-block@vger.kernel.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.