Re: [PATCH v1 1/1] misc: bcm-vk: add kconfig for supporting viper chip

[Desmond yan <desmond.yan@broadcom.com>]

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]


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

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]