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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080709213907.1e8b253b.akpm@linux-foundation.org>
Date:	Wed, 9 Jul 2008 21:39:07 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	joerg.roedel@....com, tglx@...utronix.de, mingo@...hat.com,
	linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
	bhavna.sarathy@....com, Sebastian.Biemueller@....com,
	robert.richter@....com, joro@...tes.org
Subject: Re: [PATCH 16/34] AMD IOMMU: add kernel command line parameters for
 AMD IOMMU

On Thu, 10 Jul 2008 13:25:23 +0900 FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:

> I have one related question, we should document all the kernel boot
> parameters in Documentation/kernel-parameters.txt?
> 
> Some of x86_64 boot parameters are in
> Documentations/x86/x86_64/boot-options.txt. The parameters of IOMMUs
> are scattered. It's confusing.

A single monolithic file has advantages.  I think I'd prefer that
personally.  I'd forgotten that the x86-specific one exists, actually.

If we _do_ want to split this all out into separate files, they should all
be in a dedicated subdirectory under ./Documentation/, no?
--
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