Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated oni386
From: Andrew Morton
Date: Thu Nov 17 2005 - 22:03:31 EST
Adrian Bunk <bunk@xxxxxxxxx> wrote:
> > I believe that the main reason for this is that the developers simply don't
> > notice the new warning amongst all the noise.
> There are few areas in the kernel that spit that many warnings that you
> might not see new ones .
> The developers not noticing the warnings might often be the same
> developers who send patches that don't compile...
Some architectures generate a lot more warnings than x86.
> > > If you dislike the warnings, you could move the whole __deprecated und a
> > > config option.
> > >
> > > In the case of virt_to_bus/bus_to_virt I had the hope that e.g. the ATM
> > > drivers that seem to have an active maintainer might get fixed.
> > That would be good - but perhaps a better approach would be to send pointed
> > emails to the maintainer. Or to merge lameo patches to remove
> > virt_to_bus() so he has to fix it for real ;)
> In the case of virt_to_bus/bus_to_virt there are stil many places in the
> kernel using it, and several of them are well maintained.
> IMHO the warnings are the best solution for getting a vast amount fixed,
> and then it's time to think about the rest.
But the warnings don't *work*. I'm *still* staring at stupid pm_register
and intermodule_foo warnings. How long has that been?
> > > But I'm not religious regarding this issue as long as you accept my
> > > -Werror-implicit-function-declaration patch...
> > Problem is, I'm the sucker who takes the brunt of that change. It'd be
> > best to fix up the warnings _before_ adding the make-it-break patch.
> -Werror-implicit-function-declaration doesn't add new warnings, it turns
> a specific kind of warnings that can indicate nasty runtime errors into
> compile errors.
I know, that's why the patch hurts so much. As I say, we'd be better off
fixing up all the warnings we can before turning them into build errors.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/