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: <1263851158.5591.147.camel@localhost.localdomain>
Date:	Mon, 18 Jan 2010 13:45:58 -0800
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Mark Allyn <mark.a.allyn@...el.com>
Cc:	linux-kernel@...r.kernel.org, greg@...ah.com, alan@...ux.intel.com,
	charles.f.johnson@...el.com
Subject: Re: [PATCH] Rename rar_driver to rar_register

Hi Mark,

> The purpose of this patch is to change the name of rar_register source
> files (both the .c and .h files) to rar_register.
> 
> This is the first of seven patches for the rar_register driver
> for Sunday, January 17, 2009
> 
> This is to clarify that this driver is for the rar_register.
> 
> This patch only changes the names. It does not make any changes in
> any code.
> 
> Any checkpatch errors on this code were from the original code. They
> will be addressed in future patches.
> 
> The rar stands for restricted access region. The restricted access
> region is an area of memory that can be locked from access by the
> x86 processor.
> 
> The purpose of the restricted access region is to safeguard confidential
> information from any unauthorized software running on the x86 processor.
> 
> The purpose of this driver is to enable other drivers to obtain
> the address ranges of the restricted regions as well as lock them.
> 
> This patch is referenced off the linux-next repository as pulled
> on Sunday, January 17, 2010

this is a lot of boilerplate that you repeat for every patch in this
series. It distracts from the actual change you are making. I would
prefer if you send an introductory/summary email and then focus the
commit message on the actual change you are making.

Regards

Marcel


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