Add a tracker for patches that have not yet been upstreamed

[tgross35]

See discussion at https://rust-for-linux.zulipchat.com/#narrow/stream/288089-General/topic/Registry.20of.20Abstractions

My list that this is based on: https://github.com/tgross35/RFL-patch-registry

[fbq]

Thanks for putting all the information together!

I wonder whether bullet points/lists are better than tables, at very least, we can group things belonging to the same subsystem together. For example:

Filesystem API

vfs

• Depends on: folio
  ...

MM

folio

...

pages

...

Filesystem implementions

tarfs

• Depends on: vfs
  ...

puzzle fs

...

Thoughts?

[tgross35]

Interesting, I like the thought of having dependencies. Maybe it would be good to keep the main abstractions in a table for quick reading, but the drivers and implementations could be in a list format?

I'll play around with it a bit

[fbq]

Yes, tables are better for a quick look (or a rough picture of everything). However, I think people that use the information would probably do a search with key words, so it doesn't matter. Maybe a table for each large subsystem (like MM, filesystems, networking, drm, security, etc.)? But anyway, I don't have any problem with the current format, we can always improve the format of the information later ;-)

[tgross35]

Up to you :) if you think it is ok to merge as-is, I can make a PR doing some updates. Maybe even just an extra column saying the subsystem then a second one saying exactly what it is could work