linux-kernel - Re: [GIT PULL] slave-dmaengine updates for 3.4

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] [day] [month] [year] [list]

Message-ID: <CA+55aFweNvB8LM8yp3niQbROSUufF3g7UnE35eCKc25yLNQ64Q@mail.gmail.com>
Date:	Thu, 29 Mar 2012 15:42:16 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Vinod Koul <vinod.koul@...ux.intel.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Dan <dan.j.williams@...el.com>
Subject: Re: [GIT PULL] slave-dmaengine updates for 3.4

On Thu, Mar 29, 2012 at 4:26 AM, Vinod Koul <vinod.koul@...ux.intel.com> wrote:
>
> There are few merge conflicts with your tree, so I created a branch on
> todays tip and merged the slave-dma.next. Results are at
> git://git.infradead.org/users/vkoul/slave-dma.git linus_master_merge
> for you to compare while merging.

Hmm. I think your merge is wrong.

You left the "select ARCH_MXC_AUDMUX_V1" in arch/arm/mach-imx/Kconfig
around, even though that was removed elsewhere.

You also lost the changes to the pl330.c driver (DINVALID1 and the fix
for the NULL pointer dereference on thrd), and you've left a duplicate
dev_notice() in atmel-mci.c..

Anyway, I *think* I got my merge right, but people should double-check
and actually test the affected drivers.

I also get the feeling that snd_hwparams_to_dma_slave_config() should
clear the device_fc field, but whatever. I had resolved that
identically to yours as a "minimal change".

                            Linus
--
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/