From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.com>,
Thierry Reding <thierry.reding@gmail.com>,
<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, Jeff Brasen <jbrasen@nvidia.com>
Subject: Re: [PATCH] serial: 8250_tegra: Create Tegra specific 8250 driver
Date: Tue, 21 Jan 2020 15:46:22 +0000 [thread overview]
Message-ID: <398367ec-be5b-417f-ce31-bfbe7c17c139@nvidia.com> (raw)
In-Reply-To: <20200121154102.GA588392@kroah.com>
On 21/01/2020 15:41, Greg Kroah-Hartman wrote:
> On Mon, Jan 20, 2020 at 04:01:49PM +0000, Jon Hunter wrote:
>> diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
>> index f16824bbb573..432b47647677 100644
>> --- a/drivers/tty/serial/8250/Kconfig
>> +++ b/drivers/tty/serial/8250/Kconfig
>> @@ -500,6 +500,15 @@ config SERIAL_8250_PXA
>> applicable to both devicetree and legacy boards, and early console is
>> part of its support.
>>
>> +config SERIAL_8250_TEGRA
>> + tristate "8250 support for Tegra serial ports"
>> + default SERIAL_8250
>> + depends on SERIAL_8250
>> + depends on ARCH_TEGRA
>
> No COMPILE_TEST support so we can make sure we don't break the thing
> somehow?
Good point. Will add.
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2020-01-21 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 16:01 [PATCH] serial: 8250_tegra: Create Tegra specific 8250 driver Jon Hunter
2020-01-21 15:41 ` Greg Kroah-Hartman
2020-01-21 15:46 ` Jon Hunter [this message]
2020-01-21 16:31 ` Dmitry Osipenko
2020-01-21 16:37 ` Dmitry Osipenko
2020-01-21 18:34 ` Jon Hunter
2020-01-21 18:46 ` Dmitry Osipenko
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=398367ec-be5b-417f-ce31-bfbe7c17c139@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrasen@nvidia.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).