From: Greg KH <gregkh@suse.de>
To: John Kacur <jkacur@redhat.com>
Cc: Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 00/15] Staging: Convert the semaphore mess
Date: Fri, 15 Jan 2010 07:19:42 -0800 [thread overview]
Message-ID: <20100115151942.GA10117@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1001151607570.5514@localhost.localdomain>
On Fri, Jan 15, 2010 at 04:11:23PM +0100, John Kacur wrote:
>
>
> On Thu, 14 Jan 2010, Greg KH wrote:
>
> > On Mon, Jan 11, 2010 at 09:51:39PM +0100, John Kacur wrote:
> > > Thomas / Ingo / Greg
> > >
> > > I started with the patch in -rt 041e3130496f31d0cb4887fc6183117e662f5141
> > > and tried to forward port it to 2.6.33-rc3
> > >
> > > The patch no-longer applied, because some of the changes were already accepted
> > > upstream, some files had been moved or dropped and so on.
> > >
> > > So, I broke the original patch into one patch per file, and fixed merge errors.
> > > Then I also went and changed similar problems in new code
> > >
> > > This code should be queued-up for the 2.6.34 merge window, and should also
> > > be applied to the latests -rt branch.
> >
> > I can't do that, as it breaks when applying to Linus's latest tree,
> > right?
> >
> > If this needs to go through some other tree, no objection from me at
> > all, feel free to add:
> > Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
> > to them.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Hi Greg.
>
> This shouldn't break - I tested against 2.6.33-rc3, and I just retested
> against 2.6.33-rc4. The origin of the patch is in -rt but there is nothing
> -rt about it which is why I would like to push it upstream.
>
> I don't have all that hardware, so my ability to test it is somewhat
> limited - and since these are all staging drivers, I was hoping that you
> would pick it up if Thomas doesn't have any objections.
Try applying your first patch against 2.6.33-rc3 and then just building
the code. It dies a horrible death :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-15 15:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 20:51 [PATCH 00/15] Staging: Convert the semaphore mess John Kacur
2010-01-11 20:51 ` [PATCH 01/15] dt9812: " John Kacur
2010-01-11 20:51 ` [PATCH 02/15] usbdux.c: " John Kacur
2010-01-11 20:51 ` [PATCH 03/15] usbduxfast: " John Kacur
2010-01-11 20:51 ` [PATCH 04/15] alphatrack: " John Kacur
2010-01-11 20:51 ` [PATCH 05/15] tranzport: Convert he " John Kacur
2010-01-11 20:51 ` [PATCH 06/15] mimio: Convert " John Kacur
2010-01-11 20:51 ` [PATCH 07/15] wwrap: Convert the " John Kacur
2010-01-11 20:51 ` [PATCH 08/15] p9auth: " John Kacur
2010-01-11 20:51 ` [PATCH 09/15] mt9d112: " John Kacur
2010-01-11 20:51 ` [PATCH 10/15] mt9p012_fox: " John Kacur
2010-01-11 20:51 ` [PATCH 11/15] mt9t013: " John Kacur
2010-01-11 20:51 ` [PATCH 12/15] s5k3e2fx: " John Kacur
2010-01-11 20:51 ` [PATCH 13/15] pmem: " John Kacur
2010-01-11 20:51 ` [PATCH 14/15] rtmp_init: " John Kacur
2010-01-11 20:51 ` [PATCH 15/15] vme_user: " John Kacur
2010-01-11 20:56 ` [PATCH 00/15] Staging: " John Kacur
2010-01-15 1:29 ` Greg KH
2010-01-15 15:11 ` John Kacur
2010-01-15 15:19 ` Greg KH [this message]
2010-01-15 15:41 ` John Kacur
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=20100115151942.GA10117@suse.de \
--to=gregkh@suse.de \
--cc=greg@kroah.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.