qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: AlexChen <alex.chen@huawei.com>,
	Yuval Shaia <yuval.shaia.ml@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Euler Robot <euler.robot@huawei.com>
Subject: Re: [Qemu-devel] [PULL 0/1] RDMA queue
Date: Fri, 1 Jan 2021 14:32:48 +0000	[thread overview]
Message-ID: <CAFEAcA_4VnP8KSy-Z_OsVsue=81+SFNf6N_2cRHXe3LaY-+tiQ@mail.gmail.com> (raw)
In-Reply-To: <20201218190022.31214-1-marcel.apfelbaum@gmail.com>

On Fri, 18 Dec 2020 at 19:00, Marcel Apfelbaum
<marcel.apfelbaum@gmail.com> wrote:
>
> The following changes since commit a05f8ecd88f15273d033b6f044b850a8af84a5b8:
>
>   Merge remote-tracking branch 'remotes/alistair/tags/pull-riscv-to-apply-20201217-1' into staging (2020-12-18 11:12:35 +0000)
>
> are available in the Git repository at:
>
>   https://github.com/marcel-apf/qemu tags/rdma-pull-request
>
> for you to fetch changes up to eed31bc5e2e9cc68626d51e7a10914dc52c370f8:
>
>   contrib/rdmacm-mux: Fix error condition in hash_tbl_search_fd_by_ifid() (2020-12-18 20:15:42 +0200)
>
> ----------------------------------------------------------------
> RDMA queue
>
> *  bug fix in contrib/rdmacm-mux
>


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.

-- PMM


  parent reply	other threads:[~2021-01-01 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 19:00 [Qemu-devel] [PULL 0/1] RDMA queue Marcel Apfelbaum
2020-12-18 19:00 ` [Qemu-devel] [PULL 1/1] contrib/rdmacm-mux: Fix error condition in hash_tbl_search_fd_by_ifid() Marcel Apfelbaum
2021-01-01 14:32 ` Peter Maydell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-02 19:18 [Qemu-devel] [PULL 0/1] RDMA queue Marcel Apfelbaum
2020-05-03 14:03 ` Peter Maydell

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='CAFEAcA_4VnP8KSy-Z_OsVsue=81+SFNf6N_2cRHXe3LaY-+tiQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.chen@huawei.com \
    --cc=euler.robot@huawei.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yuval.shaia.ml@gmail.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).