lkml.org 
[lkml]   [2022]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v1 1/1] misc: bcm-vk: add kconfig for supporting viper chip
From

Greg,

Please see inlined.

On 2/22/22 09:13, Greg Kroah-Hartman wrote:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
>
> http://daringfireball.net/2007/07/on_top
>
> On Tue, Feb 22, 2022 at 07:41:04AM -0800, Desmond Yan (APD) wrote:
>> Greg,
>>
>> This is to allow the customer to use their own driver, by default,
>> which is their preferred option.
>
> We do not care about out-of-tree code, and do not add Kconfig options
> just for that, sorry.
>
> Why not just add the out-of-tree driver here to the in-kernel code?
> What is preventing that from happening today?

Using the bcm_vk driver for viper is only for proof-of-concept, and is
not aimed to be deployed for production. In parallel, customer is
developing their own production-ready driver and would probably upstream
it whenever the appropriate time comes.

thx.

des
>
> thanks,
>
> greg k-h
[unhandled content-type:application/pkcs7-signature]
\
 
 \ /
  Last update: 2022-02-23 06:15    [W:0.052 / U:1.828 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site