From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] TI DaVinci SoC support updates for v4.16
Date: Fri, 5 Jan 2018 20:27:49 +0530 [thread overview]
Message-ID: <da6af385-ff4f-9bf1-8061-2853594ea114@ti.com> (raw)
In-Reply-To: <20180105070904.ckixnqva6qkbaukc@localhost>
Hi Olof,
On Friday 05 January 2018 12:39 PM, Olof Johansson wrote:
> On Sat, Dec 23, 2017 at 09:21:31PM +0530, Sekhar Nori wrote:
>> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>>
>> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v4.16/soc
>>
>> for you to fetch changes up to ed3c0c2b4fdcbe05194ee3f5e634ece3018d3b76:
>>
>> ARM: dts: da850-lcdk: Remove leading 0x and 0s from unit address (2017-12-23 15:46:25 +0530)
>>
>> ----------------------------------------------------------------
>> DaVinci SoC updates consisting of non-critical bug fixes including constifying
>> data structures, DT warning fixes for W=1 and code simplification.
>>
>> Also a defconfig update for DaVinci, enabling support for USB network adaptors.
>
> Hi,
>
> We usually don't mix DT and other updates (and sometimes we keep defconfig
> updates separate from SoC ones, but that's not needed here).
>
> Can you respin with DT separate? Feel free to just send-email the patch to us,
> or send a pull request with it if you prefer.
I sent a v2 pull request. I had two more patches that were ready to be
queued for which I was planning on sending another pull request anyway.
I added those in the v2.
Thanks,
Sekhar
prev parent reply other threads:[~2018-01-05 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 15:51 [GIT PULL] TI DaVinci SoC support updates for v4.16 Sekhar Nori
2018-01-05 7:09 ` Olof Johansson
2018-01-05 14:57 ` Sekhar Nori [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=da6af385-ff4f-9bf1-8061-2853594ea114@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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