All of lore.kernel.org
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Asus N53 USB WiFi Driver porting
Date: Thu, 18 Dec 2014 13:53:02 -0500	[thread overview]
Message-ID: <5493228E.4040806@gmail.com> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A590188@SJCPEX01CL03.citrite.net>



On 2014-12-18 01:17 PM, Jeff Haran wrote:
>> -----Original Message-----
>> From: kernelnewbies-bounces+jeff.haran=citrix.com at kernelnewbies.org
>> [mailto:kernelnewbies-bounces+jeff.haran=citrix.com at kernelnewbies.org] On
>> Behalf Of nick
>> Sent: Thursday, December 18, 2014 9:50 AM
>> To: Greg KH; Abhishek Sharma
>> Cc: Valdis.Kletnieks at vt.edu; santy30 at gmail.com; Abhishek Sharma; Kernel
>> Newbies
>> Subject: Re: Asus N53 USB WiFi Driver porting
>>
>>
>>
>> On 2014-12-18 11:26 AM, Greg KH wrote:
>>> On Thu, Dec 18, 2014 at 08:18:24PM +0530, Abhishek Sharma wrote:
>>>> Hi Valdis,
>>>> Thanks for your reply.
>>>> I do not want to change kernel.
>>>
>>> "do not want to" is very different from "applications can not be
>>> ported to newer kernels".
>>>
>>> Please realize that the Linux kernel developers have spent the last
>>> decade ensuring that you should be able to update to the latest kernel
>>> version with no problems or changes needed in your applications.  Lots
>>> of companies now realize this and have no problem updating to a newer
>>> kernel, while running their old applications.
>>>
>>> So please don't spread misinformation about how applications will
>>> break with new kernel versions, that is almost always not a true statement.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>> Abhishek,
>> I am to agree with Greg KH here. The kernel community does a very good job
>> of not breaking APIs for applications or regressions. Linus also has openly stated
>> he will not accept any patches in the main line kernel tree if they break user
>> space so you should be fine. Further more to be honest I am very impressed
>> with the amount of how little APIs or regressions we get compared to the
>> amount of commits. Abhishek, in addition this seems more like you don't know
>> or are afraid of compiling the kernel over anything else. If you want post lsmod
>> output from your system so I can help teach you how to build the kernel
>> correctly.
>> Nick
> 
> If it's a custom board, bringing up new kernel versions can be a quite daunting task that the management of engineering organizations is more often than not loathe to undertake. It can take a lot of education to convince them that the pain and unpredictable development schedule hit of a kernel upgrade is more than compensated for by the increases in stability and features one gets when one goes through the process.
> 
> Jeff Haran
> 
Jeff,
You are a 100% correct. I am assuming it wasn't a custom board but if it is them, you are right it's a lot of engineering work and time.
Nick 

  reply	other threads:[~2014-12-18 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 14:20 Asus N53 USB WiFi Driver porting Abhishek Sharma
2014-12-18 14:37 ` Valdis.Kletnieks at vt.edu
2014-12-18 14:48   ` Abhishek Sharma
2014-12-18 15:40     ` Ricardo Ribalda Delgado
2014-12-18 16:26     ` Greg KH
2014-12-18 17:49       ` nick
2014-12-18 18:17         ` Jeff Haran
2014-12-18 18:53           ` nick [this message]
2014-12-18 16:24 ` Greg KH

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=5493228E.4040806@gmail.com \
    --to=xerofoify@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.