From: Christoph Hellwig <hch@lst.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
palmer@sifive.com, arnd@arndb.de,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, mchehab@kernel.org,
james.morse@arm.com
Subject: Re: [PATCH] riscv: move sifive_l2_cache.c to drivers/misc
Date: Wed, 7 Aug 2019 17:24:38 +0200 [thread overview]
Message-ID: <20190807152438.GA16495@lst.de> (raw)
In-Reply-To: <20190807152215.GA26690@kroah.com>
On Wed, Aug 07, 2019 at 05:22:15PM +0200, Greg KH wrote:
> > Fixes: a967a289f169 ("RISC-V: sifive_l2_cache: Add L2 cache controller driver for SiFive SoCs")
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > arch/riscv/mm/Makefile | 1 -
> > drivers/misc/Makefile | 1 +
> > {arch/riscv/mm => drivers/misc}/sifive_l2_cache.c | 0
> > 3 files changed, 1 insertion(+), 1 deletion(-)
> > rename {arch/riscv/mm => drivers/misc}/sifive_l2_cache.c (100%)
>
> Why isn't this in drivers/edac/ ?
> why is this a misc driver? Seems like it should sit next to the edac
> stuff.
No idea. EDAC maintainers, would you object to taking what is
currently in arch/riscv/mm//sifive_l2_cache.c to drivers/edac/ ?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: arnd@arndb.de, palmer@sifive.com, linux-kernel@vger.kernel.org,
james.morse@arm.com, linux-riscv@lists.infradead.org,
mchehab@kernel.org, Christoph Hellwig <hch@lst.de>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH] riscv: move sifive_l2_cache.c to drivers/misc
Date: Wed, 7 Aug 2019 17:24:38 +0200 [thread overview]
Message-ID: <20190807152438.GA16495@lst.de> (raw)
In-Reply-To: <20190807152215.GA26690@kroah.com>
On Wed, Aug 07, 2019 at 05:22:15PM +0200, Greg KH wrote:
> > Fixes: a967a289f169 ("RISC-V: sifive_l2_cache: Add L2 cache controller driver for SiFive SoCs")
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > arch/riscv/mm/Makefile | 1 -
> > drivers/misc/Makefile | 1 +
> > {arch/riscv/mm => drivers/misc}/sifive_l2_cache.c | 0
> > 3 files changed, 1 insertion(+), 1 deletion(-)
> > rename {arch/riscv/mm => drivers/misc}/sifive_l2_cache.c (100%)
>
> Why isn't this in drivers/edac/ ?
> why is this a misc driver? Seems like it should sit next to the edac
> stuff.
No idea. EDAC maintainers, would you object to taking what is
currently in arch/riscv/mm//sifive_l2_cache.c to drivers/edac/ ?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-08-07 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 15:10 [PATCH] riscv: move sifive_l2_cache.c to drivers/misc Christoph Hellwig
2019-08-07 15:10 ` Christoph Hellwig
2019-08-07 15:22 ` Greg KH
2019-08-07 15:22 ` Greg KH
2019-08-07 15:24 ` Christoph Hellwig [this message]
2019-08-07 15:24 ` Christoph Hellwig
2019-08-07 15:40 ` Paul Walmsley
2019-08-07 15:40 ` Paul Walmsley
2019-08-08 7:50 ` Christoph Hellwig
2019-08-08 7:50 ` Christoph Hellwig
2019-08-08 8:07 ` Arnd Bergmann
2019-08-08 8:07 ` Arnd Bergmann
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=20190807152438.GA16495@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=palmer@sifive.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.