All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>,
	qemu-devel@nongnu.org, Adam Williamson <awilliam@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>
Subject: (Extra) KVM call for 2022-10-25
Date: Mon, 24 Oct 2022 19:48:29 +0200	[thread overview]
Message-ID: <87a65l9kpe.fsf@secure.mitica> (raw)


Hi

As discussed on last week KVM call, we repeate this Tuesday to
continue talking about vfio migration. So far we need to discuss:

- My RFC series, if they are enough for vfio devices (i.e. they are able
  to get a cheap call to calculate the size of the device state)

- My (not yet s ent) way of sending data through new channels. I lost
  the calendar entry for all calls during this years.

KVM developers conference call
Tuesday 2022-10-25 ⋅ 15:00 – 16:00 Central European Time - Madrid

Location: http://bluejeans.com/quintela

If you need call details or want to be on the calendar entry, please contact me: quintela@redhat.com

url:
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=NWpzczhmMThzY29tNDJwY3I3dmEzbzE3cjcgZWdlZDdja2kwNWxtdTF0bmd2a2wzdGhpZHNAZw&tmsrc=eged7cki05lmu1tngvkl3thids%40group.calendar.google.com

Later, Juan.

PD. The conference is on: https://bluejeans.com/quintela google calendar
decides that it is a good idea to add a google link entry by
default. I think that I removed it this time (who knows).

PD2: The entry should be public, if you can't access, just let me know
     to figure it out what is going on.

PD3: No, I have no clue how to convince google calendar to let someone
     that is not logged somehow on gmail to show the entry.  I tried to
     put it public everywhere.


                 reply	other threads:[~2022-10-24 19:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87a65l9kpe.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=awilliam@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.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 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.