From: Aurelien Jarno <aurelien@aurel32.net>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, resend] [STABLE] Sync OSS_GETVERSION handling with head
Date: Sun, 18 Apr 2010 23:38:34 +0200 [thread overview]
Message-ID: <20100418213834.GC12023@hall.aurel32.net> (raw)
In-Reply-To: <20100418211646.GA81689@triton8.kn-bremen.de>
On Sun, Apr 18, 2010 at 11:16:46PM +0200, Juergen Lock wrote:
> On Sun, Apr 18, 2010 at 10:52:22PM +0200, Aurelien Jarno wrote:
> > On Sun, Apr 11, 2010 at 06:17:32PM +0200, Juergen Lock wrote:
> > > As suggested by Andreas Färber, here is a cumulative patch that syncs
> > > OSS_GETVERSION handling with head by merging the following commits:
> > >
> > > 1. oss: issue OSS_GETVERSION ioctl only when needed
> > > 6d246526ce3c145b2831285def6983f5de6190d3
> > >
> > > 2. oss: fix fragment setting
> > > 3d709fe73a77c40e263b3af6e650fd4b519c3562
> > >
> > > 3. Workaround for broken OSS_GETVERSION on FreeBSD, part two
> > > 72ff25e4e98d6dba9286d032b9ff5432553bbad5
> > >
> > > Signed-off-by: Juergen Lock <nox@jelal.kn-bremen.de>
> >
> > I would actually prefer a patch series instead of a cumulative patch, so
> > that we can match commits between HEAD and stable-0.12.
> >
> Oh, I only did what was suggested... If you want to merge those as
> individual commits I think you can just cherry-pick them from head?
>
They doesn't apply directly, and fixing them doesn't seems that
trivial.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-04-18 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 16:17 [Qemu-devel] [PATCH, resend] [STABLE] Sync OSS_GETVERSION handling with head Juergen Lock
2010-04-18 20:52 ` Aurelien Jarno
2010-04-18 21:16 ` Juergen Lock
2010-04-18 21:38 ` Aurelien Jarno [this message]
2010-04-18 21:52 ` Juergen Lock
2010-04-19 17:58 ` Juergen Lock
2010-04-18 23:03 ` Andreas Färber
2010-04-19 7:30 ` malc
2010-04-19 8:21 ` Aurelien Jarno
2010-04-19 8:36 ` malc
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=20100418213834.GC12023@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=nox@jelal.kn-bremen.de \
--cc=qemu-devel@nongnu.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.