public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Marciniszyn <mike.marciniszyn@intel.com>
To: mmarek@suse.cz
Cc: Doug Ledford <dledford@redhat.com>,
	linux-kbuild@vger.kernel.org, mmarcini@yahoo.com
Subject: [PATCH 0/3] RPM enhancements for kbuild
Date: Mon, 24 Jun 2013 10:38:17 -0400	[thread overview]
Message-ID: <20130624143658.10761.3787.stgit@phlsvslse11.ph.intel.com> (raw)

This series of patches enhances the kernel RPM mechanism
as follows:
- executes /sbin/installkernel in a %post
- installs the firmware into a KERNELRELEASE specific directory
- adds a kernel-devel package

The installkernel allows for booting the target server
after the RPM has been installed.  A "make install" would
have done that.

The unique firmware directory avoids conflicts with distribution
firmware rpm's as recommended by Doug Ledford.

The kernel-devel package allows for external module builds
against the kernel.  A "make modules" install would have
supported such a build on a single server. The capability is lost
through the rpm mechanism because the build server source
directory is no longer appropriate for the target server.

---

Mike Marciniszyn (3):
      kbuild: add %post section to create initramfs and grub hooks
      kbuilld: install firmware files in kernel relative directory
      kbuild: add generation of kernel-devel


 scripts/package/mkspec |   44 ++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 40 insertions(+), 4 deletions(-)

-- 
Mike

             reply	other threads:[~2013-06-24 14:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 14:38 Mike Marciniszyn [this message]
2013-06-24 14:38 ` [PATCH 1/3] kbuild: add %post section to create initramfs and grub hooks Mike Marciniszyn
2013-07-23 13:19   ` Michal Marek
2013-06-24 14:38 ` [PATCH 2/3] kbuilld: install firmware files in kernel relative directory Mike Marciniszyn
2013-07-23 13:19   ` Michal Marek
2013-06-24 14:38 ` [PATCH 3/3] kbuild: add generation of kernel-devel Mike Marciniszyn
2013-07-04 15:15   ` Michal Marek
2013-07-05 13:04     ` Marciniszyn, Mike
2013-07-05 20:29       ` Michal Marek
2013-07-05 13:12     ` Marciniszyn, Mike
2013-07-05 13:17     ` Marciniszyn, Mike
2013-07-05 20:30       ` Michal Marek
2013-07-08 11:55     ` Marciniszyn, Mike
2013-07-08 12:12       ` Michal Marek
2013-07-08 13:15         ` Marciniszyn, Mike
2013-07-08 13:32           ` Doug Ledford
2013-07-08 13:39             ` Marciniszyn, Mike
2013-07-08 14:45               ` Michal Marek
2013-07-08 15:52                 ` Marciniszyn, Mike
2013-07-08 16:20                 ` Doug Ledford
2013-07-08 17:17                   ` Marciniszyn, Mike

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=20130624143658.10761.3787.stgit@phlsvslse11.ph.intel.com \
    --to=mike.marciniszyn@intel.com \
    --cc=dledford@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarcini@yahoo.com \
    --cc=mmarek@suse.cz \
    /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