From: David Miller <davem@davemloft.net>
To: bunk@kernel.org
Cc: a.beregalov@gmail.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: sparc64: build failure at sys_sparc32.c
Date: Thu, 07 Aug 2008 05:53:37 +0000 [thread overview]
Message-ID: <20080806.225337.73678483.davem@davemloft.net> (raw)
In-Reply-To: <20080804140532.GI6088@cs181140183.pp.htv.fi>
From: Adrian Bunk <bunk@kernel.org>
Date: Mon, 4 Aug 2008 17:05:32 +0300
> The only platforms that do their own stuff instead of using the
> functions from kernel/uid16.c are sparc64 and s390.
>
> Is there any reason why sparc64 has it's own functions?
Thanks for pointing it out, I'll take advantage of those helper
routines.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: bunk@kernel.org
Cc: a.beregalov@gmail.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: sparc64: build failure at sys_sparc32.c
Date: Wed, 06 Aug 2008 22:53:37 -0700 (PDT) [thread overview]
Message-ID: <20080806.225337.73678483.davem@davemloft.net> (raw)
In-Reply-To: <20080804140532.GI6088@cs181140183.pp.htv.fi>
From: Adrian Bunk <bunk@kernel.org>
Date: Mon, 4 Aug 2008 17:05:32 +0300
> The only platforms that do their own stuff instead of using the
> functions from kernel/uid16.c are sparc64 and s390.
>
> Is there any reason why sparc64 has it's own functions?
Thanks for pointing it out, I'll take advantage of those helper
routines.
next prev parent reply other threads:[~2008-08-07 5:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 6:59 sparc64: build failure at sys_sparc32.c Alexander Beregalov
2008-07-29 6:59 ` Alexander Beregalov
2008-07-29 7:12 ` David Miller
2008-07-29 7:12 ` David Miller
2008-07-29 8:38 ` Alexander Beregalov
2008-07-29 8:38 ` Alexander Beregalov
2008-08-04 1:19 ` David Miller
2008-08-04 1:19 ` David Miller
2008-08-04 14:05 ` Adrian Bunk
2008-08-04 14:05 ` Adrian Bunk
2008-08-07 5:53 ` David Miller [this message]
2008-08-07 5:53 ` David Miller
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=20080806.225337.73678483.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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.