From: Borislav Petkov <bp@alien8.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Colin Ian King <colin.king@canonical.com>,
Tony Luck <tony.luck@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
James Morse <james.morse@arm.com>,
linux-edac@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC, sb_edac: remove redundant update of tad_base
Date: Thu, 09 May 2019 14:54:26 +0000 [thread overview]
Message-ID: <20190509145426.GC17053@zn.tnic> (raw)
In-Reply-To: <20190509144650.GG21059@kadam>
On Thu, May 09, 2019 at 05:46:50PM +0300, Dan Carpenter wrote:
> On Thu, May 09, 2019 at 04:41:13PM +0200, Borislav Petkov wrote:
> > Bottom line of what I'm trying to say is, those tags better be useful to
> > the general kernel audience - that means, they should be documented so
> > that people can look them up - or better not be in commit messages at
> > all.
>
> Other people will complain if you don't mention the tool name...
To quote again what I said: "... they should be documented so that
people can look them up... "
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Colin Ian King <colin.king@canonical.com>,
Tony Luck <tony.luck@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
James Morse <james.morse@arm.com>,
linux-edac@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC, sb_edac: remove redundant update of tad_base
Date: Thu, 9 May 2019 16:54:26 +0200 [thread overview]
Message-ID: <20190509145426.GC17053@zn.tnic> (raw)
In-Reply-To: <20190509144650.GG21059@kadam>
On Thu, May 09, 2019 at 05:46:50PM +0300, Dan Carpenter wrote:
> On Thu, May 09, 2019 at 04:41:13PM +0200, Borislav Petkov wrote:
> > Bottom line of what I'm trying to say is, those tags better be useful to
> > the general kernel audience - that means, they should be documented so
> > that people can look them up - or better not be in commit messages at
> > all.
>
> Other people will complain if you don't mention the tool name...
To quote again what I said: "... they should be documented so that
people can look them up... "
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-05-09 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 22:42 [PATCH] EDAC, sb_edac: remove redundant update of tad_base Colin King
2019-05-08 22:42 ` Colin King
2019-05-08 22:48 ` Luck, Tony
2019-05-08 22:48 ` Luck, Tony
2019-05-09 14:13 ` Borislav Petkov
2019-05-09 14:13 ` Borislav Petkov
2019-05-09 14:29 ` Colin Ian King
2019-05-09 14:29 ` Colin Ian King
2019-05-09 14:41 ` Borislav Petkov
2019-05-09 14:41 ` Borislav Petkov
2019-05-09 14:46 ` Dan Carpenter
2019-05-09 14:46 ` Dan Carpenter
2019-05-09 14:54 ` Borislav Petkov [this message]
2019-05-09 14:54 ` Borislav Petkov
2019-05-09 14:55 ` Colin Ian King
2019-05-09 14:55 ` Colin Ian King
2019-05-09 15:01 ` Borislav Petkov
2019-05-09 15:01 ` 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=20190509145426.GC17053@zn.tnic \
--to=bp@alien8.de \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=james.morse@arm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.