From: Blaisorblade <blaisorblade@yahoo.it>
To: jdike@addtoit.com, Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/10] UML - compile fixes
Date: Sat, 29 Jan 2005 00:59:50 +0100 [thread overview]
Message-ID: <200501290059.51646.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050128141028.1586e7a9.akpm@osdl.org>
On Friday 28 January 2005 23:10, Andrew Morton wrote:
> Blaisorblade <blaisorblade@yahoo.it> wrote:
> > On Monday 17 January 2005 08:27, Andrew Morton wrote:
> > > Jeff Dike <jdike@addtoit.com> wrote:
> > > > This fixes some warnings, and changes the system call table so that
> > > > it will compile in -linus, where the vperf system calls are not yet
> > > > merged.
> > >
> > > methinks we already fixed this.
> > >
> > > > Signed-off-by: Jeff Dike <jdike@addtoit.com>
> >
> > No, incorrect, this is not applied, current bitkeeper snapshots don't
> > compile for this reason too.
> >
> > Jeff, I think you should resend the patch anyway.
>
> I don't know what this is about.
Yes, it was from some days ago... so I guess either I or Jeff will have to
resend it...
Andrew, when do you plan to release 2.6.11?
Jeff, you should send your queued fixes, and also resend this one (indeed, it
was not applied). If I find the time I'll select the interesting ones and
send them (with a mail to request their prompt merge).
> The only UML patch I have pending is
>
> uml-kconfig_arch-little-cleanup-to-merge-before-2611.patch
Ok, please merge it ASAP (as the title suggests).
> From: blaisorblade@yahoo.it
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
prev parent reply other threads:[~2005-01-29 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 5:56 Jeff Dike
[not found] ` <200501281827.14366.blaisorblade@yahoo.it>
[not found] ` <20050128141028.1586e7a9.akpm@osdl.org>
2005-01-28 23:59 ` Blaisorblade [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=200501290059.51646.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@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 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®