From: NeilBrown <neil@brown.name>
To: thirtythreeforty@gmail.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: George Hilliard <thirtythreeforty@gmail.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH v2 1/2] Move ralink-gdma to its own directory
Date: Fri, 11 Jan 2019 12:21:45 +1100 [thread overview]
Message-ID: <874laggf9y.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20190111004337.7223-1-thirtythreeforty@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4560 bytes --]
On Thu, Jan 10 2019, thirtythreeforty@gmail.com wrote:
> From: George Hilliard <thirtythreeforty@gmail.com>
>
> This is in preparation to allow it and the mt7621-dma drivers to be
> built separately. They are completely independent pieces of software,
> and the Kconfig specifies very different requirements.
>
> Cc: linux-kernel@vger.kernel.org
> Cc: devel@driverdev.osuosl.org
> Cc: Neil Brown <neil@brown.name>
> Signed-off-by: George Hilliard <thirtythreeforty@gmail.com>
Hi,
thanks for taking an interest in these drivers.
I original submitted this code because I though I needed it for my
mt7621 hardware, but I've subsequently realized that neither of these
dma drivers are used in this hardware.
Consequently I cannot test any changes you make.
But maybe you can - which would be excellent!
So this is just letting you and Greg know that despite my stated
interest, I cannot actually review or test this.
Thanks,
NeilBrown
> ---
> drivers/staging/Kconfig | 2 ++
> drivers/staging/Makefile | 1 +
> drivers/staging/mt7621-dma/Kconfig | 6 ------
> drivers/staging/mt7621-dma/Makefile | 1 -
> drivers/staging/ralink-gdma/Kconfig | 6 ++++++
> drivers/staging/ralink-gdma/Makefile | 3 +++
> drivers/staging/{mt7621-dma => ralink-gdma}/ralink-gdma.c | 0
> 7 files changed, 12 insertions(+), 7 deletions(-)
> create mode 100644 drivers/staging/ralink-gdma/Kconfig
> create mode 100644 drivers/staging/ralink-gdma/Makefile
> rename drivers/staging/{mt7621-dma => ralink-gdma}/ralink-gdma.c (100%)
>
> diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
> index e4f608815c05..b4cfde38e856 100644
> --- a/drivers/staging/Kconfig
> +++ b/drivers/staging/Kconfig
> @@ -110,6 +110,8 @@ source "drivers/staging/mt7621-spi/Kconfig"
>
> source "drivers/staging/mt7621-dma/Kconfig"
>
> +source "drivers/staging/ralink-gdma/Kconfig"
> +
> source "drivers/staging/mt7621-mmc/Kconfig"
>
> source "drivers/staging/mt7621-eth/Kconfig"
> diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
> index 5868631e8f1b..e095f427177c 100644
> --- a/drivers/staging/Makefile
> +++ b/drivers/staging/Makefile
> @@ -45,6 +45,7 @@ obj-$(CONFIG_SOC_MT7621) += mt7621-pci/
> obj-$(CONFIG_SOC_MT7621) += mt7621-pinctrl/
> obj-$(CONFIG_SOC_MT7621) += mt7621-spi/
> obj-$(CONFIG_SOC_MT7621) += mt7621-dma/
> +obj-$(CONFIG_SOC_MT7621) += ralink-gdma/
> obj-$(CONFIG_SOC_MT7621) += mt7621-mmc/
> obj-$(CONFIG_SOC_MT7621) += mt7621-eth/
> obj-$(CONFIG_SOC_MT7621) += mt7621-dts/
> diff --git a/drivers/staging/mt7621-dma/Kconfig b/drivers/staging/mt7621-dma/Kconfig
> index 2423c40099d1..b6e48a682c44 100644
> --- a/drivers/staging/mt7621-dma/Kconfig
> +++ b/drivers/staging/mt7621-dma/Kconfig
> @@ -1,9 +1,3 @@
> -config DMA_RALINK
> - tristate "RALINK DMA support"
> - depends on RALINK && !SOC_RT288X
> - select DMA_ENGINE
> - select DMA_VIRTUAL_CHANNELS
> -
> config MTK_HSDMA
> tristate "MTK HSDMA support"
> depends on RALINK && SOC_MT7621
> diff --git a/drivers/staging/mt7621-dma/Makefile b/drivers/staging/mt7621-dma/Makefile
> index d3152d45cf45..c9e3e1619ab0 100644
> --- a/drivers/staging/mt7621-dma/Makefile
> +++ b/drivers/staging/mt7621-dma/Makefile
> @@ -1,4 +1,3 @@
> -obj-$(CONFIG_DMA_RALINK) += ralink-gdma.o
> obj-$(CONFIG_MTK_HSDMA) += mtk-hsdma.o
>
> ccflags-y += -I$(srctree)/drivers/dma
> diff --git a/drivers/staging/ralink-gdma/Kconfig b/drivers/staging/ralink-gdma/Kconfig
> new file mode 100644
> index 000000000000..a12b2c672d48
> --- /dev/null
> +++ b/drivers/staging/ralink-gdma/Kconfig
> @@ -0,0 +1,6 @@
> +config DMA_RALINK
> + tristate "RALINK DMA support"
> + depends on RALINK && !SOC_RT288X
> + select DMA_ENGINE
> + select DMA_VIRTUAL_CHANNELS
> +
> diff --git a/drivers/staging/ralink-gdma/Makefile b/drivers/staging/ralink-gdma/Makefile
> new file mode 100644
> index 000000000000..5d917e0729bb
> --- /dev/null
> +++ b/drivers/staging/ralink-gdma/Makefile
> @@ -0,0 +1,3 @@
> +obj-$(CONFIG_DMA_RALINK) += ralink-gdma.o
> +
> +ccflags-y += -I$(srctree)/drivers/dma
> diff --git a/drivers/staging/mt7621-dma/ralink-gdma.c b/drivers/staging/ralink-gdma/ralink-gdma.c
> similarity index 100%
> rename from drivers/staging/mt7621-dma/ralink-gdma.c
> rename to drivers/staging/ralink-gdma/ralink-gdma.c
> --
> 2.20.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-01-11 1:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACmrr9gHucWaWtz07kQms6AsquLKAHbK+_Q0kF=92RGo6HmAFA@mail.gmail.com>
2019-01-11 0:43 ` thirtythreeforty
2019-01-11 0:43 ` [PATCH v2 2/2] Mediatek staging: Use individual config flags in Makefile thirtythreeforty
2019-01-15 15:30 ` [PATCH v2 2/2] staging: Mediatek: " Greg Kroah-Hartman
2019-01-15 17:02 ` [PATCH v3] " George Hilliard
2019-01-15 17:20 ` Greg Kroah-Hartman
2019-01-15 17:29 ` [PATCH v4] " George Hilliard
2019-01-15 17:43 ` Greg Kroah-Hartman
2019-01-16 6:48 ` [PATCH v5] " George Hilliard
2019-01-16 4:43 ` [PATCH v4] " kbuild test robot
2019-01-15 17:32 ` [PATCH v3] " George Hilliard
2019-01-11 1:21 ` NeilBrown [this message]
2019-01-11 2:13 ` [PATCH v2 1/2] Move ralink-gdma to its own directory George Hilliard
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=874laggf9y.fsf@notabene.neil.brown.name \
--to=neil@brown.name \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thirtythreeforty@gmail.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 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®