All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Evan T Mesterhazy <etm2131@columbia.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Changelog of features / drivers removed from kernel?
Date: Mon, 8 Feb 2021 07:52:30 +0100	[thread overview]
Message-ID: <YCDfrs94JH3l0XeA@kroah.com> (raw)
In-Reply-To: <CAJh8_PuK-PRJnotjYdM0+5hvADROva1K+iOUY+3kofreDA+LVg@mail.gmail.com>

On Sun, Feb 07, 2021 at 05:30:34PM -0500, Evan T Mesterhazy wrote:
> Apologies if this comes off as a lazy question, but after a fair bit of
> searching I've been unable to find a changelog indicating which device
> drivers / features were dropped from various versions of the kernel. Does
> such a changelog exist?

`git log v5.1..v5.2` will show you the whole log, but that's a lot.

> I'm specifically trying to narrow down why the PCI devices on a server I
> have work with 5.8 and don't work with 5.9+. The server is circa 2014, so I
> suppose there's an off chance support for some component got dropped.

I doubt support for such modern hardware has been dropped in kernel
versions like this.  Odds are you just forgot to update a configuration
option.

Try using `git bisect` to track down the offending commit, that will go
much faster.

good luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-02-08  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 22:30 Changelog of features / drivers removed from kernel? Evan T Mesterhazy
2021-02-08  6:52 ` Greg KH [this message]
2021-02-08 14:00   ` Evan T Mesterhazy
2021-02-09  9:03     ` Valdis Klētnieks
2021-02-09 14:44       ` Evan T Mesterhazy
2021-02-09 14:45         ` Greg KH

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=YCDfrs94JH3l0XeA@kroah.com \
    --to=greg@kroah.com \
    --cc=etm2131@columbia.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    /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.