Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported

Adrian Bunk wrote:
> But this doesn't mean it's OK - exporting static code is wrong.
> 
> BTW:
> It seems Patrick's recently merged patch to let the compiler help us 
> find such bugs (a1a8feed1743ec8d2af1dafa7c5321679f0a3e4f) isn't working.

Indeed, something seems to be broken. I can't get it to throw warnings
anymore even for the H.323 case I initially tested it with, which is
strange because I did trial and error until I had something which I'm
100% sure did throw warnings. I'll look into it, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
    • From: Adrian Bunk <[email protected]>
  • Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
    • From: Andrew Morton <[email protected]>
  • Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Re: Problems ejecting 4th-generation iPod with 2.6.15
• Next by Date: Re: [RESEND][RFC][PATCH 2/7] implementation of LSM hooks
• Previous by thread: Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
• Next by thread: Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]