public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] perf Makefile: Correct the message in feature-libnuma checking.
Date: Mon, 2 Dec 2013 09:26:20 -0300	[thread overview]
Message-ID: <20131202122620.GA2371@ghostprotocols.net> (raw)
In-Reply-To: <529BF100.2080504@hurleysoftware.com>

Em Sun, Dec 01, 2013 at 09:31:28PM -0500, Peter Hurley escreveu:
> On 12/02/2013 10:26 AM, Dongsheng Yang wrote:
> >The package required for numa is named numactl-devel in Fedora or RHEL,
> >and libnuma-devel in OpenSuSE, and libnuma-dev in Ubuntu. This patch
> >corrects the package name in warning message in feature-libnuma checking.
> 
> Thanks (and thanks for correcting the other lib names).

I'll take this as an:

Acked-by: Peter Hurley <peter@hurleysoftware.com>

Ok?

Please read Documentation/SubmittingPatches, relevant part:

------------------------------------------------------------
13) When to use Acked-by: and Cc:

The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery path.

If a person was not directly involved in the preparation or handling of a
patch but wishes to signify and record their approval of it then they can
arrange to have an Acked-by: line added to the patch's changelog.

Acked-by: is often used by the maintainer of the affected code when that
maintainer neither contributed to nor forwarded the patch.

Acked-by: is not as formal as Signed-off-by:.  It is a record that the acker
has at least reviewed the patch and has indicated acceptance.  Hence patch
mergers will sometimes manually convert an acker's "yep, looks good to me"
into an Acked-by:.

Acked-by: does not necessarily indicate acknowledgement of the entire patch.
For example, if a patch affects multiple subsystems and has an Acked-by: from
one subsystem maintainer then this usually indicates acknowledgement of just
the part which affects that maintainer's code.  Judgement should be used here.
When in doubt people should refer to the original discussion in the mailing
list archives.

If a person has had the opportunity to comment on a patch, but has not
provided such comments, you may optionally add a "Cc:" tag to the patch.
This is the only tag which might be added without an explicit action by the
person it names.  This tag documents that potentially interested parties
have been included in the discussion
------------------------------------------------------------
 
Thanks,

- Arnaldo

  reply	other threads:[~2013-12-02 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1385759152-19752-1-git-send-email-yangds.fnst@cn.fujitsu.com>
     [not found] ` <20131129181417.GA9876@ghostprotocols.net>
2013-12-02 14:11   ` [PATCH] perf Makefile: Correct the message in feature-libnuma checking Dongsheng Yang
2013-12-02  1:33     ` Peter Hurley
2013-12-02 14:49       ` Dongsheng Yang
2013-12-02 15:26         ` [PATCH V2] " Dongsheng Yang
2013-12-02  2:31           ` Peter Hurley
2013-12-02 12:26             ` Arnaldo Carvalho de Melo [this message]
2013-12-02 12:45               ` Peter Hurley
2013-12-04 15:41           ` [tip:perf/core] perf tools: " tip-bot for Dongsheng Yang

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=20131202122620.GA2371@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=yangds.fnst@cn.fujitsu.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