linux-kernel - Re: linux-next: build failure after merge of the libata tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150917111426.GA11478@goodgumbo.baconseed.org>
Date:	Thu, 17 Sep 2015 13:14:26 +0200
From:	Luis de Bethencourt <luis@...ethencourt.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Tejun Heo <tj@...nel.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the libata tree

On Thu, Sep 17, 2015 at 02:03:36PM +1000, Stephen Rothwell wrote:
> Hi Tejun,
> 
> After merging the libata tree, today's linux-next build (powercp
> allmodconfig) failed like this:
> 
> drivers/ata/pata_macio.c:1347:1: error: 'pata_macio_patch' undeclared here (not in a function)
> drivers/ata/pata_macio.c:1347:1: error: '__mod_of__pata_macio_patch_device_table' aliased to undefined symbol 'pata_macio_patch'
> 
> Caused by commit
> 
>   5d8619769cf5 ("ata: pata_macio: Fix module autoload for OF platform driver")
> 
> A simple typo ("patch" v "match"), but clearly never build tested.
> 
> Only found after the release.
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au

Sorry, this was my fault.

When I created the second version of the patch, based on -stable instead of
-next the typo creeped in and I didn't test properly.

Sending a correct version of the patch now.

Apologies,
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/