From: Richard Henderson <richard.henderson@linaro.org>
To: Jeuk Kim <jeuk20.kim@gmail.com>, qemu-devel@nongnu.org
Cc: fam@euphon.net, pbonzini@redhat.com, qemu-block@nongnu.org,
jeuk20.kim@samsung.com, j-young.choi@samsung.com
Subject: Re: [PULL 0/1] ufs queue
Date: Sun, 30 Jun 2024 16:11:47 -0700 [thread overview]
Message-ID: <62f95d15-d8f9-4fd1-b97b-7c032f8261c3@linaro.org> (raw)
In-Reply-To: <cover.1719719120.git.jeuk20.kim@samsung.com>
On 6/29/24 20:52, Jeuk Kim wrote:
> From: Jeuk Kim<jeuk20.kim@samsung.com>
>
> The following changes since commit 3665dd6bb9043bef181c91e2dce9e1efff47ed51:
>
> Merge tag 'for-upstream' ofhttps://gitlab.com/bonzini/qemu into staging (2024-06-28 16:09:38 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/jeuk20.kim/qemu.git tags/pull-ufs-20240630
>
> for you to fetch changes up to e12b11f6f29272ee31ccde6b0db1a10139e87083:
>
> hw/ufs: Fix potential bugs in MMIO read|write (2024-06-30 12:44:32 +0900)
>
> ----------------------------------------------------------------
> hw/ufs: fix coverity issue
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/9.1 as appropriate.
r~
next prev parent reply other threads:[~2024-06-30 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 3:52 [PULL 0/1] ufs queue Jeuk Kim
2024-06-30 3:52 ` [PULL 1/1] hw/ufs: Fix potential bugs in MMIO read|write Jeuk Kim
2024-06-30 23:11 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 1:31 [PULL 0/1] ufs queue Jeuk Kim
2024-07-08 10:00 ` Jeuk Kim
2024-04-29 3:25 Jeuk Kim
2024-04-29 13:41 ` Stefan Hajnoczi
2024-04-29 14:02 ` Richard Henderson
2024-05-01 22:15 ` Richard Henderson
2023-10-30 4:02 Jeuk Kim
2023-10-31 7:50 ` Stefan Hajnoczi
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=62f95d15-d8f9-4fd1-b97b-7c032f8261c3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=fam@euphon.net \
--cc=j-young.choi@samsung.com \
--cc=jeuk20.kim@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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).