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  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]
Date:	Mon, 16 Jun 2014 16:24:31 +0200
From:	Ulf Hansson <>
To:	Lee Jones <>
Cc:	micky <>,
	Samuel Ortiz <>,
	Chris Ball <>,,
	"" <>,
	linux-mmc <>,
	Greg Kroah-Hartman <>,
	Dan Carpenter <>,
	Roger <>, Wei WANG <>
Subject: Re: [PATCH 1/2] mfd: rtsx: add dma transfer function

On 16 June 2014 14:20, Lee Jones <> wrote:
>> From: Micky Ching <>
>> rtsx driver using a single function for transfer data, dma map/unmap are
>> placed in one fix function. We need map/unmap dma in different place(for
>> mmc async driver), so add three function for dma map, dma transfer and
>> dma unmap.
>> Signed-off-by: Micky Ching <>
>> ---
>>  drivers/mfd/rtsx_pcr.c       |   76 ++++++++++++++++++++++++++----------------
>>  include/linux/mfd/rtsx_pci.h |    6 ++++
>>  2 files changed, 54 insertions(+), 28 deletions(-)
> I don't see any glaring issues with this patch.  Does it rely on the
> first patch, or vise versa, or can it just be applied?

The mmc part in patch2 relies on this one, but please go ahead and
apply the mfd patch if you see it good.

I can later provide my ack for the mmc parts, in patch2, when it's a
reviewed properly and thus you can take it through your tree.

Kind regards
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists