public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail•com>
To: Rusty Russell <rusty@rustcorp•com.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for March 30 (Blackfin string failures again)
Date: Mon, 30 Mar 2009 20:26:40 -0400	[thread overview]
Message-ID: <8bd0f97a0903301726j536da9aciaf9eb5e9a7afff5@mail.gmail.com> (raw)

On Mon, Mar 30, 2009 at 05:01, Stephen Rothwell wrote:
> The rr tree lost 8 conflicts.

was the Blackfin changes related to the string updates lost or
something ?  the March 30 tree brought in these failures again ...

In file included from include/linux/bitmap.h:9,
                 from include/linux/nodemask.h:90,
                 from include/linux/mmzone.h:17,
                 from include/linux/gfp.h:5,
                 from include/linux/kmod.h:23,
                 from include/linux/module.h:14,
                 from arch/blackfin/lib/strncmp.c:14:
include/linux/string.h: In function 'strstarts':
include/linux/string.h:131: error: implicit declaration of function 'strncmp'
make[1]: *** [arch/blackfin/lib/strncmp.o] Error 1
make: *** [arch/blackfin/lib] Error 2
Last committer:
cc11ee1: Stephen Rothwell <sfr@...>
Merge branch 'quilt/rr'
-mike

             reply	other threads:[~2009-03-31  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  0:26 Mike Frysinger [this message]
2009-03-31  2:18 ` linux-next: Tree for March 30 (Blackfin string failures again) Rusty Russell
2009-03-31  2:20 ` [PATCH] blackfin: allow allow usage of string functions in linux/string.h Rusty Russell

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=8bd0f97a0903301726j536da9aciaf9eb5e9a7afff5@mail.gmail.com \
    --to=vapier.adi@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rusty@rustcorp$(echo .)com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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