All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Desmond Yan (APD)" <desmond.yan@broadcom.com>
Cc: Scott Branden <scott.branden@broadcom.com>,
	Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] misc: bcm-vk: add kconfig for supporting viper chip
Date: Tue, 22 Feb 2022 18:13:13 +0100	[thread overview]
Message-ID: <YhUZqYrvNy05h86j@kroah.com> (raw)
In-Reply-To: <CAEuuh2_b-xGAux_EmBaNCGcBM7C0-Z8d_q1BBZ+LA0zpkZEunQ@mail.gmail.com>

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?

thanks,

greg k-h

  reply	other threads:[~2022-02-22 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 20:08 [PATCH v1 1/1] misc: bcm-vk: add kconfig for supporting viper chip Desmond Yan
2022-02-19  7:33 ` Greg Kroah-Hartman
2022-02-22 15:41   ` Desmond Yan (APD)
2022-02-22 17:13     ` Greg Kroah-Hartman [this message]
2022-02-23  5:14       ` Desmond yan
2022-02-23  7:26         ` Greg Kroah-Hartman
2022-02-23 17:59           ` Scott Branden
2022-02-23 18:27             ` Greg Kroah-Hartman
2022-02-23 18:29               ` Scott Branden

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=YhUZqYrvNy05h86j@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=desmond.yan@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.branden@broadcom.com \
    /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.