lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokmmA3wCiao0hBzecRYRvKKyVo3LSO1a=EMLJCP3OmPuQ@mail.gmail.com>
Date:	Thu, 19 Feb 2015 14:23:27 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jean Delvare <jdelvare@...e.de>
Cc:	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Brian Loften <bloften80@...il.com>,
	Vinod Koul <vinod.koul@...el.com>, dmaengine@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Antoine Ténart <antoine@...e-electrons.com>,
	Russell King <linux@....linux.org.uk>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v5 59/61] dmaengine: Add a warning for drivers not using
 the generic slave caps retrieval

On 19 February 2015 at 13:39, Jean Delvare <jdelvare@...e.de> wrote:
> My understanding is that the warning message is here on purpose to
> instruct DMA driver authors to fix their code. So if anyone need to fix
> anything, that would be you and Andy. That being said, I suspect Andy

To some extent yes, but Andy has already tried to fix that for most of
the drivers and so I just pointed out that something is missed.

> already did that:
>
> commit 029a40e97d0db269f4a7fc02b0f29f627f628309
> Author: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> Date:   Fri Jan 2 16:17:24 2015 +0200
>
>     dmaengine: dw: provide DMA capabilities
>
> Brian, can you please try the latest Linus or linux-next kernel (or
> backport the above commit to your current kernel) and confirm that the
> backtraces are no longer printed?

Maybe yes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ