All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
	xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
	consulting@bugseng.com, xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH 3/6] x86/vm_event: add missing include
Date: Mon, 14 Aug 2023 12:33:51 +0200	[thread overview]
Message-ID: <808999f0142825bebfdbe16a309d529f@bugseng.com> (raw)
In-Reply-To: <30d1ef98-d847-b0ca-6771-4bc0abcdb214@suse.com>

On 14/08/2023 09:39, Jan Beulich wrote:
> On 11.08.2023 09:19, Nicola Vetrini wrote:
>> The missing header included by this patch provides declarations for
>> the functions 
>> 'vm_event_{fill_regs,set_registers,monitor_next_interrupt}'
>> that are defined in the source file. This also resolves violations
>> of MISRA C:2012 Rule 8.4.
>> 
>> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>> Fixes: adc75eba8b15 ("x86/vm_event: consolidate hvm_event_fill_regs 
>> and p2m_vm_event_fill_regs")
>> Fixes: 975efd3baa8d ("introduce VM_EVENT_FLAG_SET_REGISTERS")
>> Fixes: 9864841914c2 ("x86/vm_event: add support for 
>> VM_EVENT_REASON_INTERRUPT")
> 
> It's hard to see how it can be three commit here. The oldest one is at
> fault, I would say.

Since the patch is concerned with more than one function then in a sense 
I agree
with you (the headers should have been included in the proper way the 
first time around), but
then more definitions have been added by adc75eba8b15 and 9864841914c2, 
and these should have
triggered a refactoring too. I can leave just 975efd3baa8d in the Fixes 
if the preferred way is to list just the first problematic commit 
(perhaps with a little explanation after --- ).

> 
> Also please remember to Cc maintainers.

Yes, sorry. I must have forgotten to run add_maintainers.

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


  reply	other threads:[~2023-08-14 10:34 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
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 [this message]
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=808999f0142825bebfdbe16a309d529f@bugseng.com \
    --to=nicola.vetrini@bugseng.com \
    --cc=ayan.kumar.halder@amd.com \
    --cc=consulting@bugseng.com \
    --cc=jbeulich@suse.com \
    --cc=michal.orzel@amd.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.