mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Arnd Bergmann <arnd@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reference to non-existing config LOGIC_IOMEM_FALLBACK
Date: Mon, 03 Jan 2022 16:36:54 +0100	[thread overview]
Message-ID: <f86494dfec02e41e6897e8a9617d66b2d7674698.camel@sipsolutions.net> (raw)
In-Reply-To: <CAKXUXMxKj_d+Nb25rsukj0u2_06KB3+OVWfkYqNzWQG67S=rgw@mail.gmail.com>

On Thu, 2021-12-30 at 12:45 +0000, Lukas Bulwahn wrote:
> Dear Johannes, dear Richard,
> 
> In commit ca2e334232b6 ("lib: add iomem emulation (logic_iomem)"), you
> have added an ifdef on the non-existing config LOGIC_IOMEM_FALLBACK in
> ./lib/logic_iomem.c.
> 
> In the commit message, you note:
> 
>     To use, an architecture must 'select LOGIC_IOMEM' in Kconfig
>     and then include <asm-generic/logic_io.h> into asm/io.h to get
>     the __raw_read*/__raw_write* functions.
> 
>     Optionally, an architecture may 'select LOGIC_IOMEM_FALLBACK'
>     in which case non-emulated regions will 'fall back' to the
>     various real_* functions that must then be provided.
> 
> This config LOGIC_IOMEM and config LOGIC_IOMEM_FALLBACK is however not
> defined in any Kconfig file in the current repository.

Yeah, umm. Artifact of renaming things ...

> Did you mean that the architecture shall select INDIRECT_IOMEM and
> INDIRECT_IOMEM_FALLBACK, which were defined in your commit, and the
> questionable ifdef in ./lib/logic_iomem.c needs to be changed to
> INDIRECT_IOMEM_FALLBACK?

Yes. I'll send a fix, thanks for reporting.

johannes


      reply	other threads:[~2022-01-03 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 12:45 Lukas Bulwahn
2022-01-03 15:36 ` Johannes Berg [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=f86494dfec02e41e6897e8a9617d66b2d7674698.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®