From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] e1000: fix no nvm build
Date: Mon, 8 Sep 2014 04:07:30 +0200 [thread overview]
Message-ID: <201409080407.30374.marex@denx.de> (raw)
In-Reply-To: <833da41f505396e8f7cf7bd9a31b2c62f0a5e51a.1410127137.git.marcel@ziswiler.com>
On Monday, September 08, 2014 at 12:02:11 AM, Marcel Ziswiler wrote:
> Fix the following build error in case CONFIG_E1000_NO_NVM is enabled:
> CC drivers/net/e1000.o
> drivers/net/e1000.c: In function ?e1000_initialize?:
> drivers/net/e1000.c:5365:5: error: ?struct e1000_hw? has no
> member named ?eeprom_semaphore_present?
> make[1]: *** [drivers/net/e1000.o] Error 1
> make: *** [drivers/net] Error 2
> --
> This got introduced by Marek's i210 support patch commit
> 951860634fdb557bbb58e0f99215391bc0c29779.
Let me shift the blame to Tim, who should have tested it before submitting ;-D
> Signed-off-by: Marcel Ziswiler <marcel@ziswiler.com>
Thanks for spotting this!
Acked-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-08 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03c9982d8450bcbf073530edd6446ef3ec4dfddb.1410127137.git.marcel@ziswiler.com>
2014-09-07 22:02 ` [U-Boot] [PATCH] e1000: fix no nvm build Marcel Ziswiler
2014-09-08 2:07 ` Marek Vasut [this message]
2014-09-25 14:44 ` [U-Boot] " Tom Rini
2014-09-07 22:03 ` [U-Boot] [PATCH] e1000: add i211 and unprogrammed i210/i211 support Marcel Ziswiler
2014-09-08 2:07 ` Marek Vasut
2014-09-10 21:18 ` Marcel Ziswiler
2014-09-10 23:46 ` Marek Vasut
2014-10-27 22:19 ` [U-Boot] " Tom Rini
2014-10-28 1:07 ` Marcel Ziswiler
2014-10-28 11:15 ` Tom Rini
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=201409080407.30374.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.