kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Managing kernel-updates in rpm
Date: Tue, 25 Mar 2014 09:32:11 -0400	[thread overview]
Message-ID: <40146.1395754331@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 25 Mar 2014 18:18:35 +0530." <CAK25hWPE1BbVN8ycp+i3JsBqLtyS0pDiVdK-Xtup3kKO2O3keA@mail.gmail.com>

On Tue, 25 Mar 2014 18:18:35 +0530, Saket Sinha said:

>    Its a proprietary driver so its not meant to be the part of
> mainline kernel.  :(

Hey Greg - how long did Linux carry around an entire freaking *architecture*
for the Voyager when there were only like 4 systems on the *planet* still in
existence?

> > 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?

> I am sorry but I am not allowed to do that.

If you can't do that, you *probably* can't legally ship the code to customers
either.  Just thought you should consider that...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140325/e7d1ca44/attachment.bin 

  reply	other threads:[~2014-03-25 13:32 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
2014-03-25 12:48   ` Saket Sinha
2014-03-25 13:32     ` Valdis.Kletnieks at vt.edu [this message]
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=40146.1395754331@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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).