public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] e1000: fix PCI memory addressing
Date: Sat, 22 Aug 2009 11:12:45 +0200	[thread overview]
Message-ID: <20090822091245.DF0A0833DBD2@gemini.denx.de> (raw)
In-Reply-To: <1250542538-5717-1-git-send-email-timur@freescale.com>

Dear Timur Tabi,

In message <1250542538-5717-1-git-send-email-timur@freescale.com> you wrote:
> The Intel E1000 driver was making assumptions about the relationship between
> some virtual, physical, and PCI addresses.
> 
> Also fix some bad usage of the DEBUGOUT macro
> 
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
>  drivers/net/e1000.c |   17 +++++++++--------
>  1 files changed, 9 insertions(+), 8 deletions(-)

This patch causes compiler warnings:

Configuring for MVBC_P board...
e1000.c: In function 'e1000_transmit':
e1000.c:5019: warning: passing argument 1 of 'virt_to_phys' discards
qualifiers from pointer target type
...
Configuring for MPC8536DS board...
e1000.c: In function 'e1000_transmit':
e1000.c:5019: warning: passing argument 1 of 'virt_to_phys' discards
qualifiers from pointer target type
...
Configuring for MPC8544DS board...
e1000.c: In function 'e1000_transmit':
e1000.c:5019: warning: passing argument 1 of 'virt_to_phys' discards
qualifiers from pointer target type
...

etc.


Please provide a fix!


Also, I tonticed this:

> @@ -357,7 +356,7 @@ e1000_acquire_eeprom(struct e1000_hw *hw)
>  	struct e1000_eeprom_info *eeprom = &hw->eeprom;
>  	uint32_t eecd, i = 0;
>  
> -	DEBUGOUT();
> +	DEBUGFUNC();
>  
>  	if (e1000_swfw_sync_acquire(hw, E1000_SWFW_EEP_SM))
>  		return -E1000_ERR_SWFW_SYNC;
> @@ -418,7 +417,7 @@ static int32_t e1000_init_eeprom_params(struct e1000_hw *hw)
>  	int32_t ret_val = E1000_SUCCESS;
>  	uint16_t eeprom_size;
>  
> -	DEBUGOUT();
> +	DEBUGFUNC();
...

These changes are unrelated to the change and not even mentioned in
the commit message. This is a bad thing to do. Please make sure NOT
to do this again. Please split this into two orthogonal patches next
time. Thanks.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Very ugly or very beautiful women should be flattered on their
understanding, and mediocre ones on their beauty.
                                       -- Philip Earl of Chesterfield

  parent reply	other threads:[~2009-08-22  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 20:55 [U-Boot] [PATCH 2/2] e1000: fix PCI memory addressing Timur Tabi
2009-08-17 20:57 ` Timur Tabi
2009-08-17 23:25 ` Kumar Gala
2009-08-21  6:56   ` Kumar Gala
2009-08-21 16:59 ` Ben Warren
2009-08-22  9:12 ` Wolfgang Denk [this message]
2009-08-22 11:40   ` Timur Tabi
2009-08-22 11:49     ` Wolfgang Denk
2009-08-22 12:54   ` Timur Tabi
2009-08-22 13:17     ` Wolfgang Denk
2009-08-24 15:30       ` Timur Tabi

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=20090822091245.DF0A0833DBD2@gemini.denx.de \
    --to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox