From: Frederik Deweerdt <deweerdt@free.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] removing R/W semaphore content from standard semaphore.h
Date: Fri, 16 Feb 2007 21:45:18 +0000 [thread overview]
Message-ID: <20070217213142.GD32060@slug> (raw)
In-Reply-To: <Pine.LNX.4.64.0702161405230.3503@CPE00045a9c397f-CM001225dbafb6>
On Fri, Feb 16, 2007 at 03:23:25PM -0500, Robert P. J. Day wrote:
> On Fri, 16 Feb 2007, Randy Dunlap wrote:
>
> > On Fri, 16 Feb 2007 14:10:19 -0500 (EST) Robert P. J. Day wrote:
> >
> > > if someone could clarify this, i'd appreciate it. i recently
> > > submitted a patch that removed any inclusions of "linux/rwsem.h"
> > > from the semaphore.h files, since standard semaphore header files
> > > should *not* be pulling in any R/W sem stuff -- the R/W semaphores
> > > now have their own rwsem.h header file.
> >
> > My turn for a question: when you make such a change that affects
> > many $ARCH (arch/*), do you build multiple architectures to see if
> > the patch causes any problems?
>
> no, since i have access only to an x86 platform.
In case you'd want to cross-compile, eldk
(http://www.denx.de/wiki/DULG/ELDK) has some pre-built toolchains for
x86 to arm, mips and ppc.
Regards,
Frederik
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2007-02-16 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 19:10 [KJ] removing R/W semaphore content from standard semaphore.h files Robert P. J. Day
2007-02-16 19:59 ` [KJ] removing R/W semaphore content from standard semaphore.h Randy Dunlap
2007-02-16 20:23 ` Robert P. J. Day
2007-02-16 20:28 ` Robert P. J. Day
2007-02-16 20:33 ` Randy Dunlap
2007-02-16 20:44 ` Robert P. J. Day
2007-02-16 21:45 ` Frederik Deweerdt [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=20070217213142.GD32060@slug \
--to=deweerdt@free.fr \
--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.