Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] TI DaVinci SoC updates for v4.16 (part 2)
Date: Thu, 11 Jan 2018 17:36:02 -0800	[thread overview]
Message-ID: <20180112013602.q2sm25s6o3oebkbj@localhost> (raw)
In-Reply-To: <20180110112505.13633-1-nsekhar@ti.com>

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? Might
be better to hold off a release to avoid regressions?


-Olof

  reply	other threads:[~2018-01-12  1:36 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 [this message]
2018-01-12  2:36   ` David Lechner
2018-01-12  5:47     ` Sekhar Nori
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=20180112013602.q2sm25s6o3oebkbj@localhost \
    --to=olof@lixom.net \
    --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