public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>
Cc: jordan.l.justen@intel.com, ard.biesheuvel@linaro.org,
	anthony.perard@citrix.com, julien.grall@arm.com,
	xen-devel@lists.xenproject.org,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [PATCH v2 0/3] Xen PCI passthrough fixes
Date: Tue, 9 Apr 2019 09:54:55 +0200	[thread overview]
Message-ID: <fb066d31-18fb-c0de-c2f2-814423664071@redhat.com> (raw)
In-Reply-To: <1554779560-26204-1-git-send-email-igor.druzhinin@citrix.com>

Hi Igor,

On 04/09/19 05:12, Igor Druzhinin wrote:
> Igor Druzhinin (3):
>   OvmfPkg/XenSupport: remove usage of prefetchable PCI host bridge
>     aperture
>   OvmfPkg/XenSupport: use a correct PCI host bridge aperture for BAR64
>   OvmfPkg/XenSupport: turn off address decoding before BAR sizing
> 
>  OvmfPkg/Library/PciHostBridgeLib/XenSupport.c | 44 ++++++++++++++++++++++-----
>  1 file changed, 37 insertions(+), 7 deletions(-)
> 

some general administrativa:

(1) the edk2-devel mailing list has moved. Please subscribe at
<https://edk2.groups.io/g/devel>, and resend the series. Apologies about
the inconvenience.

(2) By the time we push this series,
<https://bugzilla.tianocore.org/show_bug.cgi?id=1373> will have been
fixed most likely. That means that you will no longer need to add the
"Contributed-under" line to your signoffs, on all patches.

Thanks!
Laszlo

       reply	other threads:[~2019-04-09  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1554779560-26204-1-git-send-email-igor.druzhinin@citrix.com>
2019-04-09  7:54 ` Laszlo Ersek [this message]
     [not found] ` <1554779560-26204-2-git-send-email-igor.druzhinin@citrix.com>
2019-04-11 13:07   ` [PATCH v2 1/3] OvmfPkg/XenSupport: remove usage of prefetchable PCI host bridge aperture Anthony PERARD

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-list 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=fb066d31-18fb-c0de-c2f2-814423664071@redhat.com \
    --to=devel@edk2.groups.io \
    /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