public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jeff Garzik <jeff@garzik•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Gwendal Grignou <gwendal@google•com>,
	Grant Grundler <grundler@google•com>
Subject: linux-next: build failure after merge of the libata tree
Date: Wed, 18 Aug 2010 10:40:57 +1000	[thread overview]
Message-ID: <20100818104057.5fdaf20d.sfr@canb.auug.org.au> (raw)

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

Hi Jeff,

After merging the libata tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/ata/libata-transport.c: In function 'ata_attach_transport':
drivers/ata/libata-transport.c:678: error: implicit declaration of function 'kzalloc'
drivers/ata/libata-transport.c:678: warning: assignment makes pointer from integer without a cast
drivers/ata/libata-transport.c: In function 'ata_release_transport':
drivers/ata/libata-transport.c:741: error: implicit declaration of function 'kfree'

Caused by commit 97395d39931160a171959ac2e1fbff1caba3374b ("[libata] Add
ATA transport class") neglecting to include linux/slab.h.   See Rule 1 in
Documentation/SubmitChecklist.

I have used the libata tree form next-20100817 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-08-18  0:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  0:40 Stephen Rothwell [this message]
2010-08-18  0:46 ` linux-next: build failure after merge of the libata tree Gwendal Grignou
2010-08-19 20:15   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2012-07-02  2:10 Stephen Rothwell
2012-07-02  2:19 ` huang ying
2013-08-19  1:54 Stephen Rothwell
2013-08-19  3:18 ` Terry Suereth
2013-08-19 13:40   ` Tejun Heo
2013-08-27  2:50 Stephen Rothwell
2013-08-27  5:52 ` Aaron Lu
2013-08-27 18:09   ` Tejun Heo
2014-02-26  2:55 Stephen Rothwell
2014-02-26 13:49 ` Tejun Heo
2014-04-24  1:17 Stephen Rothwell
2014-04-24 12:25 ` Tejun Heo
2015-09-17  4:03 Stephen Rothwell
2015-09-17 11:14 ` Luis de Bethencourt
2016-05-09  0:14 Stephen Rothwell
2022-01-06 14:08 Stephen Rothwell
2022-01-06 23:58 ` Damien Le Moal
2022-01-07  0:17   ` Stephen Rothwell
2022-01-07  1:28     ` Damien Le Moal

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=20100818104057.5fdaf20d.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=grundler@google$(echo .)com \
    --cc=gwendal@google$(echo .)com \
    --cc=jeff@garzik$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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