From: Jeff Garzik <jgarzik@pobox.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: akpm@osdl.org, Stephen Rothwell <sfr@canb.auug.org.au>,
ppc-dev <linuxppc-dev@ozlabs.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] Remove powerpc specific parts of 3c509 driver
Date: Wed, 20 Sep 2006 17:29:04 -0400 [thread overview]
Message-ID: <4511B2A0.2010607@pobox.com> (raw)
In-Reply-To: <82BFB659-DCB3-477C-B53D-4D8C55BAADB7@kernel.crashing.org>
Segher Boessenkool wrote:
>>>>> Sure, PCI busses are little-endian. But is readX()/writeX() for PCI
>>>>> only?
>>>>
>>>> Yes.
>>>>
>>>> For other buses, use foo_writel(), etc.
>>> Can this please be documented then? Never heard this before...
>>
>> You have come late to the party.
>
> WHat do you mean here? Could you please explain?
>
>> This has been the case for many, many years.
>
> No, it was never documented AFAICS.
A de facto standard does not need to be documented, to be a de facto
standard.
A lot of Linux "standards" are often based on emails from Linus buried
halfway down a thread. A decision gets made, and people follow.
>> And there is no point in a massive rename to pci_writel(), either.
>
> That would be really inconvenient, sure. It's also inconvenient
> that all the nice short names are PCI-only.
Only to you, a decided minority of developers.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Matt Sealey <matt@genesi-usa.com>,
akpm@osdl.org, Stephen Rothwell <sfr@canb.auug.org.au>,
ppc-dev <linuxppc-dev@ozlabs.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] Remove powerpc specific parts of 3c509 driver
Date: Wed, 20 Sep 2006 17:29:04 -0400 [thread overview]
Message-ID: <4511B2A0.2010607@pobox.com> (raw)
In-Reply-To: <82BFB659-DCB3-477C-B53D-4D8C55BAADB7@kernel.crashing.org>
Segher Boessenkool wrote:
>>>>> Sure, PCI busses are little-endian. But is readX()/writeX() for PCI
>>>>> only?
>>>>
>>>> Yes.
>>>>
>>>> For other buses, use foo_writel(), etc.
>>> Can this please be documented then? Never heard this before...
>>
>> You have come late to the party.
>
> WHat do you mean here? Could you please explain?
>
>> This has been the case for many, many years.
>
> No, it was never documented AFAICS.
A de facto standard does not need to be documented, to be a de facto
standard.
A lot of Linux "standards" are often based on emails from Linus buried
halfway down a thread. A decision gets made, and people follow.
>> And there is no point in a massive rename to pci_writel(), either.
>
> That would be really inconvenient, sure. It's also inconvenient
> that all the nice short names are PCI-only.
Only to you, a decided minority of developers.
Jeff
next prev parent reply other threads:[~2006-09-20 21:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 4:54 Fw: [PATCH] Remove powerpc specific parts of 3c509 driver Stephen Rothwell
2006-09-19 18:42 ` Linas Vepstas
2006-09-19 18:42 ` Linas Vepstas
2006-09-19 18:52 ` Matt Sealey
2006-09-19 18:52 ` Matt Sealey
2006-09-19 19:44 ` Linas Vepstas
2006-09-19 19:44 ` Linas Vepstas
2006-09-19 23:24 ` Benjamin Herrenschmidt
2006-09-19 23:24 ` Benjamin Herrenschmidt
2006-09-20 0:21 ` Segher Boessenkool
2006-09-20 0:25 ` Benjamin Herrenschmidt
2006-09-20 0:58 ` Segher Boessenkool
2006-09-20 0:58 ` Segher Boessenkool
2006-09-20 1:17 ` Linas Vepstas
2006-09-20 1:17 ` Linas Vepstas
2006-09-20 1:41 ` Segher Boessenkool
2006-09-20 0:57 ` Jeff Garzik
2006-09-20 1:08 ` Segher Boessenkool
2006-09-20 1:08 ` Segher Boessenkool
2006-09-20 1:18 ` Jeff Garzik
2006-09-20 1:18 ` Jeff Garzik
2006-09-20 20:06 ` Segher Boessenkool
2006-09-20 20:06 ` Segher Boessenkool
2006-09-20 21:29 ` Jeff Garzik [this message]
2006-09-20 21:29 ` Jeff Garzik
2006-09-19 23:18 ` Fw: " Benjamin Herrenschmidt
2006-09-19 23:27 ` Paul Mackerras
2006-09-19 23:27 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 1:54 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=4511B2A0.2010607@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=segher@kernel.crashing.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.