mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@parisc-linux.org>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, carlos@parisc-linux.org, willy@parisc-linux.org,
	linux-kernel@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [PATCH 1/5] Add generic compat_siginfo_t
Date: Tue, 10 Jan 2006 10:01:41 -0500	[thread overview]
Message-ID: <20060110150141.GE28306@quicksilver.road.mcmartin.ca> (raw)
In-Reply-To: <20060109141355.GA22296@lst.de>

On Mon, Jan 09, 2006 at 03:13:55PM +0100, Christoph Hellwig wrote:
> -mm already has a much better implementation for compat_sys_timer_create
> that doesn't require all the sigevent churn in this patch (which btw
> doesn't seem to be mentioned in the changelog at all).  

Ok, I see it in -mm now, and it does seem to be nicer code, I'll
try it out on parisc64.

> But even with
> that remove there seems to be a lot of useless ifdef and indirection
> in this patch.  

I agree, I'm really just trying to shepard this home so we don't have
to maintain it out of tree. I'm not overly attached to the code, if
I can make parisc64 work with your compat signal bits, I'll be
just as happy.

The one thing from this patchset I'd like to keep is the is_compat_task()
as it does provide nice cleanups 

Cheers, Kyle

> Over the next days I'll send out my generic compat
> singal bits which don't require all this, but otoh require every
> architecture to supply helpers.  If you can make those generic without
> all the ifdef an additional header bits all power to you!

  reply	other threads:[~2006-01-10 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 19:37 Kyle McMartin
2006-01-09 14:13 ` [parisc-linux] " Christoph Hellwig
2006-01-10 15:01   ` Kyle McMartin [this message]
2006-01-10 15:15     ` Christoph Hellwig
2006-01-10 16:39       ` Matthew Wilcox
2006-01-11  3:46         ` Stephen Rothwell
2006-01-11 17:27           ` Kyle McMartin

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=20060110150141.GE28306@quicksilver.road.mcmartin.ca \
    --to=kyle@parisc-linux.org \
    --cc=akpm@osdl.org \
    --cc=carlos@parisc-linux.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@parisc-linux.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

all inboxes | Powered by JetHome®