LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Daniel Rodrick" <daniel.rodrick@gmail.com>
To: kernelnewbies <kernelnewbies@nl.linux.org>,
	"Linux Newbie" <linux-newbie@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: after effects of a kernel API change
Date: Thu, 18 Jan 2007 09:45:04 +0530	[thread overview]
Message-ID: <292693080701172015n736a269fl6945ba4fe19d8174@mail.gmail.com> (raw)

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

             reply	other threads:[~2007-01-18  4:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18  4:15 Daniel Rodrick [this message]
2007-01-18  5:04 ` Greg KH
2007-01-18  5:10 ` Ahmed S. Darwish
2007-01-18  5:35   ` Rajat Jain
2007-01-18  7:47     ` Eric W. Biederman
2007-01-18  9:44     ` Ahmed S. Darwish

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=292693080701172015n736a269fl6945ba4fe19d8174@mail.gmail.com \
    --to=daniel.rodrick@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --subject='Re: after effects of a kernel API change' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox