From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Borislav Petkov <bp@alien8.de>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-edac@vger.kernel.org, "Tony Luck" <tony.luck@intel.com>,
"James Morse" <james.morse@arm.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Robert Richter" <rric@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC/amd81*1: Remove "\n" from MODULE_AUTHOR
Date: Tue, 28 Mar 2023 21:26:37 +0200 [thread overview]
Message-ID: <ZCM/bUZqQ+hbvZrG@probook> (raw)
In-Reply-To: <20230319192011.GEZBdga+n600nFi/tA@fat_crate.local>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Sun, Mar 19, 2023 at 08:20:11PM +0100, Borislav Petkov wrote:
> On Sun, Jan 29, 2023 at 05:50:54PM +0100, Jonathan Neuschäfer wrote:
[...]
> Wanna fix the other two in the EDAC tree:
>
> drivers/edac/e752x_edac.c:1465:MODULE_AUTHOR("Linux Networx (http://lnxi.com) Tom Zimmerman\n");
> drivers/edac/e7xxx_edac.c:599:MODULE_AUTHOR("Linux Networx (http://lnxi.com) Thayne Harbaugh et al\n"
>
> ?
>
> That macro takes:
>
> /*
> * Author(s), use "Name <email>" or just "Name", for multiple
> * authors use multiple MODULE_AUTHOR() statements/lines.
> */
> #define MODULE_AUTHOR(_author) MODULE_INFO(author, _author)
>
> and not prose.
>
> You can move the prose to the top comment in the respective file, if it
> doesn't contain it yet.
>
> Thx.
Sorry for the late reply. I'm replying now because I saw that you
applied the patch.
I might fix the above if/when I get around to it, but there's currently
no guarantee of that.
Best regards,
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-28 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 16:50 Jonathan Neuschäfer
2023-03-19 19:20 ` Borislav Petkov
2023-03-28 19:26 ` Jonathan Neuschäfer [this message]
2023-03-28 19:40 ` Borislav Petkov
2023-03-28 13:42 ` Borislav Petkov
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=ZCM/bUZqQ+hbvZrG@probook \
--to=j.neuschaefer@gmx.net \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®