From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: "Linux/m68k" <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] m68k: common PCI support definitions and code
Date: Mon, 28 Jun 2021 15:29:33 +0200 [thread overview]
Message-ID: <CAMuHMdX5vn87B=-pm8puECC74bog4YM6Uf2vY4mondntzSg65Q@mail.gmail.com> (raw)
In-Reply-To: <6796b52b-a868-7955-fedd-e841a21e6c95@linux-m68k.org>
Hi Greg,
On Mon, Jun 28, 2021 at 3:23 PM Greg Ungerer <gerg@linux-m68k.org> wrote:
> On 28/6/21 5:44 pm, Geert Uytterhoeven wrote:
> > On Mon, Jul 16, 2012 at 2:25 PM <gerg@snapgear.com> wrote:
> >> From: Greg Ungerer <gerg@uclinux.org>
> >>
> >> Basic set of definitions and support code required to turn on CONFIG_PCI
> >> for the m68k architecture. Nothing specific to any PCI implementation in
> >> any m68k class CPU hardware yet.
> >>
> >> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
> >
> >> --- a/arch/m68k/include/asm/io_mm.h
> >> +++ b/arch/m68k/include/asm/io_mm.h
> >> @@ -340,4 +340,6 @@ static inline void memcpy_toio(volatile void __iomem *dst, const void *src, int
> >> */
> >> #define xlate_dev_kmem_ptr(p) p
> >>
> >> +#define ioport_map(port, nr) ((void __iomem *)(port))
> >
> > So should we dop:
> >
> > config NO_IOPORT_MAP
> > def_bool y
> >
> > Triggered by seeing CONFIG_GPIO_TQMX86 being removed from allmodconfig
> > builds due to commit c6414e1a2bd26b00 ("gpio: AMD8111 and TQMX86
> > require HAS_IOPORT_MAP").
>
> I guess we could.
> But we would have to remove the iomap/iounmap definitions in kmap.h too right?
Why? Do I need more coffee?
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
next prev parent reply other threads:[~2021-06-28 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 12:27 [PATCH v2 0/5] ColdFire PCI bus support gerg
2012-07-16 12:27 ` [PATCH v2 1/5] m68k: common PCI support definitions and code gerg
2021-06-28 7:44 ` Geert Uytterhoeven
2021-06-28 13:23 ` Greg Ungerer
2021-06-28 13:29 ` Geert Uytterhoeven [this message]
2021-06-28 13:58 ` Greg Ungerer
2012-07-16 12:27 ` [PATCH v2 2/5] m68k: add PCI bus support definitions for the ColdFire M54xx SoC family gerg
2012-07-16 12:27 ` [PATCH v2 3/5] m68k: add IO access definitions to support PCI on ColdFire platforms gerg
2012-07-16 12:27 ` [PATCH v2 4/5] m68k: add PCI bus code support for the ColdFire M54xx SoC family gerg
2012-07-16 12:27 ` [PATCH v2 5/5] m68k: allow PCI bus to be enabled for ColdFire m54xx CPUs gerg
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='CAMuHMdX5vn87B=-pm8puECC74bog4YM6Uf2vY4mondntzSg65Q@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@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).