From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.groups.io with SMTP id smtpd.web11.7546.1608209581406889189 for ; Thu, 17 Dec 2020 04:53:01 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=a+ypekxG; spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1608209580; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YGu4LBPqJ/eIJpNkIkVDJjssdZFg3JH/UT7B4hjPsvA=; b=a+ypekxGeL8KtrVIWQS3laMC6nzbf9TbZBAFEkVMNzTVToKxKWswluRqN4e9mcwL7rxesK 7YudR6Gfq1RFjggfcma3os44PqACfx1yaHhwm27i6HH3eKwc9/u2TTqjwl4AiUz19LCNzN dMF393PF18ozZ0hZrDwEYSGYjUIjI+Q= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-390-8YO-EOqAPkeO0sYMe-VZjw-1; Thu, 17 Dec 2020 07:52:57 -0500 X-MC-Unique: 8YO-EOqAPkeO0sYMe-VZjw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0DD29800D62; Thu, 17 Dec 2020 12:52:56 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-115-40.ams2.redhat.com [10.36.115.40]) by smtp.corp.redhat.com (Postfix) with ESMTP id 42658100238C; Thu, 17 Dec 2020 12:52:55 +0000 (UTC) Subject: Re: [EXTERNAL] [edk2-devel] [PATCH] Ovmf: Set matching PCI routing values in PIIX4 To: David Woodhouse , hborghor@amazon.de Cc: devel@edk2.groups.io References: <5730ec22e8ee60485046e40c131f61712ad81206.camel@amazon.com> <42861c7d416632baaea3de29ca73b7412140a0bd.camel@infradead.org> From: "Laszlo Ersek" Message-ID: <5bae8734-cbdc-67dc-5502-c0f39c5b62e1@redhat.com> Date: Thu, 17 Dec 2020 13:52:54 +0100 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 12/15/20 00:48, David Woodhouse wrote: > On Mon, 2020-12-14 at 19:58 +0100, Laszlo Ersek wrote: >> Mail-archive.com used to be a good secondary archive, with threading and >> message-id-based search; but it stopped getting a feed for some reason, >> and I failed to rectify it (I reached out to multiple people and nobody >> responded). >> >> I also run a secondary archive at >> >> https://www.redhat.com/archives/edk2-devel-archive/ >> >> but it doesn't go back beyond "2019-April", plus it doesn't have >> msgid-based search. But, at least, it's mailman2 :) > > Some years ago I fixed Mailman's web archives to contain mailto: links > with a proper &in-reply-to= in the URI, such that using it to reply got > the threading right. > > Your archive doesn't seem to have the links at all though. TBH I'm happy this facility still exists at RH at all (i.e. that we can request and run our own mailing lists) :) > I seem to recall this is only necessary because groups.io does > something weird and *mangles* the Message-ID so that the one we receive > directly is different and all the threading is screwed anyway? No, the threading is generally OK. Groups.io has a profile-level option that basically means I have a gmail.com account, which forcefully de-duplicates messages, but I really want two separate copies of what *I* send to the list, so please falsify the message-id's on my messages delivered back to me. The option is not called exactly that, of course. So yes, it can break threading for the affected person, but it's not the general case. So anyway, I run this secondary archive because the 01.org admins had killed the original list archive that used to live their, despite their express promise. The archive was deleted in two stages actually; first they just replaced Mailman2 with Mailman3, which broke all the links of course, but then they removed the edk2-devel archive altogether. > >> Regarding the R-b, thanks for that; I've just asked for a v2 -- the code >> is correct IMO, but I'd like to receive a more extensive commit message, >> plus some extra comments in the code. > > Ack. > Thanks! Laszlo