qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jeuk Kim <jeuk20.kim@gmail.com>, qemu-devel@nongnu.org
Cc: jeuk20.kim@samsung.com, kwolf@redhat.com, hreitz@redhat.com,
	thuth@redhat.com, lvivier@redhat.com, pbonzini@redhat.com,
	fam@euphon.net, qemu-block@nongnu.org
Subject: Re: [PATCH] hw/ufs: Modify lu.c to share codes with SCSI subsystem
Date: Mon, 30 Oct 2023 05:11:04 +0100	[thread overview]
Message-ID: <53a87de9-6586-5a66-de53-152dc4cb4d1d@linaro.org> (raw)
In-Reply-To: <9fd0dc1f55724fa79011be231cc27bf4aab11157.1697764912.git.jeuk20.kim@samsung.com>

Hi Jeuk,

On 20/10/23 03:51, Jeuk Kim wrote:
> This patch removes the code that ufs-lu was duplicating from
> scsi-hd and allows them to share code.
> 
> It makes ufs-lu have a virtual scsi-bus and scsi-hd internally.
> This allows scsi related commands to be passed thorugh to the scsi-hd.
> The query request and nop command work the same as the existing logic.
> 
> Well-known lus do not have a virtual scsi-bus and scsi-hd, and
> handle the necessary scsi commands by emulating them directly.
> 
> Signed-off-by: Jeuk Kim <jeuk20.kim@samsung.com>
> ---
>   hw/ufs/lu.c            | 1473 +++++++---------------------------------

I liked this patch intent, but almost 1500 lines changed in a single
patch make it impossible to review. Ideally each patch shouldn't modify
more than 100 lines, otherwise reviewers are either exhausted or can't
be careful enough and miss possible bugs or design issues.

Regards,

Phil.

>   hw/ufs/trace-events    |   25 -
>   hw/ufs/ufs.c           |  202 +-----
>   hw/ufs/ufs.h           |   36 +-
>   include/block/ufs.h    |    2 +-
>   tests/qtest/ufs-test.c |   37 +-
>   6 files changed, 315 insertions(+), 1460 deletions(-)



  reply	other threads:[~2023-10-30  4:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  1:51 [PATCH] hw/ufs: Modify lu.c to share codes with SCSI subsystem Jeuk Kim
2023-10-30  4:11 ` Philippe Mathieu-Daudé [this message]
2023-10-30 17:15   ` Jeuk Kim

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=53a87de9-6586-5a66-de53-152dc4cb4d1d@linaro.org \
    --to=philmd@linaro.org \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=jeuk20.kim@gmail.com \
    --cc=jeuk20.kim@samsung.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).