linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: Compiling 5.5-rc2: warning: "IRQ_TIMER" redefined
Date: Thu, 19 Dec 2019 14:56:01 +0200	[thread overview]
Message-ID: <CAEn-LTq-SQXK4EO2itu_CcyqKjM8FReHqA1WjcHkZWJO2xP5Mg@mail.gmail.com> (raw)
In-Reply-To: <CAEn-LTqw=r7WotzzHJZou10O5mcCDs+TK_ep4hhyBbUnHMGMAg@mail.gmail.com>

On Thu, Dec 19, 2019 at 2:46 PM David Abdurachmanov
<david.abdurachmanov@gmail.com> wrote:
>
> Hi,
>
> While compiling modules for 5.5-rc2 in Fedora/RISCV I see compilation
> warning. Similar was reported 10 days ago by kbuild test robot [0].
> That points to a4c3733d32a72f11dee86d0731d7565aa6ebe22d ("riscv:
> abstract out CSR names for supervisor vs machine mode").  The commit
> added
>
> [..]
> #ifdef CONFIG_RISCV_M_MODE
> [..]
> #else /* CONFIG_RISCV_M_MODE */
> [..]
> # define IRQ_TIMER IRQ_S_TIMER
> [..]
> #endif /* CONFIG_RISCV_M_MODE */
>
> There seems to be a few drivers that define IRQ_TIMER:
>
> sound/pci/au88x0/au88x0.h
> sound/pci/azt3328.h
> drivers/net/fddi/skfp/h/skfbi.h
> drivers/char/pcmcia/synclink_cs.c
>
> Should we pick something different than IRQ_TIMER to avoid this clash?

Sorry for the email. I just noticed that a patch was proposed
yesterday to fix it:

https://patchwork.kernel.org/patch/11301459/

david


      reply	other threads:[~2019-12-19 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 12:46 Compiling 5.5-rc2: warning: "IRQ_TIMER" redefined David Abdurachmanov
2019-12-19 12:56 ` David Abdurachmanov [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=CAEn-LTq-SQXK4EO2itu_CcyqKjM8FReHqA1WjcHkZWJO2xP5Mg@mail.gmail.com \
    --to=david.abdurachmanov@gmail.com \
    --cc=linux-riscv@lists.infradead.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).