linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 5/6] x86: add CONFIG_ARM_AMBA, selected by STA2X11
Date: Tue, 3 Jul 2012 12:05:21 +0100	[thread overview]
Message-ID: <20120703110520.GI29030@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FF1F987.3030501@zytor.com>

On Mon, Jul 02, 2012 at 12:41:59PM -0700, H. Peter Anvin wrote:
> On 07/02/2012 11:33 AM, Mark Brown wrote:

> >> Last I saw I saw a patch to that effect, asked what the benefit
> >> was, and got no answer.

> > Are you positive about that?  I don't recall you replying any of
> > the times I sent out the patch and my mail archive isn't
> > contradicting me either.

> I said last time I saw a patch to that effect; it might not have been
> from you.  I might not have seen yours for whatever reason (including
> losing it on my end.)

I'm kind of surprised anyone else has been sending stuff (unless mine
got resent by someone else, I did include it in some of my serises for
the clock API); I know I've posted mine several times now.  In any case,
I hope the mail you're replying to answers your question about why it's
useful.

In general I'd probably go further and say that (at least when a generic
implementation is available) there should be a very good reason for not
enabling an API on an architecture rather than the other way around.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120703/38f6f475/attachment.sig>

  reply	other threads:[~2012-07-03 11:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1338222460.git.rubini@gnudd.com>
2012-05-28 16:37 ` [PATCH V2 1/6] sizes.h: move from asm-generic to <linux/sizes.h> Alessandro Rubini
2012-05-28 16:37 ` [PATCH V2 2/6] amba: use the new linux/sizes.h Alessandro Rubini
2012-05-28 16:37 ` [PATCH V2 3/6] ARM: " Alessandro Rubini
2012-05-28 16:37 ` [PATCH V2 4/6] serial: " Alessandro Rubini
2012-05-28 16:37 ` [PATCH V2 5/6] x86: add CONFIG_ARM_AMBA, selected by STA2X11 Alessandro Rubini
2012-06-28 20:06   ` H. Peter Anvin
2012-07-01 10:44   ` Alessandro Rubini
2012-07-01 10:59     ` Russell King - ARM Linux
2012-07-01 11:58       ` Jassi Brar
2012-07-01 12:10         ` Russell King - ARM Linux
2012-07-01 13:11           ` Jassi Brar
2012-07-01 11:04     ` Alessandro Rubini
2012-07-01 11:11       ` Russell King - ARM Linux
2012-07-01 14:13     ` H. Peter Anvin
2012-07-02 16:58       ` Arnd Bergmann
2012-07-02 18:05         ` Mark Brown
2012-07-02 18:07           ` H. Peter Anvin
2012-07-02 18:33             ` Mark Brown
2012-07-02 19:41               ` H. Peter Anvin
2012-07-03 11:05                 ` Mark Brown [this message]
2012-07-03 13:00     ` Alessandro Rubini
2012-07-03 13:19       ` Arnd Bergmann
2012-07-03 19:34         ` Russell King - ARM Linux
2012-08-05 20:28           ` Linus Walleij
2012-08-07 10:06             ` Kukjin Kim
2012-07-03 13:26       ` Alessandro Rubini
2012-07-03 19:46         ` Russell King - ARM Linux
2012-05-28 16:38 ` [PATCH V2 6/6] drivers/amba: add support for a PCI bridge Alessandro Rubini

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=20120703110520.GI29030@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --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).