From: Laszlo Ersek <lersek@redhat.com>
To: Julien Grall <julien.grall@arm.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
xen-devel@lists.xenproject.org, jbeulich@suse.com
Cc: Gary Lin <glin@suse.com>,
Jordan Justen <jordan.l.justen@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables)
Date: Tue, 23 May 2017 18:20:14 +0200 [thread overview]
Message-ID: <5a41b0c4-2d2c-de02-16e7-23d4806d7651@redhat.com> (raw)
In-Reply-To: <6af13bb5-0bfb-c9e3-e9fe-d1361d851e7d@arm.com>
On 05/23/17 17:02, Julien Grall wrote:
> Hi,
>
> On 23/05/17 15:12, Konrad Rzeszutek Wilk wrote:
>>>> The primary location for reporting bugs against the hypervisor and
>>>> associated bundled tools [...] is by posting to the xen-devel mailing
>>>> list (list info). Please tag your subject line with a '[BUG]' prefix.
>>>> Note that you do not need to be subscribed to the list to post
>>>> (although non-subscribers are moderated this usually happens pretty
>>>> quickly) and that list policy is to CC people so you shouldn't miss
>>>> any replies.
>>>>
>>>> [...]
>>>>
>>>> Although a bugzilla instance does exist it is not well maintained or
>>>> widely used by developers. If you really want to file a bug in
>>>> bugzilla you are strongly recommended to also post to the mailing
>>>> list.
>>>
>>> This does not make things easier for us, because rather than recurrently
>>> check a simple bug status field in the Xen tracker, we'd have to be
>>> tapped into Xen development, and follow the email thread & any relevant
>>> commits closely. In reality I'm not even subscribed to xen-devel.
>
> We recently introduced a tracker ([1]) to help us following the state of
> bugs/features. It is managed by maintainers and read-only for the others.
>
> The usual process is to report the bug on the mailing-list and a
> maintainer will create a bug on the tracker if we have no immediate
> solution.
That's perfect; we'll be able to reference Xen issue reports with URLs
like (just an example) <https://xenproject.atlassian.net/browse/XEN-86>,
from TianoCore BZs. That should enable us to quickly re-check the state
of the Xen report whenever we revisit the dependent TianoCore BZ.
... Can you please add the information about "xenproject.atlassian.net"
to the Xen Wiki article at
<https://wiki.xen.org/wiki/Reporting_Bugs_against_Xen_Project>?
> In this case, the patch made rc6. So I believe the problem is resolved.
Yes, it is. Thanks!
Laszlo
> Cheers,
>
> [1] https://xenproject.atlassian.net/projects/XEN/issues
>
prev parent reply other threads:[~2017-05-23 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 19:30 [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Laszlo Ersek
2017-05-06 19:30 ` [PATCH 1/5] OvmfPkg/EmuVariableFvbRuntimeDxe: strip trailing whitespace Laszlo Ersek
2017-05-12 9:07 ` Gary Lin
2017-05-06 19:30 ` [PATCH 2/5] OvmfPkg/EmuVariableFvbRuntimeDxe: change block size to 4KB Laszlo Ersek
2017-05-12 9:07 ` Gary Lin
2017-05-15 23:50 ` Jordan Justen
2017-05-06 19:30 ` [PATCH 3/5] OvmfPkg/PlatformPei: align EmuVariableNvStore at any page boundary Laszlo Ersek
2017-05-12 9:08 ` Gary Lin
2017-05-06 19:30 ` [PATCH 4/5] OvmfPkg/README: document 4MB flash layout Laszlo Ersek
2017-05-06 19:30 ` [PATCH 5/5] OvmfPkg: make the 4MB flash size the default (again) Laszlo Ersek
2017-05-08 4:27 ` [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Gary Lin
2017-05-12 2:02 ` Gary Lin
2017-05-12 8:40 ` Laszlo Ersek
2017-05-16 0:40 ` Jordan Justen
2017-05-16 4:20 ` Gary Lin
2017-05-18 12:36 ` Laszlo Ersek
2017-05-23 14:12 ` Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: " Konrad Rzeszutek Wilk
[not found] ` <59246AD9020000780015C380@prv-mh.provo.novell.com>
2017-05-23 16:04 ` Laszlo Ersek
[not found] ` <6af13bb5-0bfb-c9e3-e9fe-d1361d851e7d@arm.com>
2017-05-23 16:20 ` Laszlo Ersek [this message]
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=5a41b0c4-2d2c-de02-16e7-23d4806d7651@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