From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org, arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] omap soc changes for v4.3
Date: Fri, 24 Jul 2015 05:08:20 -0700 [thread overview]
Message-ID: <20150724120819.GJ16878@atomide.com> (raw)
In-Reply-To: <pull-1437718313-185670>
* Tony Lindgren <tony@atomide.com> [150724 05:09]:
> SoC changes for omaps for v4.3 merge window:
>
> - Clean-up omap4_local_timer_init to drop deal legacy code
And this typo translatges to "drop dead leagcy code" :)
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap soc changes for v4.3
Date: Fri, 24 Jul 2015 05:08:20 -0700 [thread overview]
Message-ID: <20150724120819.GJ16878@atomide.com> (raw)
In-Reply-To: <pull-1437718313-185670>
* Tony Lindgren <tony@atomide.com> [150724 05:09]:
> SoC changes for omaps for v4.3 merge window:
>
> - Clean-up omap4_local_timer_init to drop deal legacy code
And this typo translatges to "drop dead leagcy code" :)
Regards,
Tony
next prev parent reply other threads:[~2015-07-24 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 12:06 [GIT PULL 1/2] omap soc changes for v4.3 Tony Lindgren
2015-07-24 12:06 ` [GIT PULL 2/2] omap dts changes for dm814x " Tony Lindgren
2015-07-24 12:06 ` Tony Lindgren
2015-07-24 12:08 ` Tony Lindgren [this message]
2015-07-24 12:08 ` [GIT PULL 1/2] omap soc changes " Tony Lindgren
[not found] ` <55b22a44.4b226b0a.bc37c.ffffce74SMTPIN_ADDED_BROKEN@mx.google.com>
2015-07-27 12:48 ` [GIT PULL 2/2] omap dts changes for dm814x " Olof Johansson
2015-07-27 12:48 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2015-07-24 12:06 [GIT PULL 1/2] omap soc changes " Tony Lindgren
[not found] <55b22a40.4b226b0a.bc37c.ffffce3aSMTPIN_ADDED_BROKEN@mx.google.com>
2015-07-27 12:47 ` Olof Johansson
2015-07-27 12:47 ` Olof Johansson
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=20150724120819.GJ16878@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.