All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Kevin Hilman <khilman@linaro.org>,
	Simon Horman <horms@verge.net.au>, Dan Murphy <dmurphy@ti.com>,
	linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
	Chris Ball <cjb@laptop.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dmaengine: shdma: fix a build failure on platforms with no DMA support
Date: Fri, 5 Jul 2013 10:23:50 +0530	[thread overview]
Message-ID: <20130705045350.GA10947@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306192125480.12502@axis700.grange>

On Wed, Jun 19, 2013 at 09:32:18PM +0200, Guennadi Liakhovetski wrote:
> Hi Vinod
> 
> On Wed, 19 Jun 2013, Kevin Hilman wrote:
> 
> > On Thu, May 30, 2013 at 7:44 PM, Simon Horman <horms@verge.net.au> wrote:
> > 
> > [...]
> > 
> > > thanks for this. I will wait for a refresh (as we discussed earlier today).
> > > Can I confirm that this is a fix for v3.10? If so, could ou note
> > > that when you post your revised patch?
> > 
> > Any progress on this patch?
> > 
> > The SH-mobile defconfigs are still all failing in linux-next.
> 
> In
> 
> https://patchwork.kernel.org/patch/2640061/
And you havent CC maintainers on this patch, so I dont have it!
> 
> I proposed a simple immediate fix for this problem. Arnd at the same time 
> developed an alternative solution:
> 
> https://patchwork.kernel.org/patch/2644121/
> https://patchwork.kernel.org/patch/2644111/
Reading these patches I agree with Arnd that client drivers should not depend on
dma slave drivers. Existing issue need to be fixed

Arnd, Have you merged these changes?

--
~Vinod
> 
> Which, I think, is a much larger change and isn't suitable as a bug-fix 
> this late in the release cycle. Instead those patches address other issues 
> with the shdma drivers, which might need to be carefully studied and 
> solutions have to be found, which, however, would require more work and 
> need a longer time. What is your opinion on this? Would you agree to apply 
> v2 of this patch, as referenced above or would you prefer a different 
> solution?
> 
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/

-- 

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dmaengine: shdma: fix a build failure on platforms with no DMA support
Date: Fri, 05 Jul 2013 05:05:50 +0000	[thread overview]
Message-ID: <20130705045350.GA10947@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306192125480.12502@axis700.grange>

On Wed, Jun 19, 2013 at 09:32:18PM +0200, Guennadi Liakhovetski wrote:
> Hi Vinod
> 
> On Wed, 19 Jun 2013, Kevin Hilman wrote:
> 
> > On Thu, May 30, 2013 at 7:44 PM, Simon Horman <horms@verge.net.au> wrote:
> > 
> > [...]
> > 
> > > thanks for this. I will wait for a refresh (as we discussed earlier today).
> > > Can I confirm that this is a fix for v3.10? If so, could ou note
> > > that when you post your revised patch?
> > 
> > Any progress on this patch?
> > 
> > The SH-mobile defconfigs are still all failing in linux-next.
> 
> In
> 
> https://patchwork.kernel.org/patch/2640061/
And you havent CC maintainers on this patch, so I dont have it!
> 
> I proposed a simple immediate fix for this problem. Arnd at the same time 
> developed an alternative solution:
> 
> https://patchwork.kernel.org/patch/2644121/
> https://patchwork.kernel.org/patch/2644111/
Reading these patches I agree with Arnd that client drivers should not depend on
dma slave drivers. Existing issue need to be fixed

Arnd, Have you merged these changes?

--
~Vinod
> 
> Which, I think, is a much larger change and isn't suitable as a bug-fix 
> this late in the release cycle. Instead those patches address other issues 
> with the shdma drivers, which might need to be carefully studied and 
> solutions have to be found, which, however, would require more work and 
> need a longer time. What is your opinion on this? Would you agree to apply 
> v2 of this patch, as referenced above or would you prefer a different 
> solution?
> 
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/

-- 

WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: shdma: fix a build failure on platforms with no DMA support
Date: Fri, 5 Jul 2013 10:23:50 +0530	[thread overview]
Message-ID: <20130705045350.GA10947@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306192125480.12502@axis700.grange>

On Wed, Jun 19, 2013 at 09:32:18PM +0200, Guennadi Liakhovetski wrote:
> Hi Vinod
> 
> On Wed, 19 Jun 2013, Kevin Hilman wrote:
> 
> > On Thu, May 30, 2013 at 7:44 PM, Simon Horman <horms@verge.net.au> wrote:
> > 
> > [...]
> > 
> > > thanks for this. I will wait for a refresh (as we discussed earlier today).
> > > Can I confirm that this is a fix for v3.10? If so, could ou note
> > > that when you post your revised patch?
> > 
> > Any progress on this patch?
> > 
> > The SH-mobile defconfigs are still all failing in linux-next.
> 
> In
> 
> https://patchwork.kernel.org/patch/2640061/
And you havent CC maintainers on this patch, so I dont have it!
> 
> I proposed a simple immediate fix for this problem. Arnd at the same time 
> developed an alternative solution:
> 
> https://patchwork.kernel.org/patch/2644121/
> https://patchwork.kernel.org/patch/2644111/
Reading these patches I agree with Arnd that client drivers should not depend on
dma slave drivers. Existing issue need to be fixed

Arnd, Have you merged these changes?

--
~Vinod
> 
> Which, I think, is a much larger change and isn't suitable as a bug-fix 
> this late in the release cycle. Instead those patches address other issues 
> with the shdma drivers, which might need to be carefully studied and 
> solutions have to be found, which, however, would require more work and 
> need a longer time. What is your opinion on this? Would you agree to apply 
> v2 of this patch, as referenced above or would you prefer a different 
> solution?
> 
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/

-- 

  reply	other threads:[~2013-07-05  4:53 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 16:02 [PATCH] dmaengine: shdma: fix a build failure on platforms with no DMA support Guennadi Liakhovetski
2013-05-30 16:02 ` Guennadi Liakhovetski
2013-05-30 16:02 ` Guennadi Liakhovetski
2013-05-30 16:23 ` Dan Murphy
2013-05-30 16:23   ` Dan Murphy
2013-05-30 16:23   ` Dan Murphy
2013-05-31  2:44   ` Simon Horman
2013-05-31  2:44     ` Simon Horman
2013-05-31  2:44     ` Simon Horman
2013-06-19 19:00     ` Kevin Hilman
2013-06-19 19:00       ` Kevin Hilman
2013-06-19 19:00       ` Kevin Hilman
2013-06-19 19:32       ` Guennadi Liakhovetski
2013-06-19 19:32         ` Guennadi Liakhovetski
2013-06-19 19:32         ` Guennadi Liakhovetski
2013-07-05  4:53         ` Vinod Koul [this message]
2013-07-05  5:05           ` Vinod Koul
2013-07-05  4:53           ` Vinod Koul
2013-07-08  7:52           ` Olof Johansson
2013-07-08  7:52             ` Olof Johansson
2013-07-08  7:52             ` Olof Johansson
2013-07-08  7:21             ` Vinod Koul
2013-07-08  7:33               ` Vinod Koul
2013-07-08  7:21               ` Vinod Koul
2013-07-10  2:09               ` Simon Horman
2013-07-10  2:09                 ` Simon Horman
2013-07-10  2:09                 ` Simon Horman
2013-07-08  8:13           ` Guennadi Liakhovetski
2013-07-08  8:13             ` Guennadi Liakhovetski
2013-07-08  8:13             ` Guennadi Liakhovetski
  -- strict thread matches above, loose matches on Subject: below --
2013-07-10  2:09 Simon Horman
2013-07-10  2:09 ` Simon Horman
2013-07-10  2:09 ` Simon Horman
2013-07-16  1:20 ` Simon Horman
2013-07-16  1:20   ` Simon Horman
2013-07-16  1:20   ` Simon Horman
2013-07-23  2:39   ` Olof Johansson
2013-07-23  2:39     ` Olof Johansson
2013-07-23  2:39     ` Olof Johansson
2013-07-23  4:12     ` Simon Horman
2013-07-23  4:12       ` Simon Horman
2013-07-23  4:12       ` Simon Horman
     [not found]       ` <87zjtddgtg.wl%kuninori.morimoto.gx@renesas.com>
     [not found]         ` <20130724034009.GA18355@verge.net.au>
     [not found]           ` <87d2q8v6fs.wl%kuninori.morimoto.gx@renesas.com>
2013-07-24  6:12             ` [PATCH resend] shdma: fixup sh_dmae_get_partial() calculation error Kuninori Morimoto
2013-07-24  6:12               ` Kuninori Morimoto
2013-07-24  8:43               ` Guennadi Liakhovetski
2013-07-24  8:43                 ` Guennadi Liakhovetski
2013-07-26  2:38                 ` Simon Horman
2013-07-26  2:38                   ` Simon Horman
2013-07-30  8:49               ` Simon Horman
2013-07-30  8:49                 ` Simon Horman
2013-07-30  9:22                 ` Guennadi Liakhovetski
2013-07-30  9:22                   ` Guennadi Liakhovetski
2013-07-31  0:52                   ` Simon Horman
2013-07-31  0:52                     ` Simon Horman

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=20130705045350.GA10947@intel.com \
    --to=vinod.koul@intel.com \
    --cc=cjb@laptop.org \
    --cc=dmurphy@ti.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=horms@verge.net.au \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@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.