mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: x86: add missing MODULE_DESCRIPTION() macros
Date: Fri, 28 Jun 2024 16:10:30 -0700	[thread overview]
Message-ID: <75edb9c4-7fb9-4fea-9cd7-4a8565d1438e@quicinc.com> (raw)
In-Reply-To: <171961376508.228791.6632768103700293303.b4-ty@google.com>

On 6/28/2024 3:55 PM, Sean Christopherson wrote:
> On Sat, 22 Jun 2024 22:44:55 -0700, Jeff Johnson wrote:
>> Fix the following allmodconfig 'make W=1' warnings when building for x86:
>> WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/kvm/kvm.o
>> WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/kvm/kvm-intel.o
>> WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/kvm/kvm-amd.o
> 
> I split this into two commits.  The x86 changes went to `kvm-x86 misc`, and the
> generic KVM one went to `kvm-x86 generic`.  I split them partly so that I could
> opportunistically delete the VT-x comment from kvm_main.c, which was comically
> stale.
> 
> Holler if anything looks wrong.  Thanks!
> 
> [1/1] KVM: x86: add missing MODULE_DESCRIPTION() macros
>       https://github.com/kvm-x86/linux/commit/8815d77cbc99
> 
> [1/1] KVM: Add missing MODULE_DESCRIPTION()
>       https://github.com/kvm-x86/linux/commit/25bc6af60f61
> 
> --
> https://github.com/kvm-x86/linux/tree/next
LGTM, thanks!

      reply	other threads:[~2024-06-28 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23  5:44 Jeff Johnson
2024-06-28 22:55 ` Sean Christopherson
2024-06-28 23:10   ` Jeff Johnson [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-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=75edb9c4-7fb9-4fea-9cd7-4a8565d1438e@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®