public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <mchehab@osg.samsung.com>, <dougthompson@xmission.com>,
	<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] EDAC, amd64_edac: Update copyright and documentation info
Date: Thu, 17 Sep 2015 09:35:25 -0500	[thread overview]
Message-ID: <55FACFAD.4010706@amd.com> (raw)
In-Reply-To: <20150917074327.GB12316@nazgul.tnic>


On 9/17/15 2:43 AM, Borislav Petkov wrote:
> On Wed, Sep 16, 2015 at 03:53:31PM -0500, Aravind Gopalakrishnan wrote:
>>    *	Changes/Fixes by Borislav Petkov <bp@alien8.de>:
>>    *		- misc fixes and code cleanups
>>    *
>> + *	Changes by Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
>> + *		- Add support for-
>> + *		   - Fam15h Models (30-3fh; 60-6fh)
>> + *		   - Fam16h Models (00-0fh; 30-3fh)
>> + *
> Actually, we have git which can give you all the exact changelog
> information you'd need. So instead of adding more to the header, simply
> remove all changelog info from there. It is a thing from the past anyway.

Okay, will do.

>>    *
>> + *	Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 15h
>> + *	       Models 30h-3Fh Processors
>> + *	AMD publication #: 49125
>> + *	Revision: 3.06
>> + *	Issue Date: 2/12/2015 (latest release)
>> + *	Link: http://support.amd.com/TechDocs/49125_15h_Models_30h-3Fh_BKDG.pdf
>> + *
>> + *	Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 15h
>> + *	       Models 60h-6Fh Processors
>> + *	AMD publication #: 50742
>> + *	Revision: 3.01
>> + *	Issue Date: 7/23/2015 (latest release)
>> + *	Link: http://support.amd.com/TechDocs/50742_15h_Models_60h-6Fh_BKDG.pdf
>> + *
>> + *	Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 16h
>> + *	       Models 00h-0Fh Processors
>> + *	AMD publication #: 48751
>> + *	Revision: 3.03
>> + *	Issue Date: 2/23/2015 (latest release)
>> + *	Link: http://support.amd.com/TechDocs/48751_16h_bkdg.pdf
>> + *
> You can add those to an amd64_edac section of Documentation/edac.txt.

Okay, I'll look into that.

> I want to keep header files as clean as possible. Copyright updates are
> fine but everything history-like and unrelated to functionality should
> go somewhere else, if at all.
>
>
Shall I send a V2 of this patch to update copyrights and remove the 
changelogs alone?
(I can meld it with patch 2/3 too if you prefer..)

And I can take up the Documentation work as a separate patch..

Thanks,
-Aravind.


  reply	other threads:[~2015-09-17 14:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 20:53 [PATCH 0/3] Updates to amd64_edac and ghes_edac Aravind Gopalakrishnan
2015-09-16 20:53 ` [PATCH 1/3] EDAC, ghes_edac: Remove redundant memory_type array Aravind Gopalakrishnan
2015-09-24  9:24   ` Borislav Petkov
2015-09-16 20:53 ` [PATCH 2/3] EDAC, amd64_edac: Extend scrub rate programmability feature for F15hM60h Aravind Gopalakrishnan
2015-09-24  9:18   ` Borislav Petkov
2015-09-24 16:15     ` Aravind Gopalakrishnan
2015-09-24 16:33       ` Borislav Petkov
2015-09-24 16:42         ` Aravind Gopalakrishnan
2015-09-16 20:53 ` [PATCH 3/3] EDAC, amd64_edac: Update copyright and documentation info Aravind Gopalakrishnan
2015-09-17  7:43   ` Borislav Petkov
2015-09-17 14:35     ` Aravind Gopalakrishnan [this message]
2015-09-17 15:24       ` Borislav Petkov
2015-09-17 15:33         ` Aravind Gopalakrishnan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55FACFAD.4010706@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=bp@alien8.de \
    --cc=dougthompson@xmission.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox