public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Charulatha Varadarajan <charu@ti.com>
Subject: Re: [PATCH 3/3] OMAP: wd_timer: remove old, dead probing code
Date: Tue, 16 Nov 2010 15:47:59 +0300	[thread overview]
Message-ID: <4CE27D7F.1030107@ru.mvista.com> (raw)
In-Reply-To: <20101116102518.27991.38133.stgit@twilight.localdomain>

Hello.

On 16-11-2010 13:25, Paul Walmsley wrote:

> After commit f2ce62312650211f6cf665cd6dc519c334c4071e, watchdog

    Linus has asked to also specify the commit summary in parens...

> probing is handled by files in mach-omap1/ and mach-omap2/, and the
> plat-omap/devices.c probing code is no longer used.  Remove the dead
> code in plat-omap/devices.c.

> Signed-off-by: Paul Walmsley<paul@pwsan.com>
> Cc: Charulatha Varadarajan<charu@ti.com>

WBR, Sergei

  reply	other threads:[~2010-11-16 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 10:25 [PATCH 0/3] OMAP: wd_timer: update integration code to use new hwmod changes Paul Walmsley
2010-11-16 10:25 ` [PATCH 1/3] OMAP2+: wd_timer: separate watchdog disable code from the rest of mach-omap2/devices.c Paul Walmsley
2010-11-22 11:07   ` DebBarma, Tarun Kanti
2010-11-16 10:25 ` [PATCH 2/3] OMAP2+: wd_timer: disable on boot via hwmod postsetup mechanism Paul Walmsley
2010-11-16 10:25 ` [PATCH 3/3] OMAP: wd_timer: remove old, dead probing code Paul Walmsley
2010-11-16 12:47   ` Sergei Shtylyov [this message]
2010-11-16 16:29     ` Paul Walmsley
2010-12-21 22:30   ` Paul Walmsley
2010-11-16 10:37 ` [PATCH 0/3] OMAP: wd_timer: update integration code to use new hwmod changes Varadarajan, Charulatha
2010-11-16 16:48 ` Paul Walmsley

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=4CE27D7F.1030107@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=charu@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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