All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: devel@linuxdriverproject.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux-Next <linux-next@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] Staging driver patches for 3.12-rc1
Date: Thu, 5 Sep 2013 08:05:27 -0700	[thread overview]
Message-ID: <20130905150527.GA21185@kroah.com> (raw)
In-Reply-To: <CAMuHMdXfpMJeTPb4e11_oyqH5TRtTxrUMOnL9GKdSjv3VxDFww@mail.gmail.com>

On Thu, Sep 05, 2013 at 04:09:48PM +0200, Geert Uytterhoeven wrote:
> On Tue, Sep 3, 2013 at 1:58 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Here's the bit staging tree pull request for 3.12-rc1.
> >
> > Lots of staging driver updates, and fixes.  Lustre is finally enabled in
> > the build, and lots of cleanup started happening in it.  There's a new
> 
> Lustre fails modpost on (at least) 4 architectures due to unexported arch
> support functions: m68k, mips, parisc and sparc64 (patches sent).

Odd, what functions were not present in those arches that lustre uses
that no other kernel code uses?

> All 4 failures were not visible in -next due to other build failures :-(

Ah, that's why it wasn't caught, thanks for doing this.

greg k-h

  reply	other threads:[~2013-09-05 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 23:58 [GIT PATCH] Staging driver patches for 3.12-rc1 Greg KH
2013-09-05 14:09 ` Geert Uytterhoeven
2013-09-05 15:05   ` Greg KH [this message]
2013-09-05 16:54     ` Geert Uytterhoeven

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=20130905150527.GA21185@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 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.