All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ernst Schwab <eschwab@online.de>
Subject: linux-next: build failure after merge of the spi tree
Date: Tue, 29 Jun 2010 13:29:07 +1000	[thread overview]
Message-ID: <20100629132907.f857600d.sfr@canb.auug.org.au> (raw)

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

Hi Grant,

After merging the spi tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_readbytes':
drivers/mmc/host/mmc_spi.c:185: error: implicit declaration of function 'spi_sync_locked'
drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_request':
drivers/mmc/host/mmc_spi.c:1088: error: implicit declaration of function 'spi_bus_lock'
drivers/mmc/host/mmc_spi.c:1101: error: implicit declaration of function 'spi_bus_unlock'

Caused by commit f0168ff4069fba07fdd4b05aa19f283171c8d265 ("spi/mmc_spi:
mmc_spi adaptations for SPI bus locking API").  Maybe updates to another
file were missed?

I have used the spi tree from next-20100628 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2010-06-29  3:29 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29  3:29 Stephen Rothwell [this message]
2010-06-29  5:02 ` linux-next: build failure after merge of the spi tree Grant Likely
2010-10-14  1:55 Stephen Rothwell
2010-10-14  1:58 ` Grant Likely
2011-06-07  2:53 Stephen Rothwell
2011-06-07 16:51 ` Grant Likely
2013-07-29  3:42 Stephen Rothwell
2013-07-29  5:00 ` Mark Brown
2013-07-29  5:56   ` Stephen Rothwell
2013-07-29  6:40     ` Mark Brown
2013-07-29  6:48       ` Stephen Rothwell
2013-07-29  8:00         ` Mark Brown
2013-08-27  6:15 Stephen Rothwell
2013-08-27  7:20 ` Sourav Poddar
2013-08-27  7:20   ` Sourav Poddar
2014-01-06  7:03 Stephen Rothwell
2014-01-06  7:09 ` Baruch Siach
2014-02-24  3:45 Stephen Rothwell
2014-02-24  6:00 ` Mark Brown
2014-04-15  2:17 Stephen Rothwell
2014-04-15  4:35 ` Harini Katakam
2014-12-08 12:05 Stephen Rothwell
2014-12-08 12:13 ` Mark Brown
2014-12-08 12:54   ` Lee Jones
2014-12-08 12:58     ` Mark Brown
2014-12-08 13:56 ` Laurentiu Palcu
2015-01-30  3:02 Stephen Rothwell
2015-01-30  5:43 ` Ricardo Ribalda Delgado
2015-04-07  6:49 Stephen Rothwell
2015-05-12  3:14 Stephen Rothwell
2015-08-21  4:10 Stephen Rothwell
2016-01-06  3:34 Stephen Rothwell
2016-05-16  2:08 Stephen Rothwell
2016-05-16 10:23 ` Mark Brown
2016-12-09  2:32 Stephen Rothwell
2016-12-12  2:24 ` Stephen Rothwell
2017-05-24  1:08 Stephen Rothwell
2017-05-24  3:29 ` Jiada Wang
2017-07-03  3:41 Stephen Rothwell
2017-07-10  3:26 Stephen Rothwell
2017-12-22  2:18 Stephen Rothwell
2017-12-22  7:39 ` Rasmus Villemoes
2017-12-22 15:51   ` Mark Brown
2018-08-29  0:33 Stephen Rothwell
2018-08-29  1:29 ` Baolin Wang
2022-01-27  4:57 Stephen Rothwell
2022-02-15  2:08 Stephen Rothwell
2022-02-15  7:33 ` Uwe Kleine-König
2022-02-16  5:17 Stephen Rothwell
2022-02-16 12:20 ` André Almeida
2022-02-16 13:07   ` André Almeida
2022-02-16 16:08     ` Mark Brown
2022-02-16 16:13       ` André Almeida
2022-02-16 16:07   ` Mark Brown

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=20100629132907.f857600d.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=eschwab@online.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.