linux-kernel - Re: [patch v3 1/1] md: Software Raid autodetect dev list not array

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: <46D3A8AD.6000701@oracle.com>
Date:	Mon, 27 Aug 2007 21:46:37 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Michael J. Evans" <mjevans1983@...cast.net>
CC:	Michael Evans <mjevans1983@...il.com>, Neil Brown <neilb@...e.de>,
	Ingo Molnar <mingo@...hat.com>, linux-raid@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [patch v3 1/1] md: Software Raid autodetect dev list not array

Michael J. Evans wrote:
> On Monday 27 August 2007, Randy Dunlap wrote:
>> On Mon, 27 Aug 2007 15:16:21 -0700 Michael J. Evans wrote:
>>
>>> =============================================================
>>> --- linux/drivers/md/md.c.orig	2007-08-21 03:19:42.511576248 -0700
>>> +++ linux/drivers/md/md.c	2007-08-21 04:30:09.775525710 -0700
>>> @@ -24,4 +24,6 @@
>>>
>>> +   - autodetect dev list not array: Michael J. Evans 
> <mjevans1983@...il.com>
>>> +
>> Nowadays we use an SCM for such comments, not the source file(s).
> 
> SCM?  Is this automatic, where do I go to see it?

See Documentation/SubmittingPatches:
14) The canonical patch format:

The canonical patch message body contains the following:

  - A "from" line specifying the patch author.

  - An empty line.

  - The body of the explanation, which will be copied to the
    permanent changelog to describe this patch.

  - The "Signed-off-by:" lines, described above, which will
    also go in the changelog.

  - A marker line containing simply "---".

  - Any additional comments not suitable for the changelog.

  - The actual patch (diff output).


so just put whatever you want to be in the permanent SCM logs
into the "body of the explanation" part of the email.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/