All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] omap fixes against v4.6-rc2
Date: Tue, 19 Apr 2016 07:54:00 -0700	[thread overview]
Message-ID: <20160419145400.GC5995@atomide.com> (raw)
In-Reply-To: <20160408191854.GZ16484@atomide.com>

* Tony Lindgren <tony@atomide.com> [160408 12:22]:
>       ARM: OMAP: Catch callers of revision information prior to it being populated

And this one causes bogus runtime warnings with other SoCs
as reported by Guenter Roeck. I'll revert this and post
an updated pull request shortly.

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] omap fixes against v4.6-rc2
Date: Tue, 19 Apr 2016 07:54:00 -0700	[thread overview]
Message-ID: <20160419145400.GC5995@atomide.com> (raw)
In-Reply-To: <20160408191854.GZ16484@atomide.com>

* Tony Lindgren <tony@atomide.com> [160408 12:22]:
>       ARM: OMAP: Catch callers of revision information prior to it being populated

And this one causes bogus runtime warnings with other SoCs
as reported by Guenter Roeck. I'll revert this and post
an updated pull request shortly.

Regards,

Tony

  reply	other threads:[~2016-04-19 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 19:18 [GIT PULL] omap fixes against v4.6-rc2 Tony Lindgren
2016-04-08 19:18 ` Tony Lindgren
2016-04-19 14:54 ` Tony Lindgren [this message]
2016-04-19 14:54   ` Tony Lindgren
2016-04-19 19:51   ` Tony Lindgren
2016-04-19 19:51     ` Tony Lindgren
2016-04-22 15:38     ` Kevin Hilman
2016-04-22 15:38       ` Kevin Hilman

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=20160419145400.GC5995@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.