public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@osdl.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] restore libata build on frv
Date: Mon, 25 Sep 2006 15:39:12 +0100	[thread overview]
Message-ID: <20660.1159195152@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060925142016.GI29920@ftp.linux.org.uk>

Al Viro <viro@ftp.linux.org.uk> wrote:

> Fine by me.  In that case we need to add
> 	depends on !FRV || BROKEN

My point is that all the numbers are invalid or incorrect.  They will cause
the arch to oops, and so need completely replacing.  So that patch you added
is incorrect and should not include asm-generic/libata-portmap.h as nothing in
there is correct on this arch.  So your patch should *not* be applied, but
should instead be replaced.

> to drivers/ata/Kconfig and be done with that.  BTW, empty libata-portmap.h
> is equivalent to absent one - it still won't build.

Why does the arch have to supply those numbers?  What's wrong with my
suggested patch?  According to code in libata, these are _legacy_ access
methods, and on FRV they aren't currently required, so why can't I dispense
with them if they're not needed?  Doing that not only skips legacy accesses
for ISA compatibility, it also reduces the code size by not actually emitting
the code for the accesses, thus making the kernel smaller...

David

  reply	other threads:[~2006-09-25 14:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 22:39 [PATCH] restore libata build on frv Al Viro
2006-09-25 10:44 ` David Howells
2006-09-25 11:26   ` Alan Cox
2006-09-25 11:04     ` Russell King
2006-09-25 11:28       ` David Howells
2006-09-25 11:27     ` David Howells
2006-09-25 12:19       ` Alan Cox
2006-09-25 12:18         ` David Howells
2006-09-25 14:20           ` Al Viro
2006-09-25 14:39             ` David Howells [this message]
2006-09-25 15:46               ` Alan Cox
2006-09-25 16:04                 ` David Howells
2006-09-25 16:21                   ` Al Viro
2006-09-26  8:06                 ` David Woodhouse
2006-09-26  8:52                   ` Jeff Garzik
2006-09-26  8:56                     ` David Woodhouse
2006-09-26 11:25                       ` Alan Cox
2006-09-26 11:30                       ` Alan Cox
2006-09-26 16:15                       ` Linus Torvalds
2006-09-26 17:25                         ` David Howells
2006-09-26 20:21                         ` David Woodhouse
2006-09-27  7:05               ` David Woodhouse
2006-09-25 15:39             ` Alan Cox
2006-09-25 15:45               ` David Howells

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=20660.1159195152@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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