From: Valdis.Kletnieks@vt.edu
To: Pekka Enberg <penberg@kernel.org>
Cc: "Jesper Juhl" <jj@chaosbits.net>,
"Randy Dunlap" <rdunlap@xenotime.net>,
"Arnaud Lacombe" <lacombar@gmail.com>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Raghavendra D Prabhu" <rprabhu@wnohang.net>,
linux-kbuild@vger.kernel.org,
"Nir Tzachar" <nir.tzachar@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Avoid Wunused-but-set warning
Date: Tue, 12 Jul 2011 20:35:12 -0400 [thread overview]
Message-ID: <32171.1310517312@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 11 Jul 2011 08:55:19 +0300." <CAOJsxLHzXV3MDHH+83iwxaUtO=931Bmq1JRzS=MQx=6wa-wi2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
On Mon, 11 Jul 2011 08:55:19 +0300, Pekka Enberg said:
> The definitions in SubmittingPatches are not hard rules and are, in
> fact, out of date. See Documentation/development-process/5.Posting for
> alternative definitions:
>
> - Acked-by: indicates an agreement by another developer (often a
> maintainer of the relevant code) that the patch is appropriate for
> inclusion into the kernel.
>
> and
>
> - Reviewed-by: the named developer has reviewed the patch for correctness;
> see the reviewer's statement in Documentation/SubmittingPatches for more
> detail.
Unfortunately, SubmittingPatches says:
By offering my Reviewed-by: tag, I state that:
(a) I have carried out a technical review of this patch to
evaluate its appropriateness and readiness for inclusion into
the mainline kernel.
(b) Any problems, concerns, or questions relating to the patch
have been communicated back to the submitter. I am satisfied
with the submitter's response to my comments.
(c) While there may be things that could be improved with this
submission, I believe that it is, at this time, (1) a
worthwhile modification to the kernel, and (2) free of known
issues which would argue against its inclusion.
(d) While I have reviewed the patch and believe it to be sound, I
do not (unless explicitly stated elsewhere) make any
warranties or guarantees that it will achieve its stated
purpose or function properly in any given situation.
and often, I'm only comfortable stating (b) - often, I'd like to *disavow* both
(a) and (c)(1) - I usually *don't* do a tech review, and may have no opinion as
to whether it's "cooked" enough to be included. Also, usually, the only "known
issue" from (c)(2) is the one thing I commented on for part (b)...
Comments-Addressed-Acked: anybody? :)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-07-13 0:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 16:24 Raghavendra D Prabhu
2011-07-10 16:16 ` Américo Wang
2011-07-10 16:24 ` Arnaud Lacombe
2011-07-10 16:28 ` Pekka Enberg
2011-07-10 16:49 ` Arnaud Lacombe
2011-07-10 16:51 ` Américo Wang
2011-07-10 17:22 ` Arnaud Lacombe
2011-07-10 17:24 ` Pekka Enberg
2011-07-10 18:02 ` Randy Dunlap
2011-07-10 22:56 ` Jesper Juhl
2011-07-10 23:07 ` Randy Dunlap
2011-07-10 23:21 ` Jesper Juhl
2011-07-10 23:53 ` Randy Dunlap
2011-07-11 5:09 ` Mark Brown
2011-07-11 17:11 ` Randy Dunlap
2011-07-11 22:42 ` Mark Brown
2011-07-13 1:15 ` Américo Wang
2011-07-13 2:21 ` Arnaud Lacombe
2011-07-13 12:16 ` Pekka Enberg
2011-07-11 20:32 ` Jesper Juhl
2011-07-11 5:55 ` Pekka Enberg
2011-07-11 20:37 ` Jesper Juhl
2011-07-13 0:35 ` Valdis.Kletnieks [this message]
2011-07-13 0:55 ` Randy Dunlap
2011-07-10 16:49 ` Américo Wang
2011-07-13 11:39 ` Michal Marek
2011-07-18 19:00 ` Arnaud Lacombe
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=32171.1310517312@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=jj@chaosbits.net \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.tzachar@gmail.com \
--cc=penberg@kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rprabhu@wnohang.net \
--cc=xiyou.wangcong@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®