Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: <santosh.shilimkar@oracle.com>
Cc: Tero Kristo <t-kristo@ti.com>,
	Yuti Amonkar <yamonkar@cadence.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Swapnil Jakhade <sjakhade@cadence.com>,
	Sekhar Nori <nsekhar@ti.com>,
	linux-kernel@vger.kernel.org, Jyri Sarha <jsarha@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs
Date: Thu, 12 Nov 2020 20:47:10 -0600	[thread overview]
Message-ID: <20201113024710.kinhetju4iumhpq4@anaerobic> (raw)
In-Reply-To: <4b23cb5b-b1c9-34b9-2bdf-4f9c2df9ad0d@oracle.com>

On 13:59-20201112, santosh.shilimkar@oracle.com wrote:
[...]
> > 
> 
> I can apply SOC kconfig patch [1] to my soc branch. That branch with
> some additional patches am going to send up, so it should
> work. Let me know.

I think that should work, thanks.
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-11-13  2:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 17:06 [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs Nishanth Menon
2020-10-26 18:00 ` Lokesh Vutla
2020-10-26 19:08   ` Nishanth Menon
2020-10-27 15:59     ` Lokesh Vutla
2020-10-27 16:23       ` Nishanth Menon
2020-11-12 21:56     ` Nishanth Menon
2020-11-12 21:59       ` santosh.shilimkar
2020-11-12 22:22         ` Nishanth Menon
2020-11-13  1:13           ` santosh.shilimkar
2020-11-13  2:47         ` Nishanth Menon [this message]

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=20201113024710.kinhetju4iumhpq4@anaerobic \
    --to=nm@ti.com \
    --cc=jsarha@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nsekhar@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=santosh.shilimkar@oracle.com \
    --cc=sjakhade@cadence.com \
    --cc=ssantosh@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=yamonkar@cadence.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