public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, davidm@snapgear.com,
	linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] Termio userspace access error handling
Date: Tue, 09 Nov 2004 10:31:59 +0000	[thread overview]
Message-ID: <12145.1099996319@redhat.com> (raw)
In-Reply-To: <20041108143409.79bf7fd8.akpm@osdl.org>


Andrew Morton <akpm@osdl.org> wrote:
> > The attached patch creates a generic set of termio userspace access
> > functions with proper error handling. None of the current archs check for
> > errors in this case.
> 
> Why are they inlined?

Each function is used a single time. Also they can't just be integrated into
the calling functions though because some archs need to handle them
differently.

David

      reply	other threads:[~2004-11-09 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 14:32 [PATCH] Termio userspace access error handling dhowells
2004-11-08 22:34 ` Andrew Morton
2004-11-09 10:31   ` David Howells [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=12145.1099996319@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=davidm@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=uclinux-dev@uclinux.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