Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] TI DaVinci SoC updates for v4.16 (part 2)
Date: Fri, 12 Jan 2018 11:17:36 +0530	[thread overview]
Message-ID: <8a0bd7f2-c3a9-1322-a567-7a9ffdaf69d8@ti.com> (raw)
In-Reply-To: <db68cbec-a3e2-9c9e-e09c-f3d9a9972636@lechnology.com>

Hi Olof,

On Friday 12 January 2018 08:06 AM, David Lechner wrote:
> On 01/11/2018 07:36 PM, Olof Johansson wrote:
>> On Wed, Jan 10, 2018 at 04:55:05PM +0530, Sekhar Nori wrote:
>>> The following changes since commit
>>> 23bbeaef90ab7607d03428bbb708efe44f43c761:
>>>
>>> ?? ARM: davinci: constify gpio_led (2018-01-05 19:28:41 +0530)
>>>
>>> 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-p2
>>>
>>> for you to fetch changes up to 0808d3260456aaba061fe06ead31d578c8bdc936:
>>>
>>> ?? ARM: davinci: remove watchdog reset (2018-01-10 14:38:07 +0530)
>>>
>>> ----------------------------------------------------------------
>>> A patch to shift to using watchdog timer for DaVinci restart
>>> functionality.
>>> The driver support is present in linux-next as 71d1f058844d "watchdog:
>>> davinci_wdt: add restart function"
>>
>> Hi,
>>
>> So if this is merged before the driver is merged, what happens?
> 
> Then reboot hangs.

Yes. I did request[1] an immutable branch with just the driver change
applied, but looks like the message was lost and the current driver
change is applied over many other watchdog changes.

> 
>> Might
>> be better to hold off a release to avoid regressions?

The main reason I sent it out anyway is because this cleanup is a
dependency to move to common clock framework and I want to reduce those
to a minimum to have a good chance of migrating to it in v4.17.

If the watchdog driver change never makes it (very low chance), then I
can resend a revert for -rc2. If ARM-SoC is merged before watchdog, yes,
during a short while in merge window reboot will be broken. But I
figured its a risk worth taking to have a chance of getting this into v4.16.

If you have a "send these late" branch, it will be nice to put it in
there. If this is too much uncertainty, then okay, lets hold for v4.17.

Thanks,
Sekhar

[1] https://www.spinics.net/lists/linux-watchdog/msg12965.html

  reply	other threads:[~2018-01-12  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 11:25 [GIT PULL] TI DaVinci SoC updates for v4.16 (part 2) Sekhar Nori
2018-01-12  1:36 ` Olof Johansson
2018-01-12  2:36   ` David Lechner
2018-01-12  5:47     ` Sekhar Nori [this message]
2018-01-12 18:14       ` Olof Johansson
2018-01-16  7:40         ` Sekhar Nori

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=8a0bd7f2-c3a9-1322-a567-7a9ffdaf69d8@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