All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4] gcc-3.4 more fixes
Date: Mon, 23 Aug 2004 08:35:33 -0300	[thread overview]
Message-ID: <20040823113533.GA4569@logos.cnet> (raw)
In-Reply-To: <4112906E.4060707@ttnet.net.tr>

On Thu, Aug 05, 2004 at 10:54:22PM +0300, O.Sezer wrote:
> Hi all:
> 
> The attached patch applies to 2.4.27-rc5 + Mikael's patch
> series. Most fixes are taken from 2.6. The only non-lvalue
> change is to e100.h which, otherwise, caused some tens of
> warning lines on my logs.
> 
> There still are some lvalue related warnings (eicon_idi.c:2057,
> 53c7,8xx.c:3929,  fs/affs/super.c:133, rio_linux.c:1209,1333,
> intermezzo/sysctl.c:305,  and ibmphp_hpc.c and  pciehp_hpc.c).
> The hotplug dir (ibmphp_hpc.c and  pciehp_hpc.c) seems to get
> very many updates in 2.6 compared to 2.4 so it wasn't easy to
> decide. And for the rest, I got tired and bored..
> 
> There also are "integer constant is too large for "long" type"
> warnings all around and I would like to know how serious they
> are.
> 
> Compilations were tested with the gcc-3.4.0-1 package from FC2
> (rebuilt on rh9). I would like to have the folks review this
> for any of my errors/typos/brainfarts etc ;)
> 
> Thanks,
> Özkan Sezer

Ozkan, 

This are just warning fixes right?

I dont like this patches, that is, I'm not confident about them.

 Let the warnings be.

[marcelo@logos atm]$ grep PRIV idt77*
idt77105.c:#define PRIV(dev) ((struct idt77105_priv *) dev->phy_data)

> --- 27rc5~/drivers/atm/idt77105.c
> +++ 27rc5/drivers/atm/idt77105.c
> @@ -267,7 +267,7 @@
>  {
>  	unsigned long flags;
>  
> -	if (!(PRIV(dev) = kmalloc(sizeof(struct idt77105_priv),GFP_KERNEL)))
> +	if (!(dev->dev_data = kmalloc(sizeof(struct idt77105_priv),GFP_KERNEL)))
>  		return -ENOMEM;
>  	PRIV(dev)->dev = dev;
>  	spin_lock_irqsave(&idt77105_priv_lock, flags);
> @@ -345,7 +345,7 @@
>                  else
>                      idt77105_all = walk->next;
>  	        dev->phy = NULL;
> -                PRIV(dev) = NULL;
> +                dev->dev_data = NULL;
>                  kfree(walk);
>                  break;
>              }

  parent reply	other threads:[~2004-08-23 12:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 19:54 [PATCH 2.4] gcc-3.4 more fixes O.Sezer
2004-08-06 20:09 ` O.Sezer
2004-08-23 11:35 ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 13:27 O.Sezer
2004-08-23 19:07 ` Jon Oberheide
2004-08-23 13:41 O.Sezer
2004-08-23 12:34 ` Marcelo Tosatti
2004-08-23 14:13   ` O.Sezer
2004-08-23 13:11     ` Marcelo Tosatti
2004-08-23 22:18       ` Jeff Garzik
2004-08-23 22:34         ` O.Sezer
2004-08-23 16:10     ` O.Sezer

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=20040823113533.GA4569@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sezeroz@ttnet.net.tr \
    /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.