linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Ladislav Michl <ladis@linux-mips.org>,
	Nathan Chancellor <natechancellor@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, YueHaibing <yuehaibing@huawei.com>,
	Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH] clocksource/drivers/timer-ti-dm: Remove omap_dm_timer_set_load_start
Date: Thu, 11 Apr 2019 13:56:57 -0700	[thread overview]
Message-ID: <20190411205657.GT2839@atomide.com> (raw)
In-Reply-To: <b8a177ee-0058-2730-4c95-56834f6bafd4@linaro.org>

Hi,

* Daniel Lezcano <daniel.lezcano@linaro.org> [190411 19:21]:
> On 10/04/2019 22:07, Tony Lindgren wrote:
> > Hi,
> > 
> > * Daniel Lezcano <daniel.lezcano@linaro.org> [190410 17:02]:
> >> can you ask for an acked-by before pulling a patch in your tree?
> > 
> > I certainly do ask and wait for acks where possible :)
> 
> Ok, I may have missed them.
> 
> > Note that I have not applied this patch. I just added
> > Keerthy to Cc on this thread so maybe you misread the
> > message earlier. My comment "seems like no other
> > takers" was for Ladislav regarding somebody picking up
> > his earlier work, not for picking up this patch :)
> 
> Actually I was referring to the commit 592ea6bd1fad. Anyway as stated
> above I could have miss your call.

Hmm so commit 592ea6bd1fad was part of the PWM timer series
that was posted several times from late 2017 to end of
February 2018. I did not get any timer related acks or
comments so I applied it together with the PWM timer
changes.

I'm guessing you may have accidentally checked out some
older deja-vu branch from about a year ago? Commit
592ea6bd1fad is not related to this fix.. :)

Regards,

Tony




  parent reply	other threads:[~2019-04-11 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  5:01 [PATCH] clocksource/drivers/timer-ti-dm: Remove omap_dm_timer_set_load_start Nathan Chancellor
2019-03-27  8:11 ` Ladislav Michl
2019-04-04 14:17   ` Tony Lindgren
2019-04-04 18:39     ` Keerthy
2019-04-10 17:01     ` Daniel Lezcano
2019-04-10 20:07       ` Tony Lindgren
2019-04-11 19:20         ` Daniel Lezcano
2019-04-11 19:36           ` Nathan Chancellor
2019-04-11 20:13             ` Daniel Lezcano
2019-04-11 20:42               ` Tony Lindgren
2019-04-11 20:25             ` Daniel Lezcano
2019-04-11 20:56           ` Tony Lindgren [this message]
2019-04-12  4:59             ` Nathan Chancellor
2019-04-12 15:40               ` Tony Lindgren

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=20190411205657.GT2839@atomide.com \
    --to=tony@atomide.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=j-keerthy@ti.com \
    --cc=ladis@linux-mips.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).