linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: adaplas@gmail.com
Cc: akpm@osdl.org, linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] [HEADS UP] fbdev: Move arch-specific bits to their respective subdirectories
Date: Wed, 16 May 2007 14:53:17 -0700 (PDT)	[thread overview]
Message-ID: <20070516.145317.03979683.davem@davemloft.net> (raw)
In-Reply-To: <464B78BC.4080900@gmail.com>

From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: Thu, 17 May 2007 05:33:48 +0800

> Move arch-specific bits of fb_mmap() to their respective subdirectories
> 
> Signed-off-by: Antonino Daplas <adaplas@gmail.com>
> ---
> Hi all,
> 
> Please let me know if there are mistakes with this patch.

Thank you for doing this work.

__sparc_v9__ means CONFIG_SPARC64, if that is not defined it's
CONFIG_SPARC32, so you could simplify this patch a lot.

1) Remove __sparc_v9__ ifdefs from asm-sparc64/fb.h
2) Define fb_mmap_required() to return 0 in asm-sparc64/fb.h
3) Define fb_mmap_required() to return 1 in asm-sparc/fb.h
4) Remove all the sparc ifdef stuff you added to linux/fb.h
5) There won't be a default fb_mmap_required() provided by
   linux/fb.h on platforms other than sparc ones, you'll need
   to provide one in order for the build to work non-sparc since
   this call is unconditional in fbmem.c:

+	if (fb_mmap_required())
+		return -EINVAL;

With those fixes:

Signed-off-by: David S. Miller <davem@davemloft.net>

  reply	other threads:[~2007-05-16 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 21:33 [PATCH 10/10] [HEADS UP] fbdev: Move arch-specific bits to their respective subdirectories Antonino A. Daplas
2007-05-16 21:53 ` David Miller [this message]
2007-05-16 22:59   ` Antonino A. Daplas
2007-05-17  0:54 ` Kumar Gala
2007-05-17  6:13   ` Antonino A. Daplas
2007-05-17  9:43 ` Geert Uytterhoeven
2007-05-17 10:52   ` Antonino A. Daplas
2007-05-17  9:49 ` Christoph Hellwig
2007-05-17 10:51   ` Antonino A. Daplas
2007-05-17 20:30     ` David Miller

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=20070516.145317.03979683.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 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).