From: Igor Mammedov <imammedo@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3 2/3] hw/smbios: fix table memory corruption with large memory vms
Date: Mon, 21 Feb 2022 08:12:09 +0100 [thread overview]
Message-ID: <20220221081209.4e12db9a@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202171900100.294420@anisinha-lenovo>
On Thu, 17 Feb 2022 19:02:05 +0530 (IST)
Ani Sinha <ani@anisinha.ca> wrote:
> On Thu, 17 Feb 2022, Igor Mammedov wrote:
>
> > On Mon, 14 Feb 2022 19:42:35 +0530
>
> > >
> > > Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=2023977
> > s/buglink/Resolves/
> >
>
> OK I am curious about this one.
>
> Per https://www.qemu.org/docs/master/devel/submitting-a-patch.html ,
>
> If your patch fixes a bug in the gitlab bug tracker, please add a line
> with “Resolves: <URL-of-the-bug>” to the commit message, too. Gitlab can
> close bugs automatically once commits with the “Resolved:” keyword get
> merged into the master branch of the project. And if your patch addresses
> a bug in another public bug tracker, you can also use a line with
> “Buglink: <URL-of-the-bug>” for reference here, too.
>
> So I considered redhar BZ as a public bug tracker as well. Does the BZ
> also automatically close bugs when we use "Resolves:"? Should we update
> the instructions here?
I might have been wrong suggesting "Resolves" tag, it will/should not affect bugzilla.
Looking at history, shows a zoo of used tags in bugzilla case,
so I'd guess Buglink is fine as any other.
next prev parent reply other threads:[~2022-02-21 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 14:12 [PATCH v3 0/3] hw/smbios: fix table memory corruption with large memory vms Ani Sinha
2022-02-14 14:12 ` [PATCH v3 1/3] hw/smbios: code cleanup - use macro definitions for table header handles Ani Sinha
2022-02-14 14:12 ` [PATCH v3 2/3] hw/smbios: fix table memory corruption with large memory vms Ani Sinha
2022-02-17 8:54 ` Igor Mammedov
2022-02-17 13:32 ` Ani Sinha
2022-02-21 7:12 ` Igor Mammedov [this message]
2022-02-14 14:12 ` [PATCH v3 3/3] hw/smbios: add assertion to ensure handles of tables 19 and 32 do not collide Ani Sinha
2022-02-17 8:56 ` Igor Mammedov
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=20220221081209.4e12db9a@redhat.com \
--to=imammedo@redhat.com \
--cc=ani@anisinha.ca \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).