after effects of a kernel API change

Hi list,

Whenever there is a change in the kernel API (or a new API is
introduced), all of the drivers that use the older API need to be
changed (or recommended to be changed). I believe it is the
responsibility of the person changing the kernel API, to change all
the drivers that have found their way into the kernel code?

How does this happen? Because the person who brought the change in the
API might not know the internals of all the drivers?

Is there any way volunteers like me can help in this exercise?

Thanks,

Dan
-
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/

Follow-Ups:
- Re: after effects of a kernel API change
  - From: "Ahmed S. Darwish" <[email protected]>
- Re: after effects of a kernel API change
  - From: Greg KH <[email protected]>

Prev by Date: Re: query related to serial console
Next by Date: Re: problems with latest smbfs changes on 2.4.34 and security backports
Previous by thread: [RPC][PATCH 2.6.20-rc5] limit total vfs page cache
Next by thread: Re: after effects of a kernel API change
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]