From: David Miller <davem@davemloft.net>
To: robert.jarzmik@free.fr
Cc: netdev@vger.kernel.org, arnd@arndb.de
Subject: Re: [linux-next:master 1436/1582] drivers/net/ethernet/smsc/smc91x.c:2378:6: error: implicit declaration of function 'machine_is_assabet'
Date: Wed, 19 Oct 2016 16:12:06 -0400 (EDT) [thread overview]
Message-ID: <20161019.161206.1749616830232202176.davem@davemloft.net> (raw)
In-Reply-To: <87funs3ycx.fsf@belgarion.home>
From: Robert Jarzmik <robert.jarzmik@free.fr>
Date: Wed, 19 Oct 2016 21:58:06 +0200
> Hi David,
>
> Here is a little mess I created with my former serie :
>> drivers/net/ethernet/smsc/smc91x.c: In function 'smc_drv_probe':
>>>> drivers/net/ethernet/smsc/smc91x.c:2378:6: error: implicit declaration of function 'machine_is_assabet' [-Werror=implicit-function-declaration]
>> if (machine_is_assabet() && machine_has_neponset())
>> ^~~~~~~~~~~~~~~~~~
>> cc1: some warnings being treated as errors
>>
>> vim +/machine_is_assabet +2378 drivers/net/ethernet/smsc/smc91x.c
>
> The mess comes from the patch "net: smc91x: isolate u16 writes alignment
> workaround", where I though I had removed all "machine_is_*()" calls, and I
> didn't notice the machine_is_assabet() one.
>
> The fix is to re-add the removed include in the wrong chunk in [1].
>
> Now do you want :
> - another apart patch to fix the faulty one
> - a "fixup!" patch to fixup the commit in your next tree
> - or anything else
Please send me a fixup follow-on patch.
If changes are in my tree, they are part of the permanent record
and won't be rebased out.
next prev parent reply other threads:[~2016-10-19 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201610200342.Wv4wShnU%fengguang.wu@intel.com>
2016-10-19 19:58 ` [linux-next:master 1436/1582] drivers/net/ethernet/smsc/smc91x.c:2378:6: error: implicit declaration of function 'machine_is_assabet' Robert Jarzmik
2016-10-19 20:12 ` David Miller [this message]
2016-10-19 20:17 ` Robert Jarzmik
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=20161019.161206.1749616830232202176.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=netdev@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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