From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PID virtualisation snafu
Date: Wed, 18 Jan 2006 07:58:26 -0600 [thread overview]
Message-ID: <20060118135826.GA9743@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20060117161543.GJ19769@parisc-linux.org>
Quoting Matthew Wilcox (matthew@wil.cx):
>
> Are there any web archives of l-k that give out the email address of
> the author?
Regardless, that was me.
> I can tell the author of the virtualisation patches hasn't even tried to
> compile them. Here's one example:
Not only compiled, but on several architectures. Thanks for
catching this. And your point is well taken - these need to be
tested with 'make allmodconfig', since the pid accesses happen
in all sorts of drivers...
thanks,
-serge
prev parent reply other threads:[~2006-01-18 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 16:15 Matthew Wilcox
2006-01-18 13:58 ` Serge E. Hallyn [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=20060118135826.GA9743@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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®