qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Martin Mohring <martin.mohring@opensuse.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/21] Pending linux-user patches
Date: Tue, 16 Jun 2009 19:45:16 +0300	[thread overview]
Message-ID: <f43fc5580906160945m4464e7d9xfe9faa803fe50cd@mail.gmail.com> (raw)
In-Reply-To: <4A37C8BF.5010209@opensuse.org>

On 6/16/09, Martin Mohring <martin.mohring@opensuse.org> wrote:
> Riku Voipio wrote:
>  > On Sun, Jun 14, 2009 at 06:12:06PM +0300, Blue Swirl wrote:
>  >
>  >> On 6/12/09, riku.voipio@iki.fi <riku.voipio@iki.fi> wrote:
>  >>
>  >>> From: Riku Voipio <riku.voipio@iki.fi>
>  >>>
>  >>>  All the things in linux-user tree at the moment:
>  >>>
>  >>>  https://git.maemo.org/projects/qemu/gitweb?p=qemu;a=shortlog;h=refs/heads/linux-user-for-upstream
>  >>>
>  >>>  Since the maemo git hosting regrettably only provides https
>  >>>  transport, you can download the git tree faster if you already
>  >>>  have a git tree:
>  >>>
>  >>>  git clone git://git.sv.gnu.org/qemu.git
>  >>>  cd qemu
>  >>>  git remote add maemo https://git.maemo.org/projects/qemu
>  >>>  git fetch maemo
>  >>>  git checkout -b linux-user maemo/linux-user-for-upstream
>  >>>
>  >>>  This tree is constantly rebased against upstream git HEAD, so avoid basing your
>  >>>  work on this branch.
>  >>>
>  >
>  >
>  >> Constantly? It's already three days old. :-)
>  >>
>  >
>  > More accurate would be "whenever there is updates in the upstream linux-user/
>  > subdir that require rebasing", but that might give some people the impression
>  > that it is actually rabased quite rarely ;-)
>  >
>  >
>  >> Anyway, I pulled the patches with the intention of possibly committing
>  >> them. But it looks some of them are not ready yet.
>  >>
>  >
>  > The "From:" fields were not intended as signed-off-by replacements, but rather
>  > to ensure that the authorship info is not lost. With the current mailer setup
>  > the email header "From:" on the patches sent to the mailing list shows my address,
>  > and I don't want to take anyones credit away.
>  >
>  > I'll have the look at the compiler warning, I didn't see any warnings on my build
>  > env(s) before mailing.
>  >
>
> Is there any chance to accept the bunch of these changes or any reason
>  to reject them? I was told by some maintainers that currently there is
>  no maintainer for user mode anymore. Is this true, and is this the
>  reason? Or is the user mode support "officially" dropped / running out?

After the problems are fixed, I'll commit the fixed ones unless there
are objections.

  reply	other threads:[~2009-06-16 16:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 13:50 [Qemu-devel] [PATCH 00/21] Pending linux-user patches riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 01/21] export mmap_find_vma for shmat riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 02/21] Implement shm* syscalls and fix 64/32bit errors riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 03/21] linux-user: implemented ELF coredump support for ARM target riku.voipio
2009-06-14 15:16   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 04/21] linux-user: added x86 and x86_64 support for ELF coredump riku.voipio
2009-06-14 15:21   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 05/21] linux-user: strace now handles guest strings correctly [v2] riku.voipio
2009-06-14 15:17   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 06/21] Revived GUEST_BASE support for usermode emulation targets [v5] riku.voipio
2009-06-14 15:28   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 07/21] linux-user: fix utimensat riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 08/21] Fix struct termios host - target translation riku.voipio
2009-06-14 15:22   ` Blue Swirl
2009-06-15 15:36     ` Riku Voipio
2009-06-16  8:28       ` Arnaud Patard
2009-06-16  9:34         ` Riku Voipio
2009-06-16 10:01           ` Arnaud Patard
2009-06-12 13:50 ` [Qemu-devel] [PATCH 09/21] Return EOPNOTSUPP instead of ENOSYS for *xattr* syscalls riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 10/21] linux-user: Added IP_ADD_MEMBERSHIP/IP_DROP_MEMBERSHIP flags to setsockopt riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 11/21] linux-user: Added IP_(UN)BLOCK_SOURCE/IP_(ADD|DROP)_SOURCE_MEMBERSHIP " riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 12/21] linux-user: include linux/fs.h riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 13/21] linux-user: support private futexes riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 14/21] add futex wake op riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 15/21] linux-user: update syscall list riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 16/21] linux-user: implement pipe2 [v3] riku.voipio
2009-06-16 21:44   ` Stuart Brady
2009-06-17  2:31     ` Jamie Lokier
2009-06-12 13:50 ` [Qemu-devel] [PATCH 17/21] linux-user: add tee, splice and vmsplice riku.voipio
2009-06-14 15:25   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 18/21] RFC: fix fcntl support in linux-user - new try riku.voipio
2009-06-14 15:15   ` Blue Swirl
2009-06-12 13:50 ` [Qemu-devel] [PATCH 19/21] linux-user: initialize mmap_mutex properly riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 20/21] linux-user/syscall.c: define _ATFILE_SOURCE riku.voipio
2009-06-12 13:50 ` [Qemu-devel] [PATCH 21/21] linux-user: remove duplicate tswap32() from do_getsockopt() riku.voipio
2009-06-14 15:12 ` [Qemu-devel] [PATCH 00/21] Pending linux-user patches Blue Swirl
2009-06-15 15:10   ` Riku Voipio
2009-06-16 16:30     ` Martin Mohring
2009-06-16 16:45       ` Blue Swirl [this message]
2009-06-16 17:03         ` Riku Voipio

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=f43fc5580906160945m4464e7d9xfe9faa803fe50cd@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=martin.mohring@opensuse.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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;
as well as URLs for NNTP newsgroup(s).