All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Kelvin Cheung <keguang.zhang@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5] dmaengine: Loongson1: Add Loongson1 dmaengine driver
Date: Sat, 17 Jul 2021 20:09:45 +0530	[thread overview]
Message-ID: <YPLrsXEmmHPtbZ+N@matsya> (raw)
In-Reply-To: <CAJhJPsUNCSK4VYv9Z4ZNDxC03F4CxQoAXCCf+TJmmbdUe4XNNA@mail.gmail.com>

On 17-07-21, 18:57, Kelvin Cheung wrote:
> Vinod Koul <vkoul@kernel.org> 于2021年7月14日周三 下午1:14写道:
> >
> > On 04-07-21, 23:33, Keguang Zhang wrote:
> >
> > > +static struct platform_driver ls1x_dma_driver = {
> > > +     .probe  = ls1x_dma_probe,
> > > +     .remove = ls1x_dma_remove,
> > > +     .driver = {
> > > +             .name   = "ls1x-dma",
> > > +     },
> > > +};
> > > +
> > > +module_platform_driver(ls1x_dma_driver);
> >
> > so my comment was left unanswered, who creates this device!
> 
> Sorry!
> This patch will create the device: https://patchwork.kernel.org/patch/12281691

Greg, looks like the above patch creates platform devices in mips, is
that the right way..?

-- 
~Vinod

  reply	other threads:[~2021-07-17 14:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-04 15:33 [PATCH V5] dmaengine: Loongson1: Add Loongson1 dmaengine driver Keguang Zhang
2021-07-14  5:14 ` Vinod Koul
2021-07-17 10:52   ` Kelvin Cheung
2021-07-17 10:57   ` Kelvin Cheung
2021-07-17 14:39     ` Vinod Koul [this message]
2021-07-17 17:39       ` Greg KH
2021-07-20 11:43         ` Vinod Koul
2021-07-20 11:48           ` Greg KH
2021-07-20 12:18             ` Vinod Koul
2021-07-21 12:22               ` Kelvin Cheung
2021-08-11  7:18                 ` Kelvin Cheung
2021-08-25 14:26 ` Vinod Koul
2021-08-29 13:43   ` Vinod Koul

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=YPLrsXEmmHPtbZ+N@matsya \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=keguang.zhang@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.