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]
Date:	Thu, 25 Mar 2010 17:35:21 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Richard Röjfors <richard.rojfors@...agicore.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Linus Walleij <linus.walleij@...ricsson.com>
Subject: Re: [PATCH 0/2] mfd, dma: Add timb-dma driver

On Thu, Mar 25, 2010 at 11:44 AM, Richard Röjfors
<richard.rojfors@...agicore.com> wrote:
> To follow are two patches.
>
> Samuel and Dan, since the MFD patch relies on the DMA patch.
> The MFD patch is against Samuels next tree, maybe it is easiest
> if the DMA driver is merged via Samuels tree?

It depends on the mfd patch at runtime, but thankfully not at build
time.  There are some other patches being floated by Linus to change
the device_terminate_all() and device_is_tx_complete() operations.
So, I want to take just the driver patch through the dma tree to make
sure everything stays in sync.

Thanks,
Dan
--
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