From: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
To: Borislav Petkov <bp@suse.de>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/vm86: fix compilation warning on a unused variable
Date: Sun, 12 Feb 2017 23:20:07 -0500 [thread overview]
Message-ID: <20170212232007.42aa5874@blatinox-arch> (raw)
In-Reply-To: <20170212140155.yno3cxcq4hifc6gf@pd.tnic>
On Sun, 12 Feb 2017 15:01:55 +0100
Borislav Petkov <bp@suse.de> wrote:
> On Fri, Dec 16, 2016 at 11:19:16PM -0500, Jérémy Lefaure wrote:
> > I don't know why gcc raises a warning on that even if it is not used.
> > Anyway, I'm sure that the warning is reproducible. Both of your
> > solutions fix the issue.
>
> I still see the warning here. You wanna choose one solution, write a
> proper patch and send it out?
>
I am not an expert in linux patch process but I think that as Kirill
wrote the patch, he should be the author of the patch and me I should
be in the "Reported-by" tag, isn't it ?
Regards,
Jérémy
next prev parent reply other threads:[~2017-02-13 4:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 4:38 [PATCH] x86/vm86: fix compilation warning on a unused variable Jérémy Lefaure
2016-12-08 8:33 ` Borislav Petkov
2016-12-08 17:51 ` Jérémy Lefaure
2016-12-08 10:50 ` Kirill A. Shutemov
2016-12-08 11:44 ` Kirill A. Shutemov
2016-12-08 18:25 ` Jérémy Lefaure
2016-12-12 14:52 ` Kirill A. Shutemov
2016-12-17 4:19 ` Jérémy Lefaure
2017-02-12 14:01 ` Borislav Petkov
2017-02-13 4:20 ` Jérémy Lefaure [this message]
2017-02-13 10:03 ` Borislav Petkov
2017-02-13 12:52 ` [PATCH] x86/vm86: fix unused variable warning if THP is disabled Kirill A. Shutemov
2017-02-13 15:49 ` Thomas Gleixner
2017-02-13 17:47 ` Borislav Petkov
2017-02-13 18:07 ` [tip:x86/urgent] x86/vm86: Fix " tip-bot for Kirill A. Shutemov
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=20170212232007.42aa5874@blatinox-arch \
--to=jeremy.lefaure@lse.epita.fr \
--cc=bp@suse.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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