From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] twd: Don't set CLOCK_EVT_FEAT_C3STOP unconditionally
Date: Thu, 8 Oct 2015 20:37:23 +0200 [thread overview]
Message-ID: <5616B7E3.50507@free.fr> (raw)
In-Reply-To: <20151008182254.GJ32532@n2100.arm.linux.org.uk>
On 08/10/2015 20:22, Russell King - ARM Linux wrote:
> On Thu, Oct 08, 2015 at 08:16:24PM +0200, Mason wrote:
>> On 08/10/2015 19:43, Russell King - ARM Linux wrote:
>>> On Thu, Oct 08, 2015 at 07:38:53PM +0200, Mason wrote:
>>>> On 08/10/2015 19:16, Mark Rutland wrote:
>>>>> Otherwise this looks ok. If you can respin with the above wording, and
>>>>> s/twd-never-stops/always-on/ in the patch, you can add:
>>>>>
>>>>> Acked-by: Mark Rutland <mark.rutland@arm.com>
>>>>
>>>> Wouldn't you feel like going all-in and Signing-off? ;-)
>>>
>>> Then I'd reject it, because it would be wrong.
>>>
>>> Documentation/SubmittingPatches: [snip]
>>
>> Could someone explain the difference between Acked-by and
>> Reviewed-by?
>
> Again, I could quote from the above file, but you already have a copy
> of it locally, so you could just read that version instead. Section 13.
Acked-by: [...] is a record that the acker has at least
reviewed the patch and has indicated acceptance.
Reviewed-by: indicates that the patch has been reviewed and
found acceptable according to the Reviewer's Statement
IIUC Acked-by is stronger than Reviewed-by?
Regards.
next prev parent reply other threads:[~2015-10-08 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:58 [PATCH] twd: Don't set CLOCK_EVT_FEAT_C3STOP unconditionally Marc Gonzalez
2015-10-05 9:17 ` [PATCH v2] " Marc Gonzalez
2015-10-05 9:22 ` Linus Walleij
2015-10-05 9:50 ` [PATCH v3] " Marc Gonzalez
2015-10-05 10:35 ` Mark Rutland
2015-10-05 11:53 ` [PATCH v4] " Marc Gonzalez
2015-10-05 16:37 ` Marc Gonzalez
2015-10-07 12:14 ` Marc Gonzalez
2015-10-08 17:16 ` Mark Rutland
2015-10-08 17:38 ` Mason
2015-10-08 17:43 ` Russell King - ARM Linux
2015-10-08 18:16 ` Mason
2015-10-08 18:22 ` Russell King - ARM Linux
2015-10-08 18:37 ` Mason [this message]
2015-10-08 17:57 ` Mark Rutland
2015-10-08 18:25 ` Mason
2015-10-08 18:34 ` Mark Rutland
2015-10-09 9:29 ` Marc Gonzalez
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=5616B7E3.50507@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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.