From: Michael Neuling <mikey@neuling.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH] Documentation: fix getdelays.c example -l option and segv
Date: Fri, 10 Aug 2007 18:53:47 +1000 [thread overview]
Message-ID: <20368.1186736027@neuling.org> (raw)
In-Reply-To: <20070810013306.beaed37e.akpm@linux-foundation.org>
> > Fix a couple of minor issues with the getdelays.c example code.
>
> What issues?
-l option (loop) doesn't work and it seg faults in print_delayacct.
Mikey
next prev parent reply other threads:[~2007-08-10 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 8:24 [PATCH] Documentation: fix getdelays.c example -l option and segv Michael Neuling
2007-08-10 8:33 ` Andrew Morton
2007-08-10 8:53 ` Michael Neuling [this message]
2007-08-15 7:02 ` Balbir Singh
2007-08-15 8:13 ` Michael Neuling
2007-08-15 11:20 ` Balbir Singh
2007-08-15 12:00 ` Michael Neuling
2007-08-15 12:08 ` [PATCH] Documentation: fix getdelays.c printf bug Michael Neuling
2007-08-15 13:15 ` Balbir Singh
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=20368.1186736027@neuling.org \
--to=mikey@neuling.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.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