All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, michal.orzel@amd.com,
	xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
	consulting@bugseng.com, andrew.cooper3@citrix.com,
	roger.pau@citrix.com, Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [XEN PATCH 2/6] x86/setup: add missing headers
Date: Mon, 14 Aug 2023 09:43:53 +0200	[thread overview]
Message-ID: <a881f91d78befa8ee8b61101eeb65913@bugseng.com> (raw)
In-Reply-To: <e621f307-f83c-044a-cd9b-6592f452454f@suse.com>


>>> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>>> Fixes: 3eab82196b02 ("x86: PIT broadcast to fix local APIC timer stop 
>>> issue for Deep C state")
>>> Fixes: 63dc135aeaf9 ("x86: invpcid support")
> 
> One request: Please can you get used to putting the Fixes: tags first,
> so one doesn't need to (try to) remember to move them in the course of
> committing?
> 

Sure. Sorry, I didn't notice the ordering in other commits.

-- 
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)


  reply	other threads:[~2023-08-14  7:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  7:19 [XEN PATCH 0/6] xen: fix missing headers and static storage duration Nicola Vetrini
2023-08-11  7:19 ` [XEN PATCH 1/6] x86/hpet: make variable 'per_cpu__cpu_bc_channel' static Nicola Vetrini
2023-08-11 22:54   ` Stefano Stabellini
2023-08-11 22:55     ` Stefano Stabellini
2023-08-14  7:34     ` Jan Beulich
2023-08-11  7:19 ` [XEN PATCH 2/6] x86/setup: add missing headers Nicola Vetrini
2023-08-11 22:58   ` Stefano Stabellini
2023-08-14  7:38     ` Jan Beulich
2023-08-14  7:43       ` Nicola Vetrini [this message]
2023-08-11  7:19 ` [XEN PATCH 3/6] x86/vm_event: add missing include Nicola Vetrini
2023-08-11 23:01   ` Stefano Stabellini
2023-08-12  9:53     ` Nicola Vetrini
2023-08-12 11:37       ` Julien Grall
2023-08-14  7:16         ` Jan Beulich
2023-08-14  7:39   ` Jan Beulich
2023-08-14 10:33     ` Nicola Vetrini
2023-08-14 11:01       ` Julien Grall
2023-08-14 12:53         ` Nicola Vetrini
2023-08-14 13:06           ` Julien Grall
2023-08-14 13:31             ` Jan Beulich
2023-08-14 13:47               ` Julien Grall
2023-08-14 12:57   ` Nicola Vetrini
2023-08-11  7:19 ` [XEN PATCH 4/6] cpufreq: add missing include of header 'pmstat.h' Nicola Vetrini
2023-08-11 23:03   ` Stefano Stabellini
2023-08-14  7:41     ` Jan Beulich
2023-08-11  7:19 ` [XEN PATCH 5/6] vpic/msix: make 'get_slot' static Nicola Vetrini
2023-08-11 23:03   ` Stefano Stabellini
2023-08-14  7:44   ` Jan Beulich
2023-08-14  7:54     ` Nicola Vetrini
2023-08-11  7:19 ` [XEN PATCH 6/6] drivers/video: make declarations of defined functions available Nicola Vetrini
2023-08-11 23:09   ` Stefano Stabellini
2023-08-14  7:47   ` Jan Beulich
2023-08-14  7:56     ` Nicola Vetrini
2023-08-14  8:12       ` Jan Beulich
2023-08-14  9:28         ` Nicola Vetrini

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=a881f91d78befa8ee8b61101eeb65913@bugseng.com \
    --to=nicola.vetrini@bugseng.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ayan.kumar.halder@amd.com \
    --cc=consulting@bugseng.com \
    --cc=jbeulich@suse.com \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xenia.ragiadakou@amd.com \
    /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.