All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: please clean up the clockevents tree
Date: Wed, 13 May 2015 09:46:42 +0200	[thread overview]
Message-ID: <55530162.9030509@linaro.org> (raw)
In-Reply-To: <20150513151913.731a0d65@canb.auug.org.au>

On 05/13/2015 07:19 AM, Stephen Rothwell wrote:
> Hi Daniel,
>
> All the commits in the clockevents tree have appeared upstream (as
> different commits, unfortunately).  Please clean up your tree it is
> just causing unnecessary conflicts.

Hi Stephen,

I updated the branch. Let me know if everything is all right now.

Thanks.

   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2015-05-13  7:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  5:19 linux-next: please clean up the clockevents tree Stephen Rothwell
2015-05-13  7:46 ` Daniel Lezcano [this message]
2015-05-13  8:26   ` Stephen Rothwell
2017-07-10  3:30 Stephen Rothwell
2017-07-10 10:36 ` Daniel Lezcano
2017-07-10 10:55   ` Stephen Rothwell
2018-03-13 23:02 Stephen Rothwell
     [not found] ` <ce514c90-f9ec-fc9e-e205-cd822cd766b2@linaro.org>
2018-03-14  8:01   ` Stephen Rothwell
2018-12-20  5:15 Stephen Rothwell
2018-12-20  8:47 ` Daniel Lezcano
2020-02-21  0:37 Stephen Rothwell
2020-02-21  8:32 ` Daniel Lezcano
2020-02-21 11:11   ` Stephen Rothwell

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=55530162.9030509@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.