From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Avi Kivity <avi@redhat.com>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: [PATCH] KVM: add localversion to avoid confusion and conflicts
Date: Fri, 29 May 2009 12:48:14 +0530 [thread overview]
Message-ID: <1243581494.3212.1.camel@localhost.localdomain> (raw)
Adding localversion avoids confusion in kernel images :
like Linux version 2.6.30-rc7 does not tell whether it is linus or kvm kernel.
By adding localversion it tells :
Linux version 2.6.30-rc7-kvm , any doubt ;-)
Secondly, by installing modules it overwrites on linus modules.
By adding localversion :
[root@hpdv5 kvm]# make modules_install
INSTALL arch/x86/kernel/cpu/cpu_debug.ko
INSTALL arch/x86/kernel/test_nx.ko
INSTALL arch/x86/kvm/kvm-amd.ko
INSTALL arch/x86/kvm/kvm-intel.ko
INSTALL arch/x86/kvm/kvm.ko
INSTALL arch/x86/oprofile/oprofile.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL drivers/virtio/virtio.ko
INSTALL drivers/virtio/virtio_balloon.ko
INSTALL drivers/virtio/virtio_pci.ko
INSTALL drivers/virtio/virtio_ring.ko
DEPMOD 2.6.30-rc7-kvm
I am inspired by Ingo's -tip, I am sure Ingo will tell more advantages,
if these are not enough :-)
Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
---
localversion-kvm | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 localversion-kvm
diff --git a/localversion-kvm b/localversion-kvm
new file mode 100644
index 0000000..d969ff0
--- /dev/null
+++ b/localversion-kvm
@@ -0,0 +1 @@
+-kvm
--
1.6.0.6
next reply other threads:[~2009-05-29 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:18 Jaswinder Singh Rajput [this message]
2009-05-29 7:48 ` [PATCH] KVM: add localversion to avoid confusion and conflicts Christian Bornträger
2009-05-29 8:43 ` Jaswinder Singh Rajput
2009-05-29 9:29 ` Christian Bornträger
2009-06-01 19:26 ` Steven Rostedt
2009-06-01 19:48 ` Avi Kivity
2009-06-01 19:53 ` Steven Rostedt
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=1243581494.3212.1.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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