public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: huzhi001@208suo.com, gerg@linux-m68k.org, geert@linux-m68k.org
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68knommu: Fix warnings in io_no.h: Delete one of repeated word 'readw readl writew writel' in comment. WARNING: Possible repeated word: 'readw' WARNING: Possible repeated word: 'readl' WARNING: Possible repeated word: 'writew' WARNING: Possible repeated word: 'writel'
Date: Mon, 24 Jul 2023 17:34:34 +1200	[thread overview]
Message-ID: <b0c9bf6d-786d-29b8-7811-e132534227fe@gmail.com> (raw)
In-Reply-To: <9e13fec02524afde21bdf5783dcf7246@208suo.com>

Hi,

please reconsider - "#define something something" is legitimate use, and
quite intentional.

Pattern matching can only get you so far, sorry ...

Cheers,

    Michael

Am 24.07.23 um 12:40 schrieb huzhi001@208suo.com:
> Signed-off-by: ZhiHu <huzhi001@208suo.com>
> ---
>  arch/m68k/include/asm/io_no.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/m68k/include/asm/io_no.h
> b/arch/m68k/include/asm/io_no.h
> index 2c96e8480173..b24eb741e666 100644
> --- a/arch/m68k/include/asm/io_no.h
> +++ b/arch/m68k/include/asm/io_no.h
> @@ -62,7 +62,7 @@ static int cf_internalio(const volatile void __iomem
> *addr)
>   * endian on m68k/ColdFire. Bus based address ranges, like the PCI bus,
>   * are accessed little endian - so we need to byte swap those.
>   */
> -#define readw readw
> +#define readw
>  static inline u16 readw(const volatile void __iomem *addr)
>  {
>      if (cf_internalio(addr))
> @@ -70,7 +70,7 @@ static inline u16 readw(const volatile void __iomem
> *addr)
>      return swab16(__raw_readw(addr));
>  }
>
> -#define readl readl
> +#define readl
>  static inline u32 readl(const volatile void __iomem *addr)
>  {
>      if (cf_internalio(addr))
> @@ -78,7 +78,7 @@ static inline u32 readl(const volatile void __iomem
> *addr)
>      return swab32(__raw_readl(addr));
>  }
>
> -#define writew writew
> +#define writew
>  static inline void writew(u16 value, volatile void __iomem *addr)
>  {
>      if (cf_internalio(addr))
> @@ -87,7 +87,7 @@ static inline void writew(u16 value, volatile void
> __iomem *addr)
>          __raw_writew(swab16(value), addr);
>  }
>
> -#define writel writel
> +#define writel
>  static inline void writel(u32 value, volatile void __iomem *addr)
>  {
>      if (cf_internalio(addr))

      reply	other threads:[~2023-07-24  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_816D5035481D1083943D8E965A59860D5E06@qq.com>
2023-07-24  0:40 ` [PATCH] m68knommu: Fix warnings in io_no.h: Delete one of repeated word 'readw readl writew writel' in comment. WARNING: Possible repeated word: 'readw' WARNING: Possible repeated word: 'readl' WARNING: Possible repeated word: 'writew' WARNING: Possible repeated word: 'writel' huzhi001
2023-07-24  5:34   ` Michael Schmitz [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=b0c9bf6d-786d-29b8-7811-e132534227fe@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=huzhi001@208suo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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