All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the spi tree
Date: Mon, 6 Jan 2014 09:09:06 +0200	[thread overview]
Message-ID: <20140106070906.GE7812@tarshish> (raw)
In-Reply-To: <20140106180305.2839a467466f52f97ac68b93@canb.auug.org.au>

Hi Stephen,

On Mon, Jan 06, 2014 at 06:03:05PM +1100, Stephen Rothwell wrote:
> After merging the spi tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/spi/spi-dw-pci.c: In function 'spi_pci_probe':
> drivers/spi/spi-dw-pci.c:50:29: error: 'dev' undeclared (first use in this function)
>   dwpci = devm_kzalloc(&pdev-dev, sizeof(struct dw_spi_pci), GFP_KERNEL);
>                              ^
> 
> Caused by commit 04f421e7b0b1 ("spi: dw: use managed resources").
> 
> I have used the spi tree from next-20131224 for today (since the above
> commit does not revert cleanly).

Sorry, my bad (I said I have no way to test this PCI code, didn't I?). I'll 
send a fix shortly.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-01-06  7:09 UTC|newest]

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

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=20140106070906.GE7812@tarshish \
    --to=baruch@tkos.co.il \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.