linux-kernel - Re: [PATCH] char drivers: ramoops documentation

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]

Date:	Mon, 1 Aug 2011 17:19:19 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Sergiu Iordache <sergiu@...gle.com>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	marco.stornelli@...il.com
Subject: Re: [PATCH] char drivers: ramoops documentation

On Mon, 1 Aug 2011 15:37:49 -0700 Sergiu Iordache wrote:

> On Mon, Aug 1, 2011 at 3:05 PM, Randy Dunlap <rdunlap@...otime.net> wrote:
> > On Mon,  1 Aug 2011 14:26:50 -0700 Sergiu Iordache wrote:
> >
> >> Add a documentation file describing the usage of Ramoops
> >>
> >> Change-Id: I9dab9c4b9e4921b220574470372e330d32f9c63b
> >
> > eh?
> Sorry, was it the commit message you did not like or something else?

The "Change-Id:" line.
There was a discussion that began with a July 14 patch from Mike Waychison
<mikew@...gle.com>:
Subject: [PATCH 1/2] Kconfig:  Allow disabling of CONFIG_DEVPORT

that included the line:
Google-Bug-Id: 3177114

Basically we don't want umpteen zillion different such tags in commit
messages.  I posted a patch last Friday:
Subject: [PATCH] Documentation: add Internal-reference-ID: patch tag

that allows people who want to track their internal references in commit
messages to use a common tag label/format:

Internal-reference-ID: <text>

<text> should not be a private (internal) URL.


> Thanks, I've updated the doc using your feedback. I have also
> rearranged the "1. Ramoops concepts" part to make it look better I
> think. I'll wait a bit for some more comments and then resubmit the
> new version of the patch.

Thanks.

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