From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Managing kernel-updates in rpm
Date: Tue, 25 Mar 2014 05:42:13 -0700 [thread overview]
Message-ID: <20140325124213.GA4377@kroah.com> (raw)
In-Reply-To: <CAK25hWOBJSizJQw4O3C1sVi4fiy_=pptcfNVYw0=ohrcZWZBYA@mail.gmail.com>
On Tue, Mar 25, 2014 at 12:54:12PM +0530, Saket Sinha wrote:
> Hi,
>
> We have a rpm which installs a linux kernel driver. Now this
> driver has some kernel-level dependencies especially Development Tools
> (kernel-headers etc) such that they depend on running kernel version.
I'd ask you first off, why is your kernel driver not merged upstream
with the main kernel.org releases, to prevent any of these issues from
ever happening?
Do you have a pointer to your driver somewhere so we can look at it to
determine what is needed to be done to get it merged properly?
thanks,
greg k-h
next prev parent reply other threads:[~2014-03-25 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 7:24 Managing kernel-updates in rpm Saket Sinha
2014-03-25 8:39 ` parinay
2014-03-25 9:02 ` Saket Sinha
2014-03-25 12:42 ` Greg KH [this message]
2014-03-25 12:48 ` Saket Sinha
2014-03-25 13:32 ` Valdis.Kletnieks at vt.edu
2014-03-25 14:07 ` Greg KH
2014-03-25 14:06 ` Greg KH
2014-03-25 13:27 ` Valdis.Kletnieks at vt.edu
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=20140325124213.GA4377@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).