From: Borislav Petkov <bp@alien8.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] x86/microcode: Silence a static checker warning
Date: Thu, 24 Aug 2017 21:12:05 +0000 [thread overview]
Message-ID: <20170824211205.jpvmzzrm72vcb4xf@pd.tnic> (raw)
In-Reply-To: <20170824210847.hypvvpzf5pjhppyt@mwanda>
On Fri, Aug 25, 2017 at 12:08:47AM +0300, Dan Carpenter wrote:
> Sure. But the point is the same... The "p" is an error pointer at the
> end of the function.
Of course, that's why I'm still trying to find a solution. I'm just not
happy with what the ones we have now. I'll think about it more tomorrow,
on a clear head.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-08-24 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:44 [PATCH] x86/microcode/intel: Silence a static checker warning Dan Carpenter
2017-08-22 21:13 ` Borislav Petkov
2017-08-24 20:15 ` [PATCH v2] x86/microcode: " Dan Carpenter
2017-08-24 20:47 ` Borislav Petkov
2017-08-24 20:55 ` Dan Carpenter
2017-08-24 20:58 ` Borislav Petkov
2017-08-24 21:08 ` Dan Carpenter
2017-08-24 21:12 ` Borislav Petkov [this message]
2017-08-25 9:06 ` Borislav Petkov
2017-08-25 9:12 ` Dan Carpenter
2017-08-25 9:14 ` Borislav Petkov
2017-08-25 10:04 ` [PATCH] x86/microcode/intel: Improve microcode patches saving flow Borislav Petkov
2017-08-25 10:40 ` walter harms
2017-08-25 11:41 ` Borislav Petkov
2017-08-24 21:02 ` [PATCH v2] x86/microcode: Silence a static checker warning Joe Perches
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=20170824211205.jpvmzzrm72vcb4xf@pd.tnic \
--to=bp@alien8.de \
--cc=dan.carpenter@oracle.com \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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