[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <534605ef-aeb1-b0a2-2326-be6faba4709c@broadcom.com>
Date: Tue, 22 Feb 2022 21:14:02 -0800
From: Desmond yan <desmond.yan@...adcom.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Scott Branden <scott.branden@...adcom.com>,
Arnd Bergmann <arnd@...db.de>,
bcm-kernel-feedback-list@...adcom.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] misc: bcm-vk: add kconfig for supporting viper
chip
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
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4206 bytes)
Powered by blists - more mailing lists