From: Jarek Poplawski <jarkao2@o2.pl>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] detect & print stack overruns at oops time
Date: Wed, 5 Sep 2007 16:29:08 +0200 [thread overview]
Message-ID: <20070905142908.GC1938@ff.dom.local> (raw)
In-Reply-To: <20070905141923.GB1938@ff.dom.local>
On Wed, Sep 05, 2007 at 04:19:23PM +0200, Jarek Poplawski wrote:
...
> again, and there is choice or risk, then - no question & all correct.
Should be:
again, and there is no choice or risk, then - no question & all correct.
Jarek P.
prev parent reply other threads:[~2007-09-05 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 5:28 [RFC][PATCH] detect & print stack overruns at oops time Eric Sandeen
2007-08-31 16:32 ` Randy Dunlap
2007-08-31 16:36 ` Eric Sandeen
2007-09-05 9:30 ` Jarek Poplawski
2007-09-05 12:51 ` Eric Sandeen
2007-09-05 14:19 ` Jarek Poplawski
2007-09-05 14:29 ` Jarek Poplawski [this message]
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=20070905142908.GC1938@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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