public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: gerg@snapgear.com
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: merge the mmu and non-mmu versions of sys_m68k.c
Date: Sat, 21 May 2011 22:05:27 +0200	[thread overview]
Message-ID: <BANLkTinRtyuC3dFstd8e8CXuas9A2NeA3A@mail.gmail.com> (raw)
In-Reply-To: <1303354504-30085-1-git-send-email-gerg@snapgear.com>

On Thu, Apr 21, 2011 at 04:55,  <gerg@snapgear.com> wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> There is a lot of common code in the sys_m68k.c files. The mmu and non-mmu
> versions can easily be merged into a single file.
>
> There is really only 2 functions that differ in the 2 cases. A single
> ifdef on CONFIG_MMU can take care of this. Alternatively we could break
> those 2 functions out and maintain sys_m68k_no.c and sys_m68k_mm.c with
> just this code in it (Makefile could then just build the right one).
> Does anyone have strong feelings on which way they want this done?

I prefer one file with a few ifdefs, as it's more localized.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2011-05-21 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  2:55 [PATCH] m68k: merge the mmu and non-mmu versions of sys_m68k.c gerg
2011-05-21 20:05 ` Geert Uytterhoeven [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=BANLkTinRtyuC3dFstd8e8CXuas9A2NeA3A@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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