linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Faiz Abbas <faiz_abbas@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <will@kernel.org>,
	<catalin.marinas@arm.com>, <t-kristo@ti.com>
Subject: Re: [PATCH 0/2] Enable GPIO and I2C configs for TI's J721e platform
Date: Tue, 6 Oct 2020 13:44:01 +0530	[thread overview]
Message-ID: <7c45f8e1-afc7-b386-fddb-29d44326067c@ti.com> (raw)
In-Reply-To: <20201002170211.ghzbjqt6nti6mssh@attakatha>

Nishanth,

On 02/10/20 10:32 pm, Nishanth Menon wrote:
> On 22:15-20201002, Faiz Abbas wrote:
>> The following patches enable configs in the arm64 defconfig to support
>> GPIO and I2C support on TI's J721e platform.
>>
>> Faiz Abbas (2):
>>   arm64: defconfig: Enable OMAP I2C driver
>>   arm64: defconfig: Enable DAVINCI_GPIO driver
>>
>>  arch/arm64/configs/defconfig | 2 ++
>>  1 file changed, 2 insertions(+)
> 
> 
> Could we do an audit and make sure nothing else is missing - Say ALSA /
> DRM or something else?

I'm not aware of anything that might be missing. That said, I am not
aware of every single config in every subsystem. IMO the various driver
owners should be responsible for adding their configs to defconfig.
 
> 
> And I don't really see the need to split these into individual patches,
> maybe, take a hint from [1]
> 
> 
> [1] https://lore.kernel.org/linux-arm-kernel/20200630171500.11438-1-geert+renesas@glider.be/
> 

Sounds good. I'll squash into a single patch and repost.

Thanks,
Faiz

  reply	other threads:[~2020-10-06  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 16:45 [PATCH 0/2] Enable GPIO and I2C configs for TI's J721e platform Faiz Abbas
2020-10-02 16:45 ` [PATCH 1/2] arm64: defconfig: Enable OMAP I2C driver Faiz Abbas
2020-10-02 16:45 ` [PATCH 2/2] arm64: defconfig: Enable DAVINCI_GPIO driver Faiz Abbas
2020-10-02 17:02 ` [PATCH 0/2] Enable GPIO and I2C configs for TI's J721e platform Nishanth Menon
2020-10-06  8:14   ` Faiz Abbas [this message]
2020-10-06 11:51 ` Tero Kristo
2020-10-06 13:03   ` Faiz Abbas
2020-10-06 13:10     ` Tero Kristo
2020-10-08  8:59       ` Faiz Abbas
2020-10-08  9:19         ` Tero Kristo
2020-10-08  9:40           ` Faiz Abbas
2020-10-08 11:06             ` Tero Kristo
2020-10-08 11:36               ` Nishanth Menon

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=7c45f8e1-afc7-b386-fddb-29d44326067c@ti.com \
    --to=faiz_abbas@ti.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=t-kristo@ti.com \
    --cc=will@kernel.org \
    /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).