public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Richard Weinberger <richard@nod•at>
Subject: Re: linux-next: build failure after merge of the ubi tree
Date: Wed, 03 Oct 2012 10:20:43 +0300	[thread overview]
Message-ID: <1349248843.2017.108.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20121003122735.692388e2f68dd85e43052c70@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

On Wed, 2012-10-03 at 12:27 +1000, Stephen Rothwell wrote:
> Hi Artem,
> 
> After merging the ubi tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> ERROR: "ubi_update_fastmap" [drivers/mtd/ubi/ubi.ko] undefined!
> ERROR: "ubi_scan_fastmap" [drivers/mtd/ubi/ubi.ko] undefined!
> ERROR: "ubi_calc_fm_size" [drivers/mtd/ubi/ubi.ko] undefined!

I've added Richard's fastmap work there. I'll look at these failures.

And yes, using the previous ubi tree is a good decision, thanks!

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-10-03  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03  2:27 linux-next: build failure after merge of the ubi tree Stephen Rothwell
2012-10-03  7:20 ` Artem Bityutskiy [this message]
2012-10-03  8:30   ` Richard Weinberger
  -- strict thread matches above, loose matches on Subject: below --
2012-08-24  1:34 Stephen Rothwell
2012-08-24  6:24 ` Artem Bityutskiy

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=1349248843.2017.108.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=richard@nod$(echo .)at \
    --cc=sfr@canb$(echo .)auug.org.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