linux-kernel - Re: ACPI vs proc_create_data() mismerge (was Re: proc_dir

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: <alpine.LFD.1.10.0804301622120.2980@woody.linux-foundation.org>
Date:	Wed, 30 Apr 2008 16:24:37 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
cc:	Justin Mattock <justinmattock@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: ACPI vs proc_create_data() mismerge (was Re: proc_dir_entry
 'info' already registered)

On Thu, 1 May 2008, Alexey Dobriyan wrote:
>
> ACPI vs proc_create_data() mismerge.

Ahh, my bad. Sorry. It all looked fine and compiled, but yes, I didn't 
boot-test the merge - although I did ask Len to double-check it for me.

Usually these "fairly trivial" merges work without any issues, so I do the 
merge for the maintainer rather than sending an email back saying "it 
didn't merge cleanly, can you do the merge for me". I reserve the latter 
for just the things that look really complicated..

> acpi_device_dir() is NULL until all files are createst, so everyting is
> created in straight in /proc/ and creation code warns.

Thanks,

		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/