From: David Miller <davem@davemloft.net>
To: sachinp@in.ibm.com
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [Patch -next] Fix net/3c503.c build break
Date: Fri, 04 Sep 2009 03:41:24 -0700 (PDT) [thread overview]
Message-ID: <20090904.034124.45872368.davem@davemloft.net> (raw)
In-Reply-To: <4AA0ED92.6070306@in.ibm.com>
From: Sachin Sant <sachinp@in.ibm.com>
Date: Fri, 04 Sep 2009 16:06:02 +0530
> Today's Next failed to build on a x86 box with following error.
>
> drivers/net/3c503.c: In function 'el2_open':
> drivers/net/3c503.c:406: error: 'reval' undeclared (first use in this
> function)
> drivers/net/3c503.c:406: error: (Each undeclared identifier is
> reported only once
> drivers/net/3c503.c:406: error: for each function it appears in.)
>
> Most probably because of commit
> ab08999d6029bb2c79c16be5405d63d2bedbdfea
> The patch had a typo in it. Below patch fixes the issue for me.
Applied, thank you.
prev parent reply other threads:[~2009-09-04 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090904182309.dbb05c96.sfr@canb.auug.org.au>
2009-09-04 10:36 ` [Patch -next] Fix net/3c503.c build break Sachin Sant
2009-09-04 10:41 ` David Miller [this message]
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=20090904.034124.45872368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sachinp@in.ibm.com \
/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).