From: Qian Cai <cai@lca.pw>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2] powerpc: mute unused-but-set-variable warnings
Date: Tue, 19 Mar 2019 06:21:43 -0400 [thread overview]
Message-ID: <b3e7d016-74ca-aaaa-02e7-39fbc2200013@lca.pw> (raw)
In-Reply-To: <1ffdc5ae-2d5f-6c81-3997-0e6c81c67516@c-s.fr>
On 3/19/19 5:21 AM, Christophe Leroy wrote:
> Is there a reason for resending ? AFAICS, both are identical and still marked
> new in patchwork:
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=76055
>
"RESEND" because of no maintainer response for more than one week.
> Indeed, the resend has an issue in the commit log and fails the checkpatch (a ::
> in Reviewed-by::)
Yes, my bad for a copy-and-paste error.
next prev parent reply other threads:[~2019-03-19 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 22:05 [RESEND PATCH v2] powerpc: mute unused-but-set-variable warnings Qian Cai
2019-03-19 9:21 ` Christophe Leroy
2019-03-19 10:21 ` Qian Cai [this message]
2019-03-20 12:42 ` Michael Ellerman
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=b3e7d016-74ca-aaaa-02e7-39fbc2200013@lca.pw \
--to=cai@lca.pw \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox