linux-kernel - Re: [PATCH 11/12] DMAENGINE: let PL08X memcpy TXDs wait

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, 23 Sep 2010 09:46:36 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	linux-arm-kernel@...ts.infradead.org, yuanyabin1978@...a.com,
	linux-kernel@...r.kernel.org,
	Per Fridén <per.friden@...ricsson.com>,
	Rabin VINCENT <rabin.vincent@...ricsson.com>
Subject: Re: [PATCH 11/12] DMAENGINE: let PL08X memcpy TXDs wait

2010/9/23 Dan Williams <dan.j.williams@...el.com>:

> The prep routine is meant to guarantee that all the resources for a
> transaction have been acquired.

A practicality here:

The assumption to fail for physical channel allocation at .tx_submit()
is already in the first patch adding the driver.

Should I squash all the icremental improvements into the original
driver, convert to fail at .prep() and resubmit to make all of this
easier, or do you want me to refactor the patch stack, or refactor
from patch 11/12 or...?

Yours,
Linus Walleij
--
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/