public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Luis de Bethencourt <luis@debethencourt•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Tejun Heo <tj@kernel•org>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the libata tree
Date: Thu, 17 Sep 2015 13:14:26 +0200	[thread overview]
Message-ID: <20150917111426.GA11478@goodgumbo.baconseed.org> (raw)
In-Reply-To: <20150917140336.63c2d09c@canb.auug.org.au>

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@canb•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

  reply	other threads:[~2015-09-17 11:14 UTC|newest]

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

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=20150917111426.GA11478@goodgumbo.baconseed.org \
    --to=luis@debethencourt$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tj@kernel$(echo .)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