From: Jeff Garzik <jeff@garzik.org>
To: Gwendal Grignou <gwendal@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Grant Grundler <grundler@google.com>
Subject: Re: linux-next: build failure after merge of the libata tree
Date: Thu, 19 Aug 2010 16:15:24 -0400 [thread overview]
Message-ID: <4C6D90DC.4050202@garzik.org> (raw)
In-Reply-To: <AANLkTinJ8ks85Ym11wd4csdqFVgQpS7nw=RrfhMrLPUH@mail.gmail.com>
On 08/17/2010 08:46 PM, Gwendal Grignou wrote:
> Let me fix it and send a patch to Jeff.
>
> Gwendal.
>
> On Tue, Aug 17, 2010 at 5:40 PM, Stephen Rothwell<sfr@canb.auug.org.au> wrote:
>> 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.
Never received a patch; pushed out the obvious fix myself.
next prev parent reply other threads:[~2010-08-19 20:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 0:40 linux-next: build failure after merge of the libata tree Stephen Rothwell
2010-08-18 0:46 ` Gwendal Grignou
2010-08-19 20:15 ` Jeff Garzik [this message]
-- 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=4C6D90DC.4050202@garzik.org \
--to=jeff@garzik.org \
--cc=grundler@google.com \
--cc=gwendal@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).