Re: [PATCH v2 0/6] Update Davinci watchdog driver

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Sekhar Nori <nsekhar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Wim Van Sebroeck <wim@iguana.be>,
	<linux-watchdog@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Kumar Gala <galak@kernel.crashing.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Strashko Grygorii <grygorii.strashko@ti.com>
Subject: Re: [PATCH v2 0/6] Update Davinci watchdog driver
Date: Mon, 25 Nov 2013 18:36:52 +0530	[thread overview]
Message-ID: <52934B6C.4060308@ti.com> (raw)
In-Reply-To: <1384795139-19466-1-git-send-email-ivan.khoronzhuk@ti.com>

On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
> These patches are intended to update Davinci watchdog to use WDT core
> and reuse driver for keystone arch, because Keystone uses the similar
> IP like Davinci.

This series causes a regression on all DaVinci platforms because after
the series is applied the watchdog device does not get registered at
all. Since you changed the device name please include a patch to fix the
platform references too.

Thanks,
Sekhar

WARNING: multiple messages have this Message-ID (diff)

From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] Update Davinci watchdog driver
Date: Mon, 25 Nov 2013 18:36:52 +0530	[thread overview]
Message-ID: <52934B6C.4060308@ti.com> (raw)
In-Reply-To: <1384795139-19466-1-git-send-email-ivan.khoronzhuk@ti.com>

On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
> These patches are intended to update Davinci watchdog to use WDT core
> and reuse driver for keystone arch, because Keystone uses the similar
> IP like Davinci.

This series causes a regression on all DaVinci platforms because after
the series is applied the watchdog device does not get registered at
all. Since you changed the device name please include a patch to fix the
platform references too.

Thanks,
Sekhar

WARNING: multiple messages have this Message-ID (diff)

From: Sekhar Nori <nsekhar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	Strashko Grygorii <grygorii.strashko@ti.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@kernel.crashing.org>,
	Rob Herring <rob.herring@calxeda.com>,
	linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] Update Davinci watchdog driver
Date: Mon, 25 Nov 2013 18:36:52 +0530	[thread overview]
Message-ID: <52934B6C.4060308@ti.com> (raw)
In-Reply-To: <1384795139-19466-1-git-send-email-ivan.khoronzhuk@ti.com>

On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
> These patches are intended to update Davinci watchdog to use WDT core
> and reuse driver for keystone arch, because Keystone uses the similar
> IP like Davinci.

This series causes a regression on all DaVinci platforms because after
the series is applied the watchdog device does not get registered at
all. Since you changed the device name please include a patch to fix the
platform references too.

Thanks,
Sekhar

next prev parent reply	other threads:[~2013-11-25 13:08 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 17:18 [PATCH v2 0/6] Update Davinci watchdog driver Ivan Khoronzhuk
2013-11-18 17:18 ` Ivan Khoronzhuk
2013-11-18 17:18 ` Ivan Khoronzhuk
2013-11-18 17:18 ` [PATCH 1/6] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-19  5:12   ` Guenter Roeck
2013-11-19  5:12     ` Guenter Roeck
2013-11-19  5:12     ` Guenter Roeck
2013-11-19 16:17     ` Grygorii Strashko
2013-11-19 16:17       ` Grygorii Strashko
2013-11-19 16:17       ` Grygorii Strashko
2013-11-25 11:56   ` Sekhar Nori
2013-11-25 11:56     ` Sekhar Nori
2013-11-25 11:56     ` Sekhar Nori
2013-11-25 12:06     ` ivan.khoronzhuk
2013-11-25 12:06       ` ivan.khoronzhuk
2013-11-25 12:06       ` ivan.khoronzhuk
2013-11-18 17:18 ` [PATCH 2/6] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18 ` [PATCH 3/6] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-19  5:14   ` Guenter Roeck
2013-11-19  5:14     ` Guenter Roeck
2013-11-19  5:14     ` Guenter Roeck
2013-11-18 17:18 ` [PATCH 4/6] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-19  5:15   ` Guenter Roeck
2013-11-19  5:15     ` Guenter Roeck
2013-11-18 17:18 ` [PATCH 5/6] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-19  5:16   ` Guenter Roeck
2013-11-19  5:16     ` Guenter Roeck
2013-11-18 17:18 ` [PATCH 6/6] arm: dts: keystone: add watchdog entry Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-18 17:18   ` Ivan Khoronzhuk
2013-11-25 13:06 ` Sekhar Nori [this message]
2013-11-25 13:06   ` [PATCH v2 0/6] Update Davinci watchdog driver Sekhar Nori
2013-11-25 13:06   ` Sekhar Nori
2013-11-25 13:19   ` ivan.khoronzhuk
2013-11-25 13:19     ` ivan.khoronzhuk
2013-11-25 13:19     ` ivan.khoronzhuk
2013-11-25 16:44     ` ivan.khoronzhuk
2013-11-25 16:44       ` ivan.khoronzhuk
2013-11-25 16:44       ` ivan.khoronzhuk

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=52934B6C.4060308@ti.com \
    --to=nsekhar@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@kernel.crashing.org \
    --cc=grant.likely@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ivan.khoronzhuk@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=swarren@wwwdotorg.org \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.