From: Richard Weinberger <richard@nod.at>
To: Manfred Schlaegl <manfred.schlaegl@gmx.at>,
Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-user@lists.sourceforge.net,
Randy Dunlap <rdunlap@infradead.org>,
Daniel Walter <dwalter@google.com>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH] um: Remove unused bp stack-frame pointer
Date: Sat, 18 Oct 2014 16:42:16 +0200 [thread overview]
Message-ID: <54427C48.9050608@nod.at> (raw)
In-Reply-To: <544277C5.9030302@gmx.at>
Am 18.10.2014 um 16:23 schrieb Manfred Schlaegl:
> The pointer to bp stack-frame is no longer used. Removed it.
Good catch!
> This also removes a corresponding compiler-warning.
Which warning exactly?
Thanks,
//richard
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Manfred Schlaegl <manfred.schlaegl@gmx.at>,
Jeff Dike <jdike@addtoit.com>
Cc: Daniel Walter <dwalter@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: Remove unused bp stack-frame pointer
Date: Sat, 18 Oct 2014 16:42:16 +0200 [thread overview]
Message-ID: <54427C48.9050608@nod.at> (raw)
In-Reply-To: <544277C5.9030302@gmx.at>
Am 18.10.2014 um 16:23 schrieb Manfred Schlaegl:
> The pointer to bp stack-frame is no longer used. Removed it.
Good catch!
> This also removes a corresponding compiler-warning.
Which warning exactly?
Thanks,
//richard
next prev parent reply other threads:[~2014-10-18 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 14:23 [PATCH] um: Remove unused bp stack-frame pointer Manfred Schlaegl
2014-10-18 14:42 ` Richard Weinberger [this message]
2014-10-18 14:42 ` Richard Weinberger
2014-10-18 15:12 ` Manfred Schlaegl
2014-10-18 15:12 ` Manfred Schlaegl
2014-10-18 15:19 ` Richard Weinberger
2014-10-18 15:19 ` Richard Weinberger
2014-10-18 15:24 ` Manfred Schlaegl
2014-10-18 15:24 ` Manfred Schlaegl
2014-10-18 15:40 ` Richard Weinberger
2014-10-18 15:40 ` Richard Weinberger
2014-10-19 17:28 ` Manfred Schlaegl
2014-10-19 17:28 ` Manfred Schlaegl
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=54427C48.9050608@nod.at \
--to=richard@nod.at \
--cc=dwalter@google.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred.schlaegl@gmx.at \
--cc=rdunlap@infradead.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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.