From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: A comment on the 2.5.29 patch
Date: Thu, 08 Aug 2002 04:37:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905924@msgid-missing> (raw)
>>>>> On Thu, 8 Aug 2002 13:38:03 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Hi David,
Peter> The change to drivers/char/mem.c doesn't look right --- it forces a
Peter> successful system call even when there's been an error.
Peter> --- a/drivers/char/mem.c Thu Aug 1 01:08:13 2002
Peter> +++ b/drivers/char/mem.c Thu Aug 1 01:08:13 2002
Peter> @@ -518,6 +518,7 @@
Peter> default:
Peter> ret = -EINVAL;
Peter> }
Peter> + force_successful_syscall_return();
Peter> unlock_kernel();
Peter> return ret;
Peter> }
Peter> Surely that should only be when ret != -EINVAL ??? You could move it
Peter> inside the switch, although that's ugly.
Yes, that's a bug, probably due to a bad merge. Please understand
that the 2.5.29 is works-in-progress; there really is a large number
of outstanding things, so don't expect everything to be all-right.
Peter> I can't see the point of moving the declaration of extern irq_desc_t
Peter> irq_desc [NR_IRQS]; from include/linux/irq.h into asm-i386/hw_irq.,
The idea is simple: remove irq_desc[] and replace it with an irq_desc()
macro, so that platforms have the option to implement the table any way
they see fit (e.g., distributed across NUMA nodes).
Peter> And my remaining comment is that I'm not sure why the changes to the
Peter> softirq() names were made. A rose by any name would smell as sweet...
Specifics please? There are no just-for-fun renames, but again, it
could be a bad merge or something along those lines.
--david
next reply other threads:[~2002-08-08 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 4:37 David Mosberger [this message]
2002-08-08 5:08 ` [Linux-ia64] Re: A comment on the 2.5.29 patch Peter Chubb
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=marc-linux-ia64-105590701905924@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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