linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] use AMBA periphid for hardcoding
Date: Fri, 13 May 2011 17:08:38 +0200	[thread overview]
Message-ID: <BANLkTim8Pw_YXX0eQPkoju9or7NDGOuZrA@mail.gmail.com> (raw)
In-Reply-To: <1300874614-14675-1-git-send-email-linus.walleij@stericsson.com>

2011/3/23 Linus Walleij <linus.walleij@stericsson.com>:

> These patches swithches the semantics of the optional AMBA periphid
> field from fallback (when hardware ID is not found) to hardcoding
> (overriding hardware ID) when used in platform data.

Russell have you had a chance to look at this?

I think 6827/1 and 6828/1 are just normal clean-up, whereas
6829/1 thru 6832/1 is the controversial part, but I'd like to stress
that it's solving a major issue for us, and I know for sure that the
silicon will not be re-spun to solve the issue :-(

I *have* contacted the hardware RTL engineers about it and kindly
asked them to keep periphids in sync in the future.

Yours,
Linus Walleij

      reply	other threads:[~2011-05-13 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 10:03 [PATCH 0/6] use AMBA periphid for hardcoding Linus Walleij
2011-05-13 15:08 ` Linus Walleij [this message]

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=BANLkTim8Pw_YXX0eQPkoju9or7NDGOuZrA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).