All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: "manish.mishra" <manish.mishra@nutanix.com>
Cc: qemu-devel@nongnu.org,  dgilbert@redhat.com,  lsoaresp@redhat.com
Subject: Re: [PATCH v6 0/2] check magic value for deciding the mapping of channels
Date: Wed, 01 Feb 2023 16:00:30 +0100	[thread overview]
Message-ID: <87tu05zb01.fsf@secure.mitica> (raw)
In-Reply-To: <f1f1cd0f-a887-57f9-5762-7f7e638941eb@nutanix.com> (manish mishra's message of "Wed, 4 Jan 2023 16:22:10 +0530")

"manish.mishra" <manish.mishra@nutanix.com> wrote:
> Hi Everyone,
>
> I was just checking if it was not missed in holidays and was received. :)

Queued.

Sorry for the delay.



  reply	other threads:[~2023-02-01 15:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 18:44 [PATCH v6 0/2] check magic value for deciding the mapping of channels manish.mishra
2022-12-20 18:44 ` [PATCH v6 1/2] io: Add support for MSG_PEEK for socket channel manish.mishra
2023-02-01 14:55   ` Juan Quintela
2023-02-02 12:22   ` Juan Quintela
2023-02-02 12:31     ` Daniel P. Berrangé
2023-02-02 12:51       ` Juan Quintela
2023-02-02 13:13         ` Daniel P. Berrangé
2023-02-02 13:39           ` Juan Quintela
2023-02-02 13:55             ` Daniel P. Berrangé
2023-02-02 15:51               ` Juan Quintela
2022-12-20 18:44 ` [PATCH v6 2/2] migration: check magic value for deciding the mapping of channels manish.mishra
2023-02-01 14:56   ` Juan Quintela
2023-01-04 10:52 ` [PATCH v6 0/2] " manish.mishra
2023-02-01 15:00   ` Juan Quintela [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-20 18:36 manish.mishra
2023-01-31 14:59 ` manish.mishra
2023-01-31 15:17   ` Peter Xu
2023-01-31 17:45     ` manish.mishra

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=87tu05zb01.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lsoaresp@redhat.com \
    --cc=manish.mishra@nutanix.com \
    --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 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.