From: Vinod Koul <vinod.koul@intel.com>
To: Xuelin Shi <xuelin.shi@freescale.com>
Cc: Harninder Rai <harninder.rai@freescale.com>,
"andriy.shevchenko@intel.com" <andriy.shevchenko@intel.com>,
Naveen Burmi <NaveenBurmi@freescale.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v3] dmaengine: driver support for FSL RaidEngine device.
Date: Fri, 17 Oct 2014 13:00:53 +0530 [thread overview]
Message-ID: <20141017073053.GL1638@intel.com> (raw)
In-Reply-To: <4cd56c90d1e44249bd2d417005183ec7@BL2PR03MB147.namprd03.prod.outlook.com>
On Fri, Oct 17, 2014 at 02:13:20AM +0000, Xuelin Shi wrote:
> Hi Dan & Vinod,
>
> I have sent out the v4 of this patch and not received any further feedback yet.
>
> This patch looks ruled out from the patchwork. https://patchwork.kernel.org/project/linux-dmaengine/list/?page=2
>
> So do you know what happened to this patch?
First pls do not top post on mailing list
Yes I did clean patchworks this week for older patches, can you please
resubmit and we can review them
Thanks
--
~Vinod
>
> Thanks,
> Xuelin Shi
>
>
> -----Original Message-----
> From: Shi Xuelin-B29237
> Sent: 2014年4月15日 11:08
> To: 'Dan Williams'
> Cc: Koul, Vinod; andriy.shevchenko@intel.com; dmaengine@vger.kernel.org; linuxppc-dev; Rai Harninder-B01044; Burmi Naveen-B16502
> Subject: RE: [PATCH v3] dmaengine: driver support for FSL RaidEngine device.
>
> Yes, "depend on !ASYNC_TX_CHANNEL_SWITCH" is better since fsldma selects this condition.
>
> Thanks,
> Xuelin Shi
>
> -----Original Message-----
> From: Dan Williams [mailto:dan.j.williams@intel.com]
> Sent: 2014年4月15日 8:30
> To: Shi Xuelin-B29237
> Cc: Koul, Vinod; andriy.shevchenko@intel.com; dmaengine@vger.kernel.org; linuxppc-dev; Rai Harninder-B01044; Burmi Naveen-B16502
> Subject: Re: [PATCH v3] dmaengine: driver support for FSL RaidEngine device.
>
> On Sun, Apr 13, 2014 at 7:48 PM, Xuelin Shi <xuelin.shi@freescale.com> wrote:
> > Hi Dan,
> >
> > fsl dma device and fsl raid device are two differenct devices that
> > both provide async_memcpy capability, so I use !FSL_DMA to disable the fsl dma device.
> >
> > That's to say, either select fsldma device, either fsl raid device.
> >
>
> Right, but that's not what your proposed Kconfig dependency line does.
>
> You want something like "depends on FSL_SOC && !(FSL_DMA || FSL_DMA=m)"
>
> However, the more problematic option is ASYNC_TX_CHANNEL_SWITCH. That option is problematic for RAID, so I propose "depend on !ASYNC_TX_CHANNEL_SWITCH" since that addresses both problems.
>
>
--
prev parent reply other threads:[~2014-10-17 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 7:41 [PATCH v3] dmaengine: driver support for FSL RaidEngine device xuelin.shi
2014-04-11 17:42 ` Dan Williams
2014-04-11 17:45 ` Dan Williams
2014-04-14 2:48 ` Xuelin Shi
2014-04-15 0:30 ` Dan Williams
2014-04-15 3:07 ` Xuelin Shi
2014-10-17 2:13 ` Xuelin Shi
2014-10-17 7:30 ` Vinod Koul [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=20141017073053.GL1638@intel.com \
--to=vinod.koul@intel.com \
--cc=NaveenBurmi@freescale.com \
--cc=andriy.shevchenko@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=harninder.rai@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=xuelin.shi@freescale.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.