From: Al Viro <viro@ftp.linux.org.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: [uml-devel] Re: UML/2.6.14-rc3 doesn't work fixes
Date: Sun, 2 Oct 2005 18:32:03 +0100 [thread overview]
Message-ID: <20051002173203.GQ7992@ftp.linux.org.uk> (raw)
In-Reply-To: <200510021350.29959.blaisorblade@yahoo.it>
On Sun, Oct 02, 2005 at 01:50:28PM +0200, Blaisorblade wrote:
> On Sunday 02 October 2005 13:38, Al Viro wrote:
> > On Sun, Oct 02, 2005 at 12:13:39PM +0200, Blaisorblade wrote:
> > > The patch in Al Viro's:
>
> > > ecba97d4aacf4e80c56eb73e39af0369cb8539a4
>
> > > messed up UML (in particular skas0, which doesn't boot any more - or
> > > maybe it boots one out of 10 times).
>
> > > Btw: did Al CC you on it, at least?
>
> > Yes. Moreover, that had also been done two weeks ago when original version
> > of patch had been sent for review to Jeff. Who'd caught that one and other
> > bugs and sent the fixed variant back. At which point I'd fscked up the
> > merge.
>
> Ok, you're excused... now, however, I still think that this should be
> postponed to 2.6.15, since it's a (very nice, indeed) cleanup and we're
> nearing completion.
>
> Al, did you receive my "[PATCH 5/5] uml: remove empty hostfs_truncate method"?
> What about that?
What about that? Obvious patch that got no objections from anybody and
AFAICS got in -rc3:
; git-whatchanged fs/hostfs/hostfs_kern.c|head
diff-tree daa35edc0a967d1f77c2e2c1346f57d04371487a (from bd948057357db5febfe64cf7a9ef11d7e347ffec)
Author: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Date: Fri Sep 30 11:59:01 2005 -0700
[PATCH] uml: remove empty hostfs_truncate method
Calling truncate() on hostfs spits a kernel warning "Something isn't
implemented here", but it still works fine.
Indeed, hostfs i_op->truncate doesn't do anything. But hostfs_setattr() ->
;
Judging by Signed-off-by it looks like a -mm -> Linus merge...
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-10-02 17:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 10:13 [uml-devel] UML/2.6.14-rc3 doesn't work fixes Blaisorblade
2005-10-02 11:38 ` [uml-devel] " Al Viro
2005-10-02 11:50 ` Blaisorblade
2005-10-02 17:32 ` Al Viro [this message]
2005-10-02 17:45 ` Blaisorblade
2005-10-02 15:51 ` Jeff Dike
2005-10-02 16:55 ` Al Viro
2005-10-02 18:01 ` Blaisorblade
2005-10-02 18:37 ` Al Viro
2005-10-02 20:54 ` Al Viro
2005-10-03 18:30 ` Blaisorblade
2005-10-03 23:38 ` Al Viro
2005-10-04 10:26 ` Blaisorblade
2005-10-04 11:09 ` Al Viro
2005-10-04 11:19 ` Blaisorblade
2005-10-04 11:55 ` Al Viro
2005-10-04 12:09 ` Blaisorblade
2005-10-04 17:09 ` Al Viro
2005-10-04 17:14 ` Al Viro
2005-10-04 17:18 ` Al Viro
2005-10-04 17:24 ` Al Viro
2005-10-04 17:28 ` Al Viro
2005-10-09 19:16 ` Blaisorblade
2005-10-03 18:56 ` Blaisorblade
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=20051002173203.GQ7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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.