mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: frank.rowand@am.sony.com
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Thiago Farina <tfransosi@gmail.com>,
	linux list <linux-kernel@vger.kernel.org>
Subject: Re: acked-by meaning
Date: Tue, 13 Nov 2012 23:38:01 +0100	[thread overview]
Message-ID: <2562599.USXBfge9I9@vostro.rjw.lan> (raw)
In-Reply-To: <50A2C5C3.8040804@am.sony.com>

On Tuesday, November 13, 2012 02:12:19 PM Frank Rowand wrote:
> On 11/11/12 19:47, Randy Dunlap wrote:
> > On 11/11/2012 05:40 PM, Thiago Farina wrote:
> > 
> >> Hi,
> >>
> >> What is the meaning of 'Acked-by:' line? Is the same of LGTM? How it
> >> differs from 'Reviewed-by:'?
> > 
> 
> > Reviewed-by: is stronger than Acked-by:.
> > If someone replies with Reviewed-by, they also accept some
> > responsibility for fixing any problems that the patch might
> > introduce after it is merged.
> 
> I haven't found a "responsibility for fixing any problems" in the
> references provided below.  Can you help me out by pointing
> to a specific sentence or another reference?

"Reviewed-by" informs the maintainer of the relevant subsystem that the
reviewer has spent time to go through the patch and understand what it
does in detail.  It also implies that the reviewer has no objections against
the patch.

The maintainer can use this information when deciding whether or not to
apply the patch, possibly without spending as much time on it as would be
necessary otherwise.

> > Acked-by just means agreement with the patch.

Actually, the meaning of "Acked-by" depends on who gives it.

If the patch touches multiple subsystems and their maintainers "ack" it,
they inform each other that they have no objections against it and, from their
perspective, it can be merged if any one of them wants to take it.  So in that
particular case it's rather strong.

On the other hand, if the "ack" is given by someone who's not a maintainer,
the meaning of it is pretty much the same as for a "like" on Facebook. :-)

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      parent reply	other threads:[~2012-11-13 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  1:40 Thiago Farina
2012-11-12  3:47 ` Randy Dunlap
2012-11-13 22:12   ` Frank Rowand
2012-11-13 22:31     ` Randy Dunlap
2012-11-13 22:38     ` Rafael J. Wysocki [this message]

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=2562599.USXBfge9I9@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tfransosi@gmail.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®