All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	minios-devel@lists.xenproject.org,
	xen-devel@lists.xenproject.org, wl@xen.org
Subject: Re: [PATCH 1/2] mini-os: remove event channel specific struct file member
Date: Sun, 9 Jan 2022 07:18:12 +0100	[thread overview]
Message-ID: <f7bca511-3fa7-cbc6-5a10-5b6edb7a8bd1@suse.com> (raw)
In-Reply-To: <20220109011515.sx2qynqslxhllred@begin>


[-- Attachment #1.1.1: Type: text/plain, Size: 307 bytes --]

On 09.01.22 02:15, Samuel Thibault wrote:
> Juergen Gross, le ven. 07 janv. 2022 11:47:05 +0100, a ecrit:
>> The event channel specific union member in struct file is no longer
>> needed,
> 
> Doesn't xen/tools/libs/evtchn/minios.c use it?

Not after the Xen patches have been applied.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-01-09  6:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 10:47 [PATCH 0/2] mini-os: remove device specific struct file members Juergen Gross
2022-01-07 10:47 ` [PATCH 1/2] mini-os: remove event channel specific struct file member Juergen Gross
2022-01-09  1:15   ` Samuel Thibault
2022-01-09  6:18     ` Juergen Gross [this message]
2022-01-07 10:47 ` [PATCH 2/2] mini-os: remove gnttab specific member from struct file Juergen Gross
2022-01-07 11:30 ` [PATCH 0/2] mini-os: remove device specific struct file members Andrew Cooper
2022-01-07 11:33   ` Juergen Gross
2022-01-09  1:16 ` Samuel Thibault
2022-01-09  6:17   ` Juergen Gross
2022-01-10 11:35   ` Andrew Cooper
2022-01-10 11:41     ` Samuel Thibault

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=f7bca511-3fa7-cbc6-5a10-5b6edb7a8bd1@suse.com \
    --to=jgross@suse.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.