From: Masoud Sharbiani <masouds@masoud.ir>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] hexdigits definition consolidation [RESEND2]
Date: Thu, 06 Oct 2005 15:42:26 +0000 [thread overview]
Message-ID: <20051006154226.GA1546@masoud.ir> (raw)
In-Reply-To: <20051005201210.GA27788@masoud.ir>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Thu, Oct 06, 2005 at 01:21:25AM +0400, Alexey Dobriyan wrote:
> On Wed, Oct 05, 2005 at 04:12:11PM -0400, Masoud Sharbiani wrote:
> > On Wed, Oct 05, 2005 at 11:25:33AM -0600, Matthew Wilcox wrote:
> > --- linux-2.6.clean/arch/cris/arch-v10/kernel/kgdb.c
> > +++ linux-2.6.patched/arch/cris/arch-v10/kernel/kgdb.c
>
> Please, add "-p" to your diff(1) flags. It'd sometimes make reviewing
> much easier.
>
> > @@ -557,8 +556,8 @@
> > char *sd;
> > int x = 0;
> >
> > - for (s1 = (char*)s; (sd = gdb_cris_memchr(hexchars, *s1, base)) != NULL; ++s1)
> > - x = x * base + (sd - hexchars);
> > + for (s1 = (char*)s; (sd = gdb_cris_memchr(small_digits, *s1, base)) != NULL; ++s1)
> > + x = x * base + (sd - small_digits);
> >
> > if (endptr)
> > {
>
> simple_strtol()
I think the reason that they have reimplemented these is that they want to have a separate function to avoid single stepping into the library functions and thus failing the kgdb. Same thing goes for reimplementations of strlen and other library functions in the same file.
cheers,
Masoud
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-10-06 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:12 [KJ] hexdigits definition consolidation [RESEND2] Masoud Sharbiani
2005-10-05 21:21 ` Alexey Dobriyan
2005-10-05 22:22 ` Matthew Wilcox
2005-10-06 15:42 ` Masoud Sharbiani [this message]
2005-10-06 20:28 ` [KJ] hexdigits definition consolidation [RESEND3] Masoud Sharbiani
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=20051006154226.GA1546@masoud.ir \
--to=masouds@masoud.ir \
--cc=kernel-janitors@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 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.