From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PATCH] STAGING patches for .39
Date: Wed, 16 Mar 2011 18:51:26 -0700 [thread overview]
Message-ID: <20110317015126.GA31754@kroah.com> (raw)
In-Reply-To: <AANLkTikEEDDFxZQtvV46JJRU1NAtiXh_N4onJ1jwKHaF@mail.gmail.com>
On Wed, Mar 16, 2011 at 05:32:00PM -0700, Linus Torvalds wrote:
> On Wed, Mar 16, 2011 at 5:28 PM, Greg KH <greg@kroah.com> wrote:
> >>
> >> Aren't those things supposed to at least compile? What's going on?
> >
> > The gma500 driver will not build until you pull the drm tree into yours
> > as that is an api dependancy it needs. I didn't think you build staging
> > drivers, so I didn't think I needed to call this one out. I was wrong :)
>
> I don't try to compile the staging tree all the time, but I do tend to
> try to check it every once in a while. So yes, let me know if there
> are dependencies.
>
> > As for the others, I don't know of any build problems, what one did you
> > have a problem with?
>
> The one with inifinite errors was vt6655.
Wierd, it builds for me in my branch that you pulled from.
I just tested it with my 'test merge' from earlier today to verify that
there were no merge issues, which was with your tree as of commit
0bbf211975addc2963b63a41a2eac99928365996 "Merge branch 'for-linus' of
git://android.git.kernel.org/kernel/tegra" and it builds there as well.
> It may be due to network layer changes. I had some other drivers with
> conflicts. Maybe this one didn't have content conflicts, but ended up
> having conflicts due to changed semantics etc.
Ah, perhaps, I don't know what changed with wireless recently, maybe
something broke them from that tree. If so, I normally fix them up
right after -rc1 happens and will do so here as well, or earlier if you
push this merge out so I can see the problems.
thanks,
greg k-h
prev parent reply other threads:[~2011-03-17 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 21:03 [GIT PATCH] STAGING patches for .39 Greg KH
[not found] ` <1300309804-3756-1-git-send-email-gregkh@suse.de>
2011-03-16 21:03 ` [PATCH 584/961] staging: brcm80211: Fix memory leak after kmalloc failure Greg Kroah-Hartman
2011-03-17 0:19 ` [GIT PATCH] STAGING patches for .39 Linus Torvalds
2011-03-17 0:28 ` Greg KH
2011-03-17 0:32 ` Linus Torvalds
2011-03-17 0:34 ` Linus Torvalds
2011-03-17 1:52 ` Greg KH
2011-03-17 2:02 ` Greg KH
2011-03-17 19:55 ` Randy Dunlap
2011-03-17 20:04 ` Greg KH
2011-03-17 20:17 ` Randy Dunlap
2011-03-17 1:51 ` Greg KH [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=20110317015126.GA31754@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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