Merge documentation commit '7e13f7dd9689f6fa503c23e515edaa46e7d38ce5' into c9s
This commit is contained in:
Jan Stancek
commit
894e8faeb6
|
|
@ -7,6 +7,10 @@ all:
|
|||
scripts/yaml2RHMAINTAINERS info/owners.yaml > info/RHMAINTAINERS
|
||||
scripts/yaml2CODEOWNERS info/owners.yaml > info/CODEOWNERS
|
||||
scripts/verifySubsystems info/owners.yaml
|
||||
@if ! git rev-parse --verify main >& /dev/null; then \
|
||||
git fetch origin main; \
|
||||
git checkout -b main --track origin/main -b main; \
|
||||
fi
|
||||
@if test -n "$$(git diff --name-status main | grep owners.yaml)" && \
|
||||
test "$$(git config --get owners.warning)" != "false"; then \
|
||||
echo "======================================================="; \
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
**Attention**
|
||||
|
||||
Are you looking to read the RHEL kernel documentation? Be sure to view
|
||||
the rendered version [here](https://redhat.gitlab.io/centos-stream/src/kernel/documentation/) instead of the gitlab markdown version to avoid
|
||||
broken links!
|
||||
|
||||
All changes to this file and directories included at this level must be made
|
||||
to the [Red Hat kernel documentation project](https://gitlab.com/redhat/centos-stream/src/kernel/documentation)
|
||||
Please see the 'Making Changes' section below for detailed information on
|
||||
|
|
|
|||
|
|
@ -46,6 +46,10 @@ The most common questions related to contributing to Red Hat-based kernel projec
|
|||
... https://cki-project.org/docs/user_docs/gitlab-mr-testing/full_picture/#blocking-on-missing-targeted-testing[This is intended to transition to a blocking tag in the future], but there are no timelines attached to this effort currently.
|
||||
.. It is currently consumed by QA teams that are working on identifying testing gaps. The label indicates that the changed code in this commit did not have any specific tests that target the affected area. Baseline testing (booting, functional, standard regression, etc.) is still performed and validated.
|
||||
|
||||
=== What does image:images/qsg-label_image_lnst_needsinfo.png["lnstNeedsInfo label"] indicate?
|
||||
:sectnums:
|
||||
.. This label indicates that the Merge Request has been identified by the Networking Team as requiring additional testing. Questions on network testing can be sent to mailto:kernel-net-submaint@redhat.com[kernel-net-submaint@redhat.com].
|
||||
|
||||
== MR Interactions
|
||||
:sectnums:
|
||||
=== How do I make the webhook re-evaluate the readiness of a MR?
|
||||
|
|
@ -102,3 +106,25 @@ image::images/qsg-faq-datawarehouse-search-for-builds.png["Search for Builds"]
|
|||
.. Find the most recent build and click the pipeline number +
|
||||
+
|
||||
image::images/qsg-faq-pipelines_jobs.png["Pipeline Jobs Links"]
|
||||
|
||||
=== When I attempt to click the new Merge Request link after a push, I get an error. How do I resolve it? +
|
||||
:sectnums:
|
||||
|
||||
Occasionally, when clicking the link that is provided after a `git push`, the browser page that opens returns an HTTP 500 error.
|
||||
|
||||
```
|
||||
500
|
||||
Whoops, something went wrong on our end.
|
||||
Request ID: 01GQ0QHBS01AZNMPGYFC0JBEG9
|
||||
|
||||
Try refreshing the page, or going back and attempting the action again.
|
||||
|
||||
Please contact your GitLab administrator if this problem persists.
|
||||
```
|
||||
|
||||
This is caused by an issue on the GitLab server side. Try the following steps to resolve or work around the problem:
|
||||
|
||||
. Retry after a few minutes. (Try this step a couple of times before moving on)
|
||||
.. Sometimes it can just be a transient problem and waiting 5-10 minutes may be enough to fix the problem.
|
||||
. Consider opening a https://gitlab.com/redhat/rhel/gitlab#user-content-service-issues[support ticket] with GitLab.
|
||||
. Work around the problem by using xref:lab.adoc[the lab utility] or https://gitlab.com/gitlab-org/cli[gitlab-cli].
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ Looking for the xref:faq.adoc[FAQ?]
|
|||
.. Red Hat Developers must be a member of the `redhat` bugzilla group to properly associate their account with GitLab.
|
||||
.. Red Hat Partner Engineers must be a member of `redhat_partner_engineer_staff` to properly associate their account with GitLab.
|
||||
+
|
||||
xref:rh_and_gitlab_configuration.adoc#partnerengineer[Required Permissions for Partner Engineers] +
|
||||
xref:rh_and_gitlab_configuration.adoc#partnerengineer[Required Permissions for Red Hat Partner Engineers] +
|
||||
[.small]_Look for "I'm using https://red.ht/GitLabSSO to login to GitLab and can see centos-stream and other public projects but cannot see the RHEL projects."_
|
||||
+
|
||||
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0009257[Instructions to Request Access]
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ Solutions:
|
|||
* Ensure there are no ‘pending approval’ requests outstanding for your account.
|
||||
* Make sure you are part of the Linux engineering “linux-eng” rover group. You can verify your inclusion on https://rover.redhat.com/groups[https://rover.redhat.com/groups] and select “My Groups”.
|
||||
|
||||
=== I am a Red Hat Employee or Partner Engineer and am trying to authenticate through the https://red.ht/GitLabSSO[SAML] link, but I get a "SAML authentication failed: Extern uid has already been taken" error.
|
||||
=== I am a Red Hat Employee or Red Hat Partner Engineer and am trying to authenticate through the https://red.ht/GitLabSSO[SAML] link, but I get a "SAML authentication failed: Extern uid has already been taken" error.
|
||||
Solution: If your redhat.com LDAP email was not associated with a Gitlab account when you clicked on the SAML link, it is possible that an account was created for just your LDAP email address. This situation is common for developers who use email addresses. You can resolve this issue by deleting the newly created LDAP account.
|
||||
|
||||
** Login into the newly created LDAP account with the password and https://docs.gitlab.com/ee/user/profile/account/delete_account.html[delete the account]. If you do not have the password, goto https://gitlab.com[https://gitlab.com], login in with the LDAP email address and reset the account’s password.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,155 @@
|
|||
---
|
||||
title: 'Bugzilla Lifecycle'
|
||||
date: 2022-11-28T12:00:00-04:00
|
||||
draft: false
|
||||
weight: 2
|
||||
summary: The Bugzilla/Kernel lifecycle
|
||||
---
|
||||
|
||||
= Bugzilla Lifecycle
|
||||
|
||||
For every modification against the RHEL kernel, an approved https://bugzilla.redhat.com[Bugzilla] (or BZ) is required for that change to make it into the release. This document provides an overview of a modification to the RHEL kernel from the perspective of the BZ and how it evolves through the journey.
|
||||
|
||||
The status journey on a BZ can be any one of the following values. Note that there are additional status settings, but they are not generally used.
|
||||
|
||||
It is not explicitly required that this process is followed in 100% order. Meaning, that a bugfix may be prepared ahead of the BZ being ready, but the overall process cannot be completed until each of the detailed steps below are completed and satisfied.
|
||||
|
||||
For guidance around the overall xref:rhel_kernel_workflow.adoc[Kernel Workflow] process, please visit the xref:readme.adoc[Quick Start Guide].
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
{toc}
|
||||
|
||||
== Step 1. BZ Opened
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/colored-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
As with every process, it must begin somewhere. For Bugzilla and the Kernel Workflow process, this status ends up being `NEW`. This indicates that the BZ is just that, new. It has not been reviewed, triaged, or considered for fixing or addressing yet.
|
||||
|
||||
BZ's that are in this state will be periodically reviewed by their current default assignee, which is determined by the component and sub-component that was chosen. A BZ may be transferred between multiple components and sub-components until the appropriate destination has been determined.
|
||||
|
||||
Every team has their own review process, but common to them all is that once a BZ has been triaged, it will then be moved to `ASSIGNED` to an individual to review and evaluate the BZ. As part of the triage process, a BZ can also just move directly to the `CLOSED` status if it is not appropriate to keep open. Reasons could be that the BZ has already been addressed (and therefore would be `CLOSED` -> `DUPLICATE`) or maybe it's something else (e.g. user error).
|
||||
|
||||
== Step 2. BZ Triaged and Scheduled
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/colored-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
Once a BZ has been triaged and `ASSIGNED` to an individual, they will review the details of it and identify what needs to be done. Assuming a change is required, the BZ will then be scheduled for a particular release, which requires setting a number of internal-only visible fields such as Development Target Milestone, Internal Target Milestone, and Internal Target Release.
|
||||
|
||||
In the most basic scenario (before ITM 26, and not for a Z-Stream), a BZ is approved once the `release+` flag is granted. For more information, visit the xref:readme.adoc#getreleaseapproval[Get Release Approval] section in the xref:readme.adoc[Quick Start Guide].
|
||||
|
||||
== Step 3. Change Prepared
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/colored-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
Once a change has been prepared for the kernel, it needs to be made available for review. To indicate that the update is ready to be looked at, the state of the BZ should be changed to `POST`. Almost along the lines of it being `POST`-ed to a bulletin board for people to see. This step will be automatically completed by the webhooks once the BZ has been detected in the description.
|
||||
|
||||
For the RHEL Kernel Workflow process, the update is provided via the GitLab Merge Request interface.
|
||||
|
||||
== Step 4. MR / GitLab Process
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/colored-POST.png["All Status"] a| image::images/colored-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
All changes to the RHEL kernel are done via the GitLab Merge Request interface. For more detailed information about this process, please visit the xref:readme.adoc[Quick Start Guide]. As soon as the web hooks in the GitLab infrastructure notices a referenced BZ in the description, a link will be added to the BZ pointing at the relevant Merge Request(s).
|
||||
|
||||
The loose process, however, looks like this:
|
||||
|
||||
. Tag all commits in the Merge Request as specified in the xref:commitrules.adoc[Commit Rules] document.
|
||||
. Open MR.
|
||||
. Obtain at least 2 reviews and reviews from the affected https://gitlab.com/redhat/centos-stream/src/kernel/documentation/-/blob/main/info/owners.yaml[code owners].
|
||||
. Verify the Continuous Kernel Integration (CKI) test has run and completed successfully.
|
||||
. Once all but the Bugzilla check labels receives the `::OK` status, the `readyForQA` label will be applied.
|
||||
.. This would include checks such as `Acks`, `Dependencies`, `Signoff`, etc.
|
||||
. Work with QE to properly set Verified field in BZ to `Tested`.
|
||||
. Upon the time where the MR receives the `::OK` status on *all* labels, the `readyForQA` label is removed and `readyForMerge` label is applied.
|
||||
. Kernel Maintainer pulls in the Merge Request once the `readyForMerge` label has been obtained.
|
||||
|
||||
== Step 5. QE Verifies the fix
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/colored-POST.png["All Status"] a| image::images/colored-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
Once the Merge Request has received sufficient reviews and the CKI test has passed, the `readyForQA` label will be applied to it. It is at this point that the BZ status will be moved from POST to `MODIFIED`. The assigned QE engineer will verify that the change does what was intended. This is typically done by using the reproduction steps that were noted in the BZ's description field when it was originally opened. From there, the QE Engineer will set the Verified Field to `Tested`.
|
||||
|
||||
== Step 6. Maintainers stage for the next build.
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/colored-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
After the BZ's Verified field is updated to `Tested` (or equivalent), the Merge Request should now have the `readyForMerge` label applied to it. This is the signal to the Kernel Maintainer that the merge request is ready to be pulled into a delivery candidate kernel build. When the update does get pulled in, the affected BZ statuses will be updated to `MODIFIED`.
|
||||
|
||||
== Step 7. New kernel is available
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/colored-MODIFIED.png["All Status"] a| image::images/colored-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
The maintainers assemble a new kernel periodically to deliver the various updates that they were provided. The schedule on this can vary, but when times are busy enough it's not uncommon to see a new kernel at least once per week. As part of this process, the kernel undergoes its own set of CKI tests just like every other Merge Request. Once the new kernel has gotten past the gating phase, it is tagged in the infrastructure to be used in the next upcoming composes. It is at this point that the BZ will transition from `MODIFIED` to `ON_QA` by adding it to an existing errata advisory.
|
||||
|
||||
== Step 8. QE Performs Final Verification
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/colored-ON_QA.png["All Status"] a| image::images/colored-VERIFIED.png["All Status"] a| image::images/clear-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
Just like in previous steps, when the BZ reaches the `ON_QA` status, it is a signal to QE that they can perform final verification of the BZ based on the description steps that were provided.A If everything checks out, the QE engineer will mark the BZ as `VERIFIED`. The BZ will remain in this state until it is released with an update for RHEL.
|
||||
|
||||
== Step 9. BZ Update is delivered with a release and finally the BZ is Closed
|
||||
|
||||
[frame=none, grid=none]
|
||||
|===
|
||||
|
||||
// Is there a way to make this cleaner? Seems like it all has to be on a single line, which is hard to read.
|
||||
a| image::images/clear-NEW.png["All Status"] a| image::images/clear-ASSIGNED.png["All Status"] a| image::images/clear-POST.png["All Status"] a| image::images/clear-MODIFIED.png["All Status"] a| image::images/clear-ON_QA.png["All Status"] a| image::images/clear-VERIFIED.png["All Status"] a| image::images/colored-CLOSED.png["All Status"]
|
||||
|
||||
|===
|
||||
|
||||
During the release process, all BZ's attached to the relevant errata advisories for a particular RHEL release will be closed. The BZ status is then updated to `CLOSED` and resolution `CURRENT_RELEASE`. It is at this point that the involvement of the BZ has concluded its responsibilities in relation to RHEL, the RHEL Kernel, and the issues that it addresses.
|
||||
|
|
@ -33,10 +33,10 @@ In general, users can submit an MR and use the CKI build artifacts. In cases wh
|
|||
make dist-brew
|
||||
----
|
||||
|
||||
Specific architectures can be built by setting the BREW_FLAGS variable. For example, to build the x86_64 and noarch architectures,
|
||||
Specific architectures can be built by setting the BUILD_FLAGS variable. For example, to build the x86_64 and noarch architectures,
|
||||
|
||||
----
|
||||
make dist-brew BREW_FLAGS="--arch-override=x86_64,noarch"
|
||||
make dist-brew BUILD_FLAGS="--arch-override=x86_64,noarch"
|
||||
----
|
||||
|
||||
== Command Help
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.8 KiB |
|
|
@ -12,7 +12,7 @@ There are many source-git and dist-git repositories that are used to construct R
|
|||
|
||||
=== source-git repositories
|
||||
|
||||
Public git repositories can be used by both Red Hat and non-Red Hat contributors. Private git repositories are restricted to Red Hat contributors and Partner contributors.
|
||||
Public git repositories can be used by Red Hat contributors, Community Contributors, and all Partner Engineer contributors. Private git repositories are restricted to Red Hat contributors and Partner contributors.
|
||||
|
||||
The general model of these repositories is that the main branch tracks the current minor development, and other branches track old minor development (commonly referred to as ‘z-stream’). Some repositories may also contain Real Time kernel branches that are tagged with “-rt”.
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ For example, the rhel-8 repository contains branches and the main branch (as of
|
|||
|
||||
=== dist-git repositories
|
||||
|
||||
Public git repositories can be used by both Red Hat and non-Red Hat contributors. Private git repositories are restricted to Red Hat contributors and Partner contributors.
|
||||
Public git repositories can be used by Red Hat contributors, Community Contributors, and all Partner Engineer contributors. Private git repositories are restricted to Red Hat contributors and Partner contributors.
|
||||
|
||||
|===
|
||||
|Name|Location|Type
|
||||
|
|
|
|||
|
|
@ -117,15 +117,11 @@ Abridged MR Submission Process
|
|||
|
||||
Addendum
|
||||
|
||||
While synchronizing your fork to the latest commit in origin is not
|
||||
necessary, it is annoying to see dozens of commits having nothing
|
||||
to do with your work being pushed to your fork, because it is out
|
||||
of sync with the origin.
|
||||
|
||||
If you want to update your fork before pushing your changes to it,
|
||||
a force push may be required depending on the state of your local
|
||||
branch or the remote branch. In which case, you must assure that
|
||||
it allows a forced push.
|
||||
Synchronizing your fork to the latest commit in origin is not necessary.
|
||||
However, if you want to update your fork before pushing your changes to it,
|
||||
a force push may be required depending on the state of your local branch or
|
||||
the remote branch. Therefore, you must assure that your remote fork allows
|
||||
a forced push.
|
||||
|
||||
* All your forks are listed at https://gitlab/<username>
|
||||
* Select one of your forks to synchronize.
|
||||
|
|
@ -135,4 +131,4 @@ it allows a forced push.
|
|||
* Click the 'Expand' button to the right of the 'Protected Branches' field
|
||||
* Scroll down to the bottom of that entry where it lists protected branches
|
||||
to the row starting with 'main'.
|
||||
* Slide the 'Allow to force push' to its 'ON' position.
|
||||
* Move the 'Allow to force push' slider to its 'ON' position.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,53 @@
|
|||
= Red Hat Kernel Team Policies and owners.yaml
|
||||
|
||||
|
||||
https://gitlab.com/redhat/centos-stream/src/kernel/documentation/-/blob/main/info/owners.yaml[owners.yaml] is a collection of data which maps which Red Hat SSTs (Sub System Team) are responsible for kernel technologies (aka subsystems) that Red Hat supports. The owners.yaml file includes other data such as Kernel technology maintainers and reviewers that is useful for the https://gitlab.com/cki-project/kernel-webhooks/[kernel-webhooks] and other utilities.
|
||||
|
||||
Two Red Hat Kernel Team policies are followed in the file:
|
||||
|
||||
== *Every Kernel technology must have at least one maintainer.*
|
||||
|
||||
* Devel Engineers are responsible for providing updates and debugging technologies. Maintainers are also responsible for reviewing code changes that impact their Kernel technologies.
|
||||
|
||||
== *Every Kernel technology is tracked by SSTs.*
|
||||
|
||||
* Red Hat is organized by SSTs and tracks work via SSTs. Having Kernel technologies aligned with this structure allows for better planning of efforts surrounding the technology. Engineers may change SSTs, maintainers may change over time, etc., but the technology must remain tracked by SSTs.
|
||||
|
||||
=== FAQ
|
||||
|
||||
|
||||
*Why is there a requirement that every Kernel technology have an SST tracking it?*
|
||||
|
||||
A technology must have at least one SST responsible for product decisions of the technology. In the case of more than one SST tracking a Kernel technology, SSTs should collaborate with other SSTs to provide feedback on product decisions.
|
||||
|
||||
*Why is there a requirement that every Kernel technology have a maintainer?*
|
||||
|
||||
Every file (code or CONFIG) is tracked to a Kernel technology and every Kernel technology is tracked by an SST. As a result, every kernel file will have an SST responsible for tracking product changes in RHEL, and every kernel file will have an maintainer responsible for approving or modifying changes to the kernel code.
|
||||
|
||||
*Does the maintainer or QE representative of a Kernel technology have to be in the SST(s) tracking the Kernel technology?*
|
||||
|
||||
No. Devel Engineers maintaining a Kernel technology may be part of or move to another SST, and the Devel Engineer may remain as a maintainer for the Kernel technology. The same holds true for QE Engineers; they may remain as the QE representative for a Kernel technology while being part of another SST.
|
||||
|
||||
SST Leads should communicate with all the SST Kernel technologies’ maintainers and QE representatives. SST meetings should also include all the SST Kernel technologies’ maintainers and QE representatives.
|
||||
|
||||
*Why does an SST and maintainer have to be assigned for disabled CONFIGs?*
|
||||
|
||||
An SST and maintainer are required to help make product decisions in case the CONFIG is enabled in RHEL.
|
||||
|
||||
*Can more than one SST be assigned to a Kernel technology?*
|
||||
|
||||
Yes. It is recommended that SSTs attempt to split the Kernel technology into different subsystems when this happens, however, it is not a requirement. It is also recommended that the SSTs coordinate efforts to avoid duplication of work and effort.
|
||||
|
||||
*Do I have to update my Rover SST group to indicate developers from other SSTs are helping?*
|
||||
|
||||
Rover Groups for SSTs can contain "members" for all individuals who work with that SST. In the case of Development Engineers, most of them are (and should be) focused on a single SST. It only makes sense to list a single Development Engineer in multiple Rover SSTs in very extenuating circumstances.
|
||||
|
||||
Unlike Development Engineers, members of QE, Docs, Support are often supporting multiple SSTs. So, it makes sense, for example, to have a single QE individual listed as a member of multiple SSTs in their respective Rover Groups. In these cases, please indicate in that QE member's *Role *in each Rover Group that they participate in, what specific things they test or do for that specific SST.
|
||||
|
||||
*How do I find the right QE representative?*
|
||||
|
||||
There are multiple ways to find a QE representative.
|
||||
|
||||
* Look at the https://rover.redhat.com/groups/search?q=rhel-sst-[Rover groups].
|
||||
* Look at the assigned QE person in a bugzilla associated with the technology.
|
||||
* Attend *any* SST meeting. A QE representative will be able to assist you with finding the representative for a technology.
|
||||
|
|
@ -10,6 +10,8 @@ summary: The RHEL Kernel Workflow is used by Red Hat-based kernel projects inclu
|
|||
|
||||
https://red.ht/kernel_workflow_doc[https://red.ht/kernel_workflow_doc]
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
The RHEL Kernel Workflow is used by Red Hat-based kernel projects including RHEL Kernels, CentOS Stream kernels, the Fedora kernel, and the Always Ready Kernel (ARK). The RHEL Kernel Workflow is built upon the standard https://docs.gitlab.com/ee/topics/gitlab_flow.html[GitLab workflow] and uses GitLab Merge Requests as the only way to make changes to the Red Hat kernel.
|
||||
|
||||
At Red Hat, all work is directed through the analysis of user bug reports. Contributors (ie, engineers) review bugs and identify work to be completed for each bug. For each bug, a contributor codes a fix and submits the code for review. Reviewers analyze the fix, and when they are satisfied with the fix, the maintainers accept the fix into the codebase. The modified codebase is tested by Quality Engineering, and when they are satisfied with the results of testing, the Documentation team will document the changes for our customers.
|
||||
|
|
@ -48,7 +50,7 @@ dist-git: A packaging git tree used by distro package maintainers. A git reposi
|
|||
|
||||
== Roles
|
||||
|
||||
There are five roles (Red Hat Contributor, Red Hat Partner Contributor, Non-Red Hat Contributor, Red Hat Maintainer, and Red Hat Management) in the Kernel Workflow. The Kernel Workflow has three levels of public exposure for projects (Public, _Private_, and Secret). These projects all have source-git repositories, but only Public projects also have a dist-git repository. Two of these Public projects are the CentOS Stream and RHEL Kernels.
|
||||
There are five roles (Red Hat Contributor, Red Hat Partner Contributor, Community or Stream Partner Engineer Contributor, Red Hat Maintainer, and Red Hat Management) in the Kernel Workflow. The Kernel Workflow has three levels of public exposure for projects (Public, _Private_, and Secret). These projects all have source-git repositories, but only Public projects also have a dist-git repository. Two of these Public projects are the CentOS Stream and RHEL Kernels.
|
||||
|
||||
Each role will require a different level of code access. For example, Maintainers will require access to both source-git and dist-git repositories, while Management may only require access to statistical information from the source-git repositories.
|
||||
|
||||
|
|
@ -66,9 +68,9 @@ Red Hat employees can contribute to the Red Hat kernel GitLab projects as Develo
|
|||
|
||||
Red Hat Partners can contribute to Red Hat kernel GitLab projects as Developers, and in some cases, as Reviewers. See the <<Contributor>> section for more details.
|
||||
|
||||
==== Non-Red Hat Contributor
|
||||
==== Community Contributor or Stream Partner Engineers Contributor
|
||||
|
||||
Non-Red Hat Contributors can contribute to the Red Hat kernel GitLab projects as Guests. They have restricted CI and review capabilities. See the <<Contributor>> section for more details.
|
||||
Community Contributors or Stream Partner Engineer Contributors can contribute to the Red Hat kernel GitLab projects as Guests. They have restricted CI and review capabilities. See the <<Contributor>> section for more details.
|
||||
|
||||
==== Red Hat Maintainer
|
||||
|
||||
|
|
@ -93,7 +95,7 @@ Contributors may both provide and review code to Red Hat kernel projects via Git
|
|||
|
||||
==== Setup
|
||||
|
||||
New users should follow the <<Account Setup & Configuration>> and configure link:rhel_kernel_workflow.adoc#Tools[tooling for working with the Red Hat kernel trees] sections below. Advanced users may optionally reference the link:README.adoc[Developer Quick Start Guide].
|
||||
New users should follow the <<Account Setup & Configuration>> and configure link:rhel_kernel_workflow.adoc#user-content-tools[tooling for working with the Red Hat kernel trees] sections below. Advanced users may optionally reference the link:README.adoc[Developer Quick Start Guide].
|
||||
|
||||
==== Developers for RHEL
|
||||
|
||||
|
|
@ -197,7 +199,7 @@ Contributors can follow link:general_build_instructions.adoc[these instructions]
|
|||
|
||||
==== Submitting a Merge Request
|
||||
|
||||
Contributors can follow these general https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html[instructions on submitting an MR] using the GitLab UI. Contributors to RHEL kernel projects should also follow these Red Hat specific instructions on link:lab.adoc[lab] GitLab command line tool can also be used to submit Merge Requests.
|
||||
Contributors can follow these general https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html[instructions on submitting an MR] using the GitLab UI. Contributors to RHEL kernel projects should also follow these Red Hat specific instructions of the link:CommitRules.adoc[Commit Rules]. The link:lab.adoc[lab] GitLab command line tool can also be used to submit Merge Requests.
|
||||
|
||||
The <<Kernel-webhooks>> will automatically assign reviewers based on the changeset's code content. Changesets that modify many subsystems or drivers will result in a large number of reviewers assigned to the merge request. To avoid this problem it is strongly encouraged that Merge Request Authors follow upstream's guidance on separating code changes: "https://www.kernel.org/doc/html/latest/process/submitting-patches.html#separate-your-changes[If you cannot condense your patch set into a smaller set of patches, then only post say 15 or so at a time and wait for review and integration]".
|
||||
|
||||
|
|
@ -213,7 +215,7 @@ All reviews can be completed through the GitLab WebUI. Red Hat recommends the G
|
|||
|
||||
Red Hat Employee Contributors can follow the link:merge_request_approvals_and_blocks.adoc[Merge Request Approval Procedure]. In some cases, Red Hat Partner Contributors may be asked by their manager to also review Merge Requests.
|
||||
|
||||
Non-Red Hat Contributors are able to participate in discussions but do not have the ability to approve or block merge requests.
|
||||
Community Contributors and Stream Partner Engineer Contributors are able to participate in discussions but do not have the ability to approve or block merge requests.
|
||||
|
||||
==== Finding Merge Requests to review
|
||||
|
||||
|
|
@ -247,7 +249,7 @@ Instructions for https://bugzilla.redhat.com/docs/en/html/using/filing.html#repo
|
|||
|
||||
All Red Hat Kernels are hosted on GitLab so all contributors must set up a GitLab account to contribute to the Red Hat Kernel. Red Hat Employees are granted Developer and Reviewer status by default, and Maintainer status if necessary. Red Hat Partner Engineers are granted Developers status by default.
|
||||
|
||||
*Red Hat contributors to Red Hat Kernel projects must link:RH_and_GitLab_Configuration.adoc[configure a Red Hat GitLab account] and submit merge requests through that account. Non-Red Hat contributors to Red Hat Kernel Projects must configure a GitLab account(TBD).*
|
||||
*Red Hat contributors to Red Hat Kernel projects must link:RH_and_GitLab_Configuration.adoc[configure a Red Hat GitLab account] and submit merge requests through that account. Community Contributors or Stream Partner Engineer contributors to Red Hat Kernel Projects must configure a GitLab account(TBD).*
|
||||
|
||||
== Tools
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,9 @@
|
|||
|
||||
[ARK Kernel Maintainer]
|
||||
makefile jforbes@redhat.com jforbes@fedoraproject.org ptalbert@redhat.com
|
||||
Makefile.rhelver jforbes@redhat.com jforbes@fedoraproject.org ptalbert@redhat.com
|
||||
redhat/ jforbes@redhat.com jforbes@fedoraproject.org ptalbert@redhat.com
|
||||
^redhat/configs/ jforbes@redhat.com jforbes@fedoraproject.org ptalbert@redhat.com
|
||||
|
||||
[ARK Real Time Kernel Maintainer]
|
||||
makefile williams@redhat.com ahalaney@redhat.com
|
||||
Makefile.rhelver williams@redhat.com ahalaney@redhat.com
|
||||
redhat/ williams@redhat.com ahalaney@redhat.com
|
||||
^redhat/configs/ williams@redhat.com ahalaney@redhat.com
|
||||
|
||||
[Automotive Stream Distribution Kernel Maintainer]
|
||||
makefile jfaracco@redhat.com scweaver@redhat.com
|
||||
|
|
@ -18,152 +12,85 @@ redhat/ jfaracco@redhat.com scweaver@redhat.com
|
|||
^redhat/configs/ jfaracco@redhat.com scweaver@redhat.com
|
||||
|
||||
[CentOS Stream 9 Kernel Maintainer]
|
||||
makefile fhrbata@redhat.com
|
||||
Makefile.rhelver fhrbata@redhat.com
|
||||
redhat/ fhrbata@redhat.com
|
||||
^redhat/configs/ fhrbata@redhat.com
|
||||
Makefile.rhelver herton@redhat.com
|
||||
|
||||
[CentOS Stream 9 Real Time Kernel Maintainer]
|
||||
makefile lgoncalv@redhat.com
|
||||
Makefile.rhelver lgoncalv@redhat.com
|
||||
redhat/ lgoncalv@redhat.com
|
||||
^redhat/configs/ lgoncalv@redhat.com
|
||||
|
||||
[RHEL 9.1 Kernel Maintainer]
|
||||
makefile ptalbert@redhat.com
|
||||
Makefile.rhelver ptalbert@redhat.com
|
||||
redhat/ ptalbert@redhat.com
|
||||
^redhat/configs/ ptalbert@redhat.com
|
||||
|
||||
[RHEL/ARK/Centos-Stream General Kernel Reviewers]
|
||||
makefile
|
||||
Makefile.rhelver
|
||||
redhat/
|
||||
^redhat/configs/
|
||||
makefile herton@redhat.com jforbes@fedoraproject.org
|
||||
redhat/ herton@redhat.com jforbes@fedoraproject.org
|
||||
Kconfig.redhat herton@redhat.com jforbes@fedoraproject.org
|
||||
^redhat/configs/ herton@redhat.com jforbes@fedoraproject.org
|
||||
|
||||
[RHEL 9.1 Real Time Kernel Maintainer]
|
||||
makefile lgoncalv@redhat.com
|
||||
Makefile.rhelver lgoncalv@redhat.com
|
||||
redhat/ lgoncalv@redhat.com
|
||||
^redhat/configs/ lgoncalv@redhat.com
|
||||
|
||||
[RHEL 9.0 Kernel Maintainer]
|
||||
makefile herton@redhat.com
|
||||
Makefile.rhelver herton@redhat.com
|
||||
redhat/ herton@redhat.com
|
||||
^redhat/configs/ herton@redhat.com
|
||||
Makefile.rhelver jstancek@redhat.com
|
||||
|
||||
[RHEL 9.0 Real Time Kernel Maintainer]
|
||||
makefile lgoncalv@redhat.com lleshchi@redhat.com
|
||||
Makefile.rhelver lgoncalv@redhat.com lleshchi@redhat.com
|
||||
redhat/ lgoncalv@redhat.com lleshchi@redhat.com
|
||||
^redhat/configs/ lgoncalv@redhat.com lleshchi@redhat.com
|
||||
|
||||
[RHEL 8.8 Kernel Maintainer]
|
||||
makefile lzampier@redhat.com
|
||||
Makefile.rhelver lzampier@redhat.com
|
||||
redhat/ lzampier@redhat.com
|
||||
^redhat/configs/ lzampier@redhat.com
|
||||
|
||||
[RHEL 8.8 Real Time Kernel Maintainer]
|
||||
makefile jwyatt@redhat.com chwhite@redhat.com
|
||||
Makefile.rhelver jwyatt@redhat.com chwhite@redhat.com
|
||||
redhat/ jwyatt@redhat.com chwhite@redhat.com
|
||||
^redhat/configs/ jwyatt@redhat.com chwhite@redhat.com
|
||||
|
||||
[RHEL 8.7 Kernel Maintainer]
|
||||
makefile jarod@redhat.com
|
||||
Makefile.rhelver jarod@redhat.com
|
||||
redhat/ jarod@redhat.com
|
||||
^redhat/configs/ jarod@redhat.com
|
||||
|
||||
[RHEL 8.7 Real Time Kernel Maintainer]
|
||||
makefile chwhite@redhat.com
|
||||
Makefile.rhelver chwhite@redhat.com
|
||||
redhat/ chwhite@redhat.com
|
||||
^redhat/configs/ chwhite@redhat.com
|
||||
|
||||
[RHEL 8.6 Kernel Maintainer]
|
||||
makefile acaringi@redhat.com
|
||||
Makefile.rhelver acaringi@redhat.com
|
||||
redhat/ acaringi@redhat.com
|
||||
^redhat/configs/ acaringi@redhat.com
|
||||
|
||||
[RHEL 8.6 Real Time Kernel Maintainer]
|
||||
makefile chwhite@redhat.com
|
||||
Makefile.rhelver chwhite@redhat.com
|
||||
redhat/ chwhite@redhat.com
|
||||
^redhat/configs/ chwhite@redhat.com
|
||||
|
||||
[RHEL 8.4 Kernel Maintainer]
|
||||
makefile scweaver@redhat.com
|
||||
Makefile.rhelver scweaver@redhat.com
|
||||
redhat/ scweaver@redhat.com
|
||||
^redhat/configs/ scweaver@redhat.com
|
||||
|
||||
[RHEL 8.4 Real Time Kernel Maintainer]
|
||||
makefile debarbos@redhat.com
|
||||
Makefile.rhelver debarbos@redhat.com
|
||||
redhat/ debarbos@redhat.com
|
||||
^redhat/configs/ debarbos@redhat.com
|
||||
|
||||
[RHEL 8.2 Kernel Maintainer]
|
||||
makefile jfaracco@redhat.com
|
||||
Makefile.rhelver jfaracco@redhat.com
|
||||
redhat/ jfaracco@redhat.com
|
||||
^redhat/configs/ jfaracco@redhat.com
|
||||
|
||||
[RHEL 8.2 Real Time Kernel Maintainer]
|
||||
makefile tyberry@redhat.com
|
||||
Makefile.rhelver tyberry@redhat.com
|
||||
redhat/ tyberry@redhat.com
|
||||
^redhat/configs/ tyberry@redhat.com
|
||||
|
||||
[RHEL 8.1 Kernel Maintainer]
|
||||
makefile scweaver@redhat.com
|
||||
Makefile.rhelver scweaver@redhat.com
|
||||
redhat/ scweaver@redhat.com
|
||||
^redhat/configs/ scweaver@redhat.com
|
||||
|
||||
[RHEL 7.9 Kernel Maintainer]
|
||||
makefile rvrbovsk@redhat.com
|
||||
redhat/ rvrbovsk@redhat.com
|
||||
^redhat/configs/ rvrbovsk@redhat.com
|
||||
Makefile rvrbovsk@redhat.com
|
||||
|
||||
[RHEL 7.9 Real Time Kernel Maintainer]
|
||||
makefile swood@redhat.com
|
||||
redhat/ swood@redhat.com
|
||||
^redhat/configs/ swood@redhat.com
|
||||
Makefile swood@redhat.com
|
||||
|
||||
[RHEL 7.7 Kernel Maintainer]
|
||||
makefile rvrbovsk@redhat.com
|
||||
redhat/ rvrbovsk@redhat.com
|
||||
^redhat/configs/ rvrbovsk@redhat.com
|
||||
Makefile rvrbovsk@redhat.com
|
||||
|
||||
[RHEL 7.6 Kernel Maintainer]
|
||||
makefile dvlasenk@redhat.com
|
||||
redhat/ dvlasenk@redhat.com
|
||||
^redhat/configs/ dvlasenk@redhat.com
|
||||
Makefile dvlasenk@redhat.com
|
||||
|
||||
[RHEL 7.6 Real Time Kernel Maintainer]
|
||||
makefile lgoncalv@redhat.com
|
||||
redhat/ lgoncalv@redhat.com
|
||||
^redhat/configs/ lgoncalv@redhat.com
|
||||
Makefile lgoncalv@redhat.com
|
||||
|
||||
[RHEL 7.4 Kernel Maintainer]
|
||||
makefile dvlasenk@redhat.com
|
||||
redhat/ dvlasenk@redhat.com
|
||||
^redhat/configs/ dvlasenk@redhat.com
|
||||
Makefile dvlasenk@redhat.com
|
||||
|
||||
[RHEL 7.3 Kernel Maintainer]
|
||||
makefile dvlasenk@redhat.com
|
||||
redhat/ dvlasenk@redhat.com
|
||||
^redhat/configs/ dvlasenk@redhat.com
|
||||
Makefile dvlasenk@redhat.com
|
||||
|
||||
[RHEL 6.10 Kernel Maintainer]
|
||||
makefile dvlasenk@redhat.com
|
||||
redhat/ dvlasenk@redhat.com
|
||||
^redhat/configs/ dvlasenk@redhat.com
|
||||
Makefile dvlasenk@redhat.com
|
||||
|
||||
^[3ware 9000 Storage Controller Linux Driver (3w-9xxx)]
|
||||
drivers/scsi/3w-9xxx* thenzl@redhat.com
|
||||
|
|
@ -175,7 +102,7 @@ drivers/net/ethernet/realtek/8139cp.c ivecera@redhat.com
|
|||
drivers/net/ethernet/realtek/r8169* jtornosm@redhat.com
|
||||
|
||||
^[ACCESSIBILITY SUBSYSTEM]
|
||||
drivers/accessibility/ torez@redhat.com dledford@redhat.com prarit@redhat.com
|
||||
drivers/accessibility/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[ACPI SUBSYSTEM]
|
||||
drivers/acpi/ mlangsdo@redhat.com lszubowi@redhat.com prarit@redhat.com darcari@redhat.com
|
||||
|
|
@ -211,15 +138,15 @@ Documentation/networking/device_drivers/ethernet/amazon/ena.rst joskera@redhat.c
|
|||
drivers/net/ethernet/amazon/ joskera@redhat.com
|
||||
|
||||
^[AMAZON RDMA EFA DRIVER (efa)]
|
||||
drivers/infiniband/hw/efa/ kheib@redhat.com
|
||||
include/uapi/rdma/efa-abi.h kheib@redhat.com
|
||||
drivers/infiniband/hw/efa/ ibakolla@redhat.com kheib@redhat.com
|
||||
include/uapi/rdma/efa-abi.h ibakolla@redhat.com kheib@redhat.com
|
||||
|
||||
[AMD IOMMU (AMD-VI)]
|
||||
drivers/iommu/amd/ jsnitsel@redhat.com
|
||||
include/linux/amd-iommu.h jsnitsel@redhat.com
|
||||
|
||||
^[AMD PTDMA DRIVER]
|
||||
drivers/dma/ptdma linville@redhat.com mstowe@redhat.com
|
||||
drivers/dma/ptdma/ linville@redhat.com mstowe@redhat.com
|
||||
|
||||
^[AMD SEV/SEV-ES/SEV-SNP Guest Side]
|
||||
arch/x86/boot/compressed/sev*.c vkuznets@redhat.com wehuang@redhat.com
|
||||
|
|
@ -317,13 +244,19 @@ block/ ming.lei@redhat.com jmoyer@redhat.com vgoyal@redhat.com
|
|||
drivers/block/ ming.lei@redhat.com jmoyer@redhat.com vgoyal@redhat.com
|
||||
|
||||
^[BLUETOOTH SUBSYSTEM]
|
||||
drivers/bluetooth/ gtiwari@redhat.com
|
||||
include/net/bluetooth/ gtiwari@redhat.com
|
||||
net/bluetooth/ gtiwari@redhat.com
|
||||
drivers/bluetooth/ dmarlin@redhat.com
|
||||
include/net/bluetooth/ dmarlin@redhat.com
|
||||
net/bluetooth/ dmarlin@redhat.com
|
||||
|
||||
^[BONDING DRIVER]
|
||||
Documentation/networking/bonding.rst jtoppins@redhat.com
|
||||
drivers/net/bonding/ jtoppins@redhat.com
|
||||
include/linux/if_bonding.h jtoppins@redhat.com
|
||||
include/net/bond_3ad.h jtoppins@redhat.com
|
||||
include/net/bond_alb.h jtoppins@redhat.com
|
||||
include/net/bonding.h jtoppins@redhat.com
|
||||
include/net/bond_options.h jtoppins@redhat.com
|
||||
include/uapi/linux/if_bonding.h jtoppins@redhat.com
|
||||
tools/testing/selftests/drivers/net/bonding/ jtoppins@redhat.com
|
||||
|
||||
^[BPF (Safe dynamic programs and tools)]
|
||||
arch/*/net/* ykaliuta@redhat.com
|
||||
|
|
@ -332,6 +265,11 @@ include/linux/filter.h ykaliuta@redhat.com
|
|||
include/trace/events/xdp.h ykaliuta@redhat.com
|
||||
include/uapi/linux/filter.h ykaliuta@redhat.com
|
||||
net/core/filter.c ykaliuta@redhat.com
|
||||
^Documentation/devicetree/bindings/dma/*nbpfaxi* ykaliuta@redhat.com
|
||||
^drivers/dma/*nbpfaxi* ykaliuta@redhat.com
|
||||
^drivers/media/i2c/sony-btf-mpx.c ykaliuta@redhat.com
|
||||
^drivers/staging/fbtft/ ykaliuta@redhat.com
|
||||
^include/dt-bindings/dma/*nbpfaxi* ykaliuta@redhat.com
|
||||
^net/bpfilter/ ykaliuta@redhat.com
|
||||
|
||||
^[BROADCOM B44 10/100 ETHERNET DRIVER]
|
||||
|
|
@ -350,8 +288,8 @@ drivers/net/ethernet/broadcom/bnxt/ jkc@redhat.com
|
|||
drivers/net/ethernet/broadcom/Kconfig jkc@redhat.com
|
||||
|
||||
^[BROADCOM BNXT_RE RDMA ROCE DRIVER]
|
||||
drivers/infiniband/hw/bnxt_re/ sxavier@redhat.com
|
||||
include/uapi/rdma/bnxt_re-abi.h sxavier@redhat.com
|
||||
drivers/infiniband/hw/bnxt_re/ sxavier@redhat.com kheib@redhat.com
|
||||
include/uapi/rdma/bnxt_re-abi.h sxavier@redhat.com kheib@redhat.com
|
||||
|
||||
^[Broadcom NetXtreme II BCM5706/5708/5709/57710/57711/57712/57800/57810/57840 iSCSI Driver]
|
||||
drivers/scsi/bnx2i/ mlombard@redhat.com
|
||||
|
|
@ -362,6 +300,10 @@ drivers/scsi/bnx2fc/ mlombard@redhat.com
|
|||
^[Broadcom NetXtreme II CNIC Driver (cnic)]
|
||||
drivers/net/ethernet/broadcom/cnic* mlombard@redhat.com
|
||||
|
||||
^[Broadcom specific AMBA]
|
||||
drivers/bcma/ jtornosm@redhat.com mschmidt@redhat.com
|
||||
include/linux/bcma/ jtornosm@redhat.com mschmidt@redhat.com
|
||||
|
||||
^[BROADCOM TG3 GIGABIT ETHERNET DRIVER]
|
||||
drivers/net/ethernet/broadcom/tg3.* jkc@redhat.com
|
||||
drivers/net/ethernet/broadcom/Kconfig jkc@redhat.com
|
||||
|
|
@ -399,13 +341,19 @@ drivers/misc/ dledford@redhat.com prarit@redhat.com
|
|||
include/linux/miscdevice.h dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[CIFS FILESYSTEM]
|
||||
fs/cifs/
|
||||
fs/cifs/ lsahlber@redhat.com
|
||||
|
||||
^[CISCO FCOE HBA (fnic)]
|
||||
drivers/scsi/fnic/ cleech@redhat.com
|
||||
|
||||
^[CISCO VIC ETHERNET NIC DRIVER]
|
||||
drivers/net/ethernet/cisco/enic/ gvaradar@redhat.com
|
||||
drivers/net/ethernet/cisco/enic/ mschmidt@redhat.com
|
||||
|
||||
^[CLOCKSOURCE]
|
||||
drivers/clocksource/ msalter@redhat.com
|
||||
^drivers/clocksource/hyperv_timer.c msalter@redhat.com
|
||||
^drivers/clocksource/arm_arch_timer.c msalter@redhat.com
|
||||
^drivers/clocksource/timer-qcom.c msalter@redhat.com
|
||||
|
||||
^[COMMON CLK FRAMEWORK]
|
||||
Documentation/devicetree/bindings/clock/ msalter@redhat.com
|
||||
|
|
@ -424,8 +372,11 @@ Documentation/driver-api/cxl/memory-devices.rst mstowe@redhat.com linville@redha
|
|||
fs/configfs/ rpeterso@redhat.com
|
||||
include/linux/configfs.h rpeterso@redhat.com
|
||||
|
||||
^[CONNECTOR]
|
||||
drivers/connector/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
[Continuous Integration (CKI)]
|
||||
.gitlab-ci.yml vkabatov@redhat.com mhofmann@redhat.com sturivny@redhat.com
|
||||
.gitlab-ci.yml tcalanch@redhat.com mhofmann@redhat.com sturivny@redhat.com
|
||||
|
||||
^[CONTROL GROUP (CGROUP)]
|
||||
Documentation/cgroup* longman@redhat.com
|
||||
|
|
@ -451,15 +402,15 @@ drivers/cpufreq/ mlangsdo@redhat.com lszubowi@redhat.com prarit@redhat.com darca
|
|||
[CPU IDLE DRIVERS]
|
||||
drivers/cpuidle/ mlangsdo@redhat.com prarit@redhat.com darcari@redhat.com
|
||||
|
||||
^[CRYPTO API]
|
||||
Documentation/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
Documentation/devicetree/bindings/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
arch/*/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
drivers/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
include/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
include/linux/crypto* herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
lib/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com
|
||||
[CRYPTO API]
|
||||
Documentation/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
Documentation/devicetree/bindings/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
arch/*/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
drivers/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
include/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
include/linux/crypto* herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
lib/crypto/ herbert.xu@redhat.com davem@redhat.com vdronov@redhat.com cllang@redhat.com simo@redhat.com
|
||||
|
||||
^[CXGB3 ETHERNET DRIVER (cxgb3)]
|
||||
drivers/net/ethernet/chelsio/cxgb3/ mschmidt@redhat.com
|
||||
|
|
@ -468,8 +419,8 @@ drivers/net/ethernet/chelsio/cxgb3/ mschmidt@redhat.com
|
|||
drivers/net/ethernet/chelsio/cxgb4/ mschmidt@redhat.com
|
||||
|
||||
^[CXGB4 IWARP DRIVER (IW_CXGB4)]
|
||||
drivers/infiniband/hw/cxgb4/ mschmidt@redhat.com
|
||||
include/uapi/rdma/cxgb4-abi.h mschmidt@redhat.com
|
||||
drivers/infiniband/hw/cxgb4/ rlakkire@redhat.com kheib@redhat.com
|
||||
include/uapi/rdma/cxgb4-abi.h rlakkire@redhat.com kheib@redhat.com
|
||||
|
||||
^[DCA SUBSYSTEM]
|
||||
drivers/dca/ jsnitsel@redhat.com
|
||||
|
|
@ -528,7 +479,8 @@ drivers/edac/ arozansk@redhat.com
|
|||
drivers/scsi/lpfc/ emilne@redhat.com
|
||||
|
||||
^[ETHERNET]
|
||||
drivers/net/ethernet/
|
||||
drivers/net/ethernet/ mschmidt@redhat.com
|
||||
^drivers/net/ethernet/microsoft/ mschmidt@redhat.com
|
||||
|
||||
^[ETHERNET BRIDGE]
|
||||
net/bridge/ ivecera@redhat.com haliu@redhat.com
|
||||
|
|
@ -536,9 +488,11 @@ include/linux/if_bridge.h ivecera@redhat.com haliu@redhat.com
|
|||
|
||||
^[ETHERNET PHY LIBRARY]
|
||||
Documentation/networking/phy.rst poros@redhat.com
|
||||
drivers/net/mdio/ poros@redhat.com
|
||||
drivers/net/phy/ poros@redhat.com
|
||||
drivers/of/of_mdio.c poros@redhat.com
|
||||
include/linux/*mdio*.h poros@redhat.com
|
||||
include/linux/mdio/ poros@redhat.com
|
||||
include/linux/phy.h poros@redhat.com
|
||||
include/linux/phy_fixed.h poros@redhat.com
|
||||
include/linux/platform_data/mdio-bcm-unimac.h poros@redhat.com
|
||||
|
|
@ -574,7 +528,6 @@ fs/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.
|
|||
^fs/ceph/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/cifs/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/configfs/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/cramfs/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/dax.c bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/direct-io.c bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
^fs/dlm/ bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
|
|
@ -624,6 +577,9 @@ kernel/futex/ longman@redhat.com
|
|||
tools/perf/bench/futex* longman@redhat.com
|
||||
tools/testing/selftests/futex/ longman@redhat.com
|
||||
|
||||
^[GCOV]
|
||||
kernel/gcov/ jstancek@redhat.com
|
||||
|
||||
^[GENERIC PHY FRAMEWORK]
|
||||
Documentation/devicetree/bindings/phy/ poros@redhat.com
|
||||
drivers/phy/ poros@redhat.com
|
||||
|
|
@ -634,6 +590,10 @@ Documentation/filesystems/gfs2*.txt rpeterso@redhat.com agruenba@redhat.com
|
|||
fs/gfs2/ rpeterso@redhat.com agruenba@redhat.com
|
||||
include/uapi/linux/gfs2_ondisk.h rpeterso@redhat.com agruenba@redhat.com
|
||||
|
||||
^[GNSS SUBSYSTEM]
|
||||
drivers/gnss/ mschmidt@redhat.com
|
||||
include/linux/gnss.h mschmidt@redhat.com
|
||||
|
||||
^[GPIO SUBSYSTEM]
|
||||
Documentation/ABI/obsolete/sysfs-gpio bmasney@redhat.com darcari@redhat.com
|
||||
Documentation/ABI/testing/gpio-cdev bmasney@redhat.com darcari@redhat.com
|
||||
|
|
@ -658,11 +618,20 @@ drivers/hwspinlock/ dledford@redhat.com prarit@redhat.com
|
|||
^[HARDWARE TRACING FACILITIES]
|
||||
drivers/hwtracing/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[HIBERNATION (aka Software Suspend, aka swsusp)]
|
||||
kernel/power/ lszubowi@redhat.com
|
||||
|
||||
^[HID CORE LAYER]
|
||||
drivers/hid/ benjamin.tissoires@redhat.com
|
||||
include/linux/hid* benjamin.tissoires@redhat.com
|
||||
include/uapi/linux/hid* benjamin.tissoires@redhat.com
|
||||
|
||||
^[HTE SUBSYSTEM (HARDWARE TIMESTAMP ENGINE)]
|
||||
Documentation/devicetree/bindings/timestamp/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
Documentation/driver-api/hte/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
drivers/hte/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
include/linux/hte.h athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
|
||||
^[HWMON SUBSYSTEM]
|
||||
drivers/hwmon/ dnelson@redhat.com
|
||||
|
||||
|
|
@ -672,14 +641,14 @@ mm/hwpoison-inject.c dnelson@redhat.com
|
|||
|
||||
^[Hyper-V CORE AND DRIVERS]
|
||||
Documentation/networking/device_drivers/microsoft/netvsc.txt cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/arm64/hyperv cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/arm64/hyperv/ cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/arm64/include/asm/hyperv-tlfs.h cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/arm64/include/asm/mshyperv.h cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/include/asm/mshyperv.h cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/include/asm/trace/hyperv.h cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/include/asm/hyperv-tlfs.h cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/kernel/cpu/mshyperv.c cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/hyperv cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
arch/x86/hyperv/ cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
drivers/clocksource/hyperv_timer.c cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
drivers/hid/hid-hyperv.c cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
drivers/hv/ cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
|
|
@ -702,13 +671,13 @@ Documentation/ABI/stable/sysfs-bus-vmbus cavery@redhat.com mgamal@redhat.com vku
|
|||
Documentation/ABI/testing/debugfs-hyperv cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
|
||||
^[I2C SUBSYSTEM]
|
||||
Documentation/devicetree/bindings/i2c/ gtiwari@redhat.com darcari@redhat.com
|
||||
Documentation/i2c/ gtiwari@redhat.com darcari@redhat.com
|
||||
drivers/i2c/ gtiwari@redhat.com darcari@redhat.com
|
||||
include/linux/i2c.h gtiwari@redhat.com darcari@redhat.com
|
||||
include/linux/i2c-*.h gtiwari@redhat.com darcari@redhat.com
|
||||
include/uapi/linux/i2c.h gtiwari@redhat.com darcari@redhat.com
|
||||
include/uapi/linux/i2c-*.h gtiwari@redhat.com darcari@redhat.com
|
||||
Documentation/devicetree/bindings/i2c/ darcari@redhat.com
|
||||
Documentation/i2c/ darcari@redhat.com
|
||||
drivers/i2c/ darcari@redhat.com
|
||||
include/linux/i2c.h darcari@redhat.com
|
||||
include/linux/i2c-*.h darcari@redhat.com
|
||||
include/uapi/linux/i2c.h darcari@redhat.com
|
||||
include/uapi/linux/i2c-*.h darcari@redhat.com
|
||||
|
||||
^[INDUSTRIAL I/O SUBSYSTEM (IIO)]
|
||||
drivers/iio/ dledford@redhat.com prarit@redhat.com
|
||||
|
|
@ -719,6 +688,8 @@ include/rdma/ kheib@redhat.com
|
|||
include/uapi/rdma/ kheib@redhat.com
|
||||
include/uapi/linux/if_infiniband.h kheib@redhat.com
|
||||
Documentation/infiniband/ kheib@redhat.com
|
||||
include/linux/mlx4/ kheib@redhat.com
|
||||
include/linux/mlx5/ kheib@redhat.com
|
||||
|
||||
^[INIT]
|
||||
init/ prarit@redhat.com
|
||||
|
|
@ -744,6 +715,11 @@ drivers/net/ethernet/intel/e1000e/ jkc@redhat.com
|
|||
|
||||
^[INTEL ETHERNET CONNECTION E800 SERIES (ice)]
|
||||
drivers/net/ethernet/intel/ice/ poros@redhat.com
|
||||
include/linux/net/intel/ poros@redhat.com
|
||||
|
||||
^[INTEL ETHERNET PROTOCOL DRIVER FOR RDMA (irdma)]
|
||||
drivers/infiniband/hw/irdma/ kheib@redhat.com
|
||||
include/uapi/rdma/irdma-abi.h kheib@redhat.com
|
||||
|
||||
^[INTEL I40E ETHERNET DRIVERS (i40e)]
|
||||
drivers/net/ethernet/intel/i40e/ ivecera@redhat.com
|
||||
|
|
@ -786,7 +762,7 @@ drivers/counter/intel-qep.c prarit@redhat.com darcari@redhat.com
|
|||
drivers/crypto/qat/ vdronov@redhat.com tcamuso@redhat.com
|
||||
|
||||
[INTEL RAPL DRIVER]
|
||||
drivers/powercap/intel_rapl.c prarit@redhat.com darcari@redhat.com
|
||||
drivers/powercap/intel* prarit@redhat.com darcari@redhat.com
|
||||
|
||||
^[INTERPROCESS COMMUNICATION (IPC)]
|
||||
include/linux/ipc*.h arozansk@redhat.com aquini@redhat.com longman@redhat.com
|
||||
|
|
@ -828,6 +804,10 @@ kernel/irq/ prarit@redhat.com darcari@redhat.com msalter@redhat.com
|
|||
drivers/scsi/*iscsi* cleech@redhat.com
|
||||
include/scsi/*iscsi* cleech@redhat.com
|
||||
|
||||
^[IUCV]
|
||||
include/net/iucv/ dledford@redhat.com prarit@redhat.com
|
||||
net/iucv/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[JOURNALLING LAYER FOR BLOCK DEVICES (JBD2)]
|
||||
fs/jbd2/ lczerner@redhat.com
|
||||
include/linux/jbd2.h lczerner@redhat.com
|
||||
|
|
@ -845,8 +825,11 @@ kernel/*.[ch] prarit@redhat.com
|
|||
^kernel/kexec* prarit@redhat.com
|
||||
^kernel/rcu/ prarit@redhat.com
|
||||
^kernel/trace/ prarit@redhat.com
|
||||
^kernel/time/ prarit@redhat.com
|
||||
^kernel/power/ prarit@redhat.com
|
||||
|
||||
^[KERNEL VIRTUAL MACHINE (KVM)]
|
||||
drivers/virt/tdx/ pbonzini@redhat.com bsd@redhat.com vkuznets@redhat.com
|
||||
Documentation/virt/kvm/ pbonzini@redhat.com bsd@redhat.com vkuznets@redhat.com
|
||||
include/trace/events/kvm.h pbonzini@redhat.com bsd@redhat.com vkuznets@redhat.com
|
||||
include/uapi/asm-generic/kvm* pbonzini@redhat.com bsd@redhat.com vkuznets@redhat.com
|
||||
|
|
@ -928,6 +911,7 @@ arch/x86/include/asm/livepatch.h jpoimboe@redhat.com joe.lawrence@redhat.com asa
|
|||
arch/x86/kernel/livepatch.c jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
include/linux/livepatch.h jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
kernel/livepatch/ jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
kernel/module/livepatch.c jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
lib/livepatch/ jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
samples/livepatch/ jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
tools/objtool/ jpoimboe@redhat.com joe.lawrence@redhat.com asavkov@redhat.com ycote@redhat.com
|
||||
|
|
@ -964,7 +948,7 @@ drivers/scsi/mpt3sas/ thenzl@redhat.com
|
|||
arch/x86/kernel/cpu/mcheck/ prarit@redhat.com
|
||||
|
||||
^[MAILBOX DRIVERS]
|
||||
drivers/mailbox/ ahs3@redhat.com
|
||||
drivers/mailbox/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
|
||||
^[MEDIA INPUT INFRASTRUCTURE (V4L/DVB)]
|
||||
drivers/media/ dnelson@redhat.com
|
||||
|
|
@ -1019,10 +1003,6 @@ mm/ aquini@redhat.com
|
|||
^[MFD DRIVERS (Multi Function Devices)]
|
||||
drivers/mfd/ msalter@redhat.com prarit@redhat.com
|
||||
|
||||
^[MICRON PCIe SSD DRIVER (mtip32xx)]
|
||||
drivers/block/mtip32xx/mtip32xx.c gtiwari@redhat.com
|
||||
drivers/block/mtip32xx/mtip32xx.h gtiwari@redhat.com
|
||||
|
||||
^[MICROSEMI SMART ARRAY SMARTPQI DRIVER (smartpqi)]
|
||||
drivers/scsi/smartpqi/smartpqi*.[ch] dbrace@redhat.com thenzl@redhat.com
|
||||
drivers/scsi/smartpqi/Kconfig dbrace@redhat.com thenzl@redhat.com
|
||||
|
|
@ -1049,26 +1029,26 @@ include/linux/mlx5/ atzin@redhat.com mkabat@redhat.com kheib@redhat.com
|
|||
include/uapi/rdma/mlx5-abi.h atzin@redhat.com mkabat@redhat.com kheib@redhat.com
|
||||
|
||||
^[MMC LAYER]
|
||||
Documentation/mmc/ gtiwari@redhat.com
|
||||
include/linux/mmc/ gtiwari@redhat.com
|
||||
drivers/mmc/ gtiwari@redhat.com
|
||||
Documentation/mmc/ msalter@redhat.com
|
||||
include/linux/mmc/ msalter@redhat.com
|
||||
drivers/mmc/ msalter@redhat.com
|
||||
|
||||
^[MYRICOM MYRI-10G 10GbE DRIVER (MYRI10GE)]
|
||||
drivers/net/ethernet/myricom/myri10ge/ jarod@redhat.com
|
||||
|
||||
[NAMESPACES]
|
||||
Documentation/admin-guide/namespaces/ ebiederm@redhat.com agladkov@redhat.com
|
||||
fs/proc/namespaces.c ebiederm@redhat.com agladkov@redhat.com
|
||||
include/linux/mnt_namespace.h ebiederm@redhat.com agladkov@redhat.com
|
||||
include/linux/pid_namespace.h ebiederm@redhat.com agladkov@redhat.com
|
||||
include/linux/time_namespace.h ebiederm@redhat.com agladkov@redhat.com
|
||||
include/linux/user_namespace.h ebiederm@redhat.com agladkov@redhat.com
|
||||
kernel/nsproxy.c ebiederm@redhat.com agladkov@redhat.com
|
||||
kernel/time/namespace.c ebiederm@redhat.com agladkov@redhat.com
|
||||
kernel/ucounts.c ebiederm@redhat.com agladkov@redhat.com
|
||||
kernel/user_namespace.c ebiederm@redhat.com agladkov@redhat.com
|
||||
tools/testing/selftests/pid_namespace/ ebiederm@redhat.com agladkov@redhat.com
|
||||
tools/testing/selftests/rlimits/ ebiederm@redhat.com agladkov@redhat.com
|
||||
Documentation/admin-guide/namespaces/ agladkov@redhat.com
|
||||
fs/proc/namespaces.c agladkov@redhat.com
|
||||
include/linux/mnt_namespace.h agladkov@redhat.com
|
||||
include/linux/pid_namespace.h agladkov@redhat.com
|
||||
include/linux/time_namespace.h agladkov@redhat.com
|
||||
include/linux/user_namespace.h agladkov@redhat.com
|
||||
kernel/nsproxy.c agladkov@redhat.com
|
||||
kernel/time/namespace.c agladkov@redhat.com
|
||||
kernel/ucounts.c agladkov@redhat.com
|
||||
kernel/user_namespace.c agladkov@redhat.com
|
||||
tools/testing/selftests/pid_namespace/ agladkov@redhat.com
|
||||
tools/testing/selftests/rlimits/ agladkov@redhat.com
|
||||
|
||||
^[NETFILTER]
|
||||
net/netfilter/ fwestpha@redhat.com
|
||||
|
|
@ -1097,7 +1077,9 @@ net/dsa/ ivecera@redhat.com
|
|||
net/ jbenc@redhat.com mleitner@redhat.com
|
||||
Documentation/admin-guide/sysctl/net.rst jbenc@redhat.com mleitner@redhat.com
|
||||
Documentation/networking/ jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/Kconfig jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/Space.c jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/appletalk/ jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/bareudp.c jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/dummy.c jbenc@redhat.com mleitner@redhat.com
|
||||
drivers/net/geneve.c jbenc@redhat.com mleitner@redhat.com
|
||||
|
|
@ -1175,6 +1157,7 @@ tools/testing/selftests/wireguard/ jbenc@redhat.com mleitner@redhat.com
|
|||
^Documentation/networking/rds* jbenc@redhat.com mleitner@redhat.com
|
||||
^Documentation/networking/regulatory* jbenc@redhat.com mleitner@redhat.com
|
||||
^Documentation/networking/rxrpc* jbenc@redhat.com mleitner@redhat.com
|
||||
^include/linux/net/intel/ jbenc@redhat.com mleitner@redhat.com
|
||||
^include/linux/netfs.h jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/*80211* jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/*80215* jbenc@redhat.com mleitner@redhat.com
|
||||
|
|
@ -1182,7 +1165,6 @@ tools/testing/selftests/wireguard/ jbenc@redhat.com mleitner@redhat.com
|
|||
^include/net/bluetooth/ jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/calipso.h jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/cipso_ipv4.h jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/intel/ jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/irda/ jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/iucv/ jbenc@redhat.com mleitner@redhat.com
|
||||
^include/net/iw* jbenc@redhat.com mleitner@redhat.com
|
||||
|
|
@ -1212,7 +1194,6 @@ tools/testing/selftests/wireguard/ jbenc@redhat.com mleitner@redhat.com
|
|||
^net/vmw_vsock/ jbenc@redhat.com mleitner@redhat.com
|
||||
^net/wimax/ jbenc@redhat.com mleitner@redhat.com
|
||||
^net/wireless/ jbenc@redhat.com mleitner@redhat.com
|
||||
^net/x25/ jbenc@redhat.com mleitner@redhat.com
|
||||
|
||||
^[NETWORKING [LABELED] (NetLabel, Labeled IPsec, SECMARK)]
|
||||
Documentation/netlabel/ omosnace@redhat.com
|
||||
|
|
@ -1248,52 +1229,6 @@ fs/nfs/ bcodding@redhat.com jlayton@redhat.com steved@redhat.com smayhew@redhat.
|
|||
^[NFS SERVER (nfsd)]
|
||||
fs/nfsd/ bcodding@redhat.com jlayton@redhat.com steved@redhat.com smayhew@redhat.com
|
||||
|
||||
^[NIC DRIVERS AND RDMA]
|
||||
drivers/net/ethernet/
|
||||
drivers/infiniband/
|
||||
include/rdma/
|
||||
include/uapi/rdma/
|
||||
include/uapi/linux/if_infiniband.h
|
||||
Documentation/infiniband/
|
||||
include/linux/mlx4/
|
||||
include/linux/mlx5/
|
||||
Documentation/networking/mac80211*
|
||||
Documentation/networking/regulatory*
|
||||
drivers/net/wireless/
|
||||
net/mac80211/
|
||||
net/wireless/
|
||||
net/rfkill/
|
||||
include/linux/*80211*
|
||||
include/net/*80211*
|
||||
include/net/iw*
|
||||
include/net/regulatory.h
|
||||
include/uapi/linux/nl80211.h
|
||||
include/uapi/linux/wireless.h
|
||||
drivers/net/bonding/
|
||||
include/linux/if_bonding.h
|
||||
Documentation/networking/phy.rst
|
||||
drivers/net/phy/
|
||||
drivers/of/of_mdio.c
|
||||
include/linux/*mdio*.h
|
||||
include/linux/phy.h
|
||||
include/linux/phy_fixed.h
|
||||
include/linux/platform_data/mdio-bcm-unimac.h
|
||||
include/linux/platform_data/mdio-gpio.h
|
||||
include/trace/events/mdio.h
|
||||
include/uapi/linux/mdio.h
|
||||
include/uapi/linux/mii.h
|
||||
include/net/intel/
|
||||
Documentation/devicetree/bindings/net/dsa/
|
||||
Documentation/networking/dsa/
|
||||
drivers/net/dsa/
|
||||
include/linux/dsa/
|
||||
include/linux/platform_data/dsa.h
|
||||
include/net/dsa.h
|
||||
net/dsa/
|
||||
Documentation/networking/ena.txt
|
||||
Documentation/networking/device_drivers/ethernet/amazon/ena.rst
|
||||
^drivers/net/ethernet/microsoft/
|
||||
|
||||
^[NITRO ENCLAVES (NE)]
|
||||
Documentation/virt/ne_overview.rst cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
drivers/virt/nitro_enclaves/ cavery@redhat.com mgamal@redhat.com vkuznets@redhat.com
|
||||
|
|
@ -1326,25 +1261,33 @@ include/linux/nd.h jmoyer@redhat.com
|
|||
include/uapi/linux/ndctl.h jmoyer@redhat.com
|
||||
|
||||
^[NVM EXPRESS DRIVER (nvme)]
|
||||
drivers/nvme/ gtiwari@redhat.com
|
||||
include/linux/nvme.h gtiwari@redhat.com
|
||||
include/linux/nvme-rdma*.h gtiwari@redhat.com
|
||||
include/uapi/linux/nvme_ioctl.h gtiwari@redhat.com
|
||||
drivers/nvme/ mlombard@redhat.com
|
||||
include/linux/nvme.h mlombard@redhat.com
|
||||
include/uapi/linux/nvme_ioctl.h mlombard@redhat.com
|
||||
|
||||
^[NVM EXPRESS DRIVER FC]
|
||||
drivers/nvme/host/fc.c emilne@redhat.com
|
||||
drivers/nvme/target/fc.c emilne@redhat.com
|
||||
include/linux/nvme-fc*.h emilne@redhat.com
|
||||
|
||||
^[NVM EXPRESS DRIVER PCI]
|
||||
drivers/nvme/host/pci.c jmeneghi@redhat.com
|
||||
drivers/nvme/target/pci.c jmeneghi@redhat.com
|
||||
|
||||
^[NVM EXPRESS DRIVER RDMA]
|
||||
drivers/nvme/host/rdma.c kheib@redhat.com
|
||||
drivers/nvme/target/rdma.c kheib@redhat.com
|
||||
include/linux/nvme-rdma*.h kheib@redhat.com
|
||||
|
||||
^[NVM EXPRESS DRIVER TCP]
|
||||
drivers/nvme/host/tcp.c cleech@redhat.com
|
||||
drivers/nvme/target/tcp.c cleech@redhat.com
|
||||
include/linux/nvme-tcp*.h cleech@redhat.com
|
||||
|
||||
^[OMNI-PATH ARCHITECTURE (opa)]
|
||||
drivers/infiniband/hw/hfi* kheib@redhat.com
|
||||
include/rdma/opa* kheib@redhat.com
|
||||
include/uapi/rdma/hfi* kheib@redhat.com
|
||||
drivers/infiniband/hw/hfi* ibakolla@redhat.com kheib@redhat.com
|
||||
include/rdma/opa* ibakolla@redhat.com kheib@redhat.com
|
||||
include/uapi/rdma/hfi* ibakolla@redhat.com kheib@redhat.com
|
||||
|
||||
^[OPEN FIRMWARE AND FLATTENED DEVICE TREE]
|
||||
drivers/of/ dledford@redhat.com prarit@redhat.com
|
||||
|
|
@ -1361,22 +1304,26 @@ fs/overlayfs/ mszeredi@redhat.com
|
|||
drivers/parport/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[PCI HOTPLUG]
|
||||
drivers/pci/hotplug/ prarit@redhat.com myron.stowe@redhat.com
|
||||
drivers/pci/hotplug/ prarit@redhat.com mstowe@redhat.com
|
||||
|
||||
^[PCI SUBSYSTEM]
|
||||
drivers/pci/ myron.stowe@redhat.com prarit@redhat.com
|
||||
include/linux/pci* myron.stowe@redhat.com prarit@redhat.com
|
||||
drivers/pci/ mstowe@redhat.com prarit@redhat.com
|
||||
include/linux/pci* mstowe@redhat.com prarit@redhat.com
|
||||
|
||||
^[PCI-E NON-TRANSPARENT BRIDGE]
|
||||
drivers/pci/ linville@redhat.com myron.stowe@redhat.com
|
||||
tools/testing/selftests/ntb linville@redhat.com myron.stowe@redhat.com
|
||||
include/linux/ntb.h linville@redhat.com myron.stowe@redhat.com
|
||||
include/linux/ntb_transport.h linville@redhat.com myron.stowe@redhat.com
|
||||
Documentation/driver-api/ntb.rst linville@redhat.com myron.stowe@redhat.com
|
||||
Documentation/PCI/endpoint/ linville@redhat.com myron.stowe@redhat.com
|
||||
drivers/ntb linville@redhat.com myron.stowe@redhat.com
|
||||
drivers/pci/endpoint/ linville@redhat.com myron.stowe@redhat.com
|
||||
drivers/net/ntb_netdev.c linville@redhat.com myron.stowe@redhat.com
|
||||
drivers/pci/ linville@redhat.com mstowe@redhat.com
|
||||
tools/testing/selftests/ntb/ linville@redhat.com mstowe@redhat.com
|
||||
include/linux/ntb.h linville@redhat.com mstowe@redhat.com
|
||||
include/linux/ntb_transport.h linville@redhat.com mstowe@redhat.com
|
||||
Documentation/driver-api/ntb.rst linville@redhat.com mstowe@redhat.com
|
||||
Documentation/PCI/endpoint/ linville@redhat.com mstowe@redhat.com
|
||||
drivers/ntb/ linville@redhat.com mstowe@redhat.com
|
||||
drivers/pci/endpoint/ linville@redhat.com mstowe@redhat.com
|
||||
drivers/net/ntb_netdev.c linville@redhat.com mstowe@redhat.com
|
||||
|
||||
^[PCS NETWORK DRIVERS]
|
||||
drivers/net/pcs/ vinschen@redhat.com
|
||||
include/linux/pcs/ vinschen@redhat.com
|
||||
|
||||
^[Pensando Ethernet IONIC Driver]
|
||||
drivers/net/ethernet/pensando/ jtoppins@redhat.com
|
||||
|
|
@ -1398,7 +1345,10 @@ drivers/pinctrl/ bmasney@redhat.com darcari@redhat.com
|
|||
include/linux/pinctrl/ bmasney@redhat.com darcari@redhat.com
|
||||
|
||||
^[PLATFORM DRIVERS]
|
||||
drivers/platform/Kconfig darcari@redhat.com mlangsdo@redhat.com
|
||||
drivers/platform/Kconfig mlangsdo@redhat.com
|
||||
drivers/platform/ mlangsdo@redhat.com
|
||||
^drivers/platform/x86/ mlangsdo@redhat.com
|
||||
^drivers/platform/mellanox/ mlangsdo@redhat.com
|
||||
|
||||
^[PLATFORM DRIVERS MELLANOX]
|
||||
drivers/platform/mellanox/ mlangsdo@redhat.com
|
||||
|
|
@ -1417,6 +1367,10 @@ drivers/firmware/psci*.c msalter@redhat.com mlangsdo@redhat.com jlinton@redhat.c
|
|||
include/linux/psci.h msalter@redhat.com mlangsdo@redhat.com jlinton@redhat.com
|
||||
include/uapi/linux/psci.h msalter@redhat.com mlangsdo@redhat.com jlinton@redhat.com
|
||||
|
||||
^[POWERCAP]
|
||||
drivers/powercap/ mlangsdo@redhat.com lszubowi@redhat.com
|
||||
^drivers/powercap/intel* mlangsdo@redhat.com lszubowi@redhat.com
|
||||
|
||||
^[POWERPC (64-BIT)]
|
||||
arch/powerpc/ sbest@redhat.com
|
||||
^arch/powerpc/net/ sbest@redhat.com
|
||||
|
|
@ -1425,8 +1379,8 @@ arch/powerpc/ sbest@redhat.com
|
|||
drivers/pps/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[PSTORE PERSISTENT STORAGE]
|
||||
Documentation/ABI/testing/pstore lszubowi@redhat.com ahs3@redhat.com
|
||||
fs/pstore/ lszubowi@redhat.com ahs3@redhat.com
|
||||
Documentation/ABI/testing/pstore lszubowi@redhat.com
|
||||
fs/pstore/ lszubowi@redhat.com
|
||||
|
||||
^[PTP HARDWARE CLOCK SUPPORT]
|
||||
Documentation/ptp/ jbenc@redhat.com prarit@redhat.com
|
||||
|
|
@ -1456,7 +1410,8 @@ drivers/net/ethernet/qlogic/qed/ mchopra@redhat.com mschmidt@redhat.com
|
|||
drivers/net/ethernet/qlogic/qede/ mchopra@redhat.com mschmidt@redhat.com
|
||||
|
||||
^[QLOGIC QEDR RDMA ETHERNET NETWORK DRIVER]
|
||||
drivers/infiniband/hw/qedr/ mchopra@redhat.com mschmidt@redhat.com
|
||||
drivers/infiniband/hw/qedr/ mchopra@redhat.com kheib@redhat.com
|
||||
include/uapi/rdma/qedr-abi.h mchopra@redhat.com kheib@redhat.com
|
||||
|
||||
^[QLOGIC QL41xxx FCOE DRIVER]
|
||||
drivers/scsi/qedf/ njavali@redhat.com aeasi@redhat.com
|
||||
|
|
@ -1508,13 +1463,20 @@ tools/testing/selftests/rtc/ longman@redhat.com prarit@redhat.com
|
|||
^[REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM]
|
||||
drivers/remoteproc/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[RFKILL]
|
||||
Documentation/rfkill.txt linville@redhat.com
|
||||
net/rfkill/ linville@redhat.com
|
||||
|
||||
^[ROCKER DRIVER]
|
||||
drivers/net/ethernet/rocker/ ivecera@redhat.com
|
||||
|
||||
^[S390 ARCHITECTURE]
|
||||
arch/s390/ sbest@redhat.com
|
||||
drivers/s390/ sbest@redhat.com
|
||||
^arch/s390/include/uapi/asm/kvm* sbest@redhat.com
|
||||
^arch/s390/include/asm/gmap.h sbest@redhat.com
|
||||
^arch/s390/include/asm/kvm* sbest@redhat.com
|
||||
^arch/s390/kvm/ sbest@redhat.com
|
||||
^arch/s390/mm/ sbest@redhat.com
|
||||
^drivers/s390/cio/vfio_ccw* sbest@redhat.com
|
||||
^drivers/s390/virtio/ sbest@redhat.com
|
||||
|
||||
^[S390 VFIO-CCW DRIVER]
|
||||
drivers/s390/cio/vfio_ccw* cohuck@redhat.com
|
||||
Documentation/s390/vfio-ccw.txt cohuck@redhat.com
|
||||
|
|
@ -1526,6 +1488,9 @@ include/linux/sched/ pauld@redhat.com
|
|||
include/linux/sched.h pauld@redhat.com
|
||||
include/uapi/linux/sched.h pauld@redhat.com
|
||||
include/linux/wait.h pauld@redhat.com
|
||||
kernel/time/tick-* pauld@redhat.com
|
||||
kernel/time/sched_clock.c pauld@redhat.com
|
||||
kernel/Kconfig.hz pauld@redhat.com
|
||||
|
||||
^[SCSI CORE SUBSYSTEM (NOT INDIVIDUAL DRIVERS)]
|
||||
drivers/scsi/ emilne@redhat.com
|
||||
|
|
@ -1588,6 +1553,9 @@ drivers/net/ethernet/marvell/skge.* mschmidt@redhat.com
|
|||
^[SKY2 10/100/1000 GIGABIT ETHERNET DRIVER]
|
||||
drivers/net/ethernet/marvell/sky2.* jlinton@redhat.com mlangsdo@redhat.com
|
||||
|
||||
^[SLIP (serial line)]
|
||||
drivers/net/slip/ mschmidt@redhat.com
|
||||
|
||||
^[SOFT-IWARP DRIVER (siw)]
|
||||
drivers/infiniband/sw/siw/ kheib@redhat.com
|
||||
include/uapi/rdma/siw-abi.h kheib@redhat.com
|
||||
|
|
@ -1610,12 +1578,16 @@ include/linux/memstick.h dledford@redhat.com prarit@redhat.com
|
|||
drivers/soundwire/ dledford@redhat.com prarit@redhat.com
|
||||
|
||||
^[SPI DRIVERS (Serial Peripheral Interface)]
|
||||
drivers/spi/ ahs3@redhat.com
|
||||
drivers/spi/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
|
||||
^[SQUASHFS FILE SYSTEM]
|
||||
Documentation/filesystems/squashfs.txt adas@redhat.com
|
||||
fs/squashfs/ adas@redhat.com
|
||||
|
||||
^[STMICRO ETHERNET DRIVER]
|
||||
drivers/net/ethernet/stmicro/ vinschen@redhat.com
|
||||
include/linux/stmmac.h vinschen@redhat.com
|
||||
|
||||
^[SUN REMOTE PROCEDURE CALL (sunrpc)]
|
||||
net/sunrpc/ bcodding@redhat.com jlayton@redhat.com steved@redhat.com smayhew@redhat.com
|
||||
|
||||
|
|
@ -1650,10 +1622,28 @@ include/linux/cpu_cooling.h darcari@redhat.com
|
|||
include/linux/thermal.h darcari@redhat.com
|
||||
|
||||
^[THUNDERBOLT SUBSYSTEM]
|
||||
drivers/net/thunderbolt.c torez@redhat.com
|
||||
drivers/thunderbolt/ torez@redhat.com
|
||||
drivers/platform/x86/intel-wmi-thunderbolt.c torez@redhat.com
|
||||
include/linux/thunderbolt.h torez@redhat.com
|
||||
drivers/net/thunderbolt.c desnesn@redhat.com
|
||||
drivers/thunderbolt/ desnesn@redhat.com
|
||||
drivers/platform/x86/intel-wmi-thunderbolt.c desnesn@redhat.com
|
||||
include/linux/thunderbolt.h desnesn@redhat.com
|
||||
|
||||
[TIME]
|
||||
kernel/time/ prarit@redhat.com
|
||||
include/linux/time32.h prarit@redhat.com
|
||||
include/linux/time64.h prarit@redhat.com
|
||||
include/linux/timecounter.h prarit@redhat.com
|
||||
include/linux/time.h prarit@redhat.com
|
||||
include/linux/timekeeper_internal.h prarit@redhat.com
|
||||
include/linux/timekeeping.h prarit@redhat.com
|
||||
include/linux/time_namespace.h prarit@redhat.com
|
||||
include/linux/timerfd.h prarit@redhat.com
|
||||
include/linux/timer.h prarit@redhat.com
|
||||
include/linux/timerqueue.h prarit@redhat.com
|
||||
include/linux/timex.h prarit@redhat.com
|
||||
include/time/hrtimer.c prarit@redhat.com
|
||||
^kernel/time/namespace.c prarit@redhat.com
|
||||
^kernel/time/tick-* prarit@redhat.com
|
||||
^kernel/time/sched_clock.c prarit@redhat.com
|
||||
|
||||
^[TIPC PROTOCOL]
|
||||
net/tipc/ jmaloy@redhat.com lxin@redhat.com
|
||||
|
|
@ -1681,14 +1671,18 @@ include/uapi/linux/serial_core.h linville@redhat.com
|
|||
include/uapi/linux/tty.h linville@redhat.com
|
||||
|
||||
^[UNIVERSAL EXTENSIBLE FIRMWARE INTERFACE (UEFI/EFI)]
|
||||
arch/x86/kernel/efi* lszubowi@redhat.com ahs3@redhat.com myron.stowe@redhat.com prarit@redhat.com
|
||||
include/linux/efi.h lszubowi@redhat.com ahs3@redhat.com myron.stowe@redhat.com prarit@redhat.com
|
||||
arch/x86/kernel/efi* lszubowi@redhat.com mstowe@redhat.com prarit@redhat.com
|
||||
include/linux/efi.h lszubowi@redhat.com mstowe@redhat.com prarit@redhat.com
|
||||
|
||||
^[USB CDC ETHERNET DRIVER]
|
||||
drivers/net/usb/cdc_ether.c jtornosm@redhat.com
|
||||
^[UNIVERSAL FLASH STORAGE HOST CONTROLLER]
|
||||
drivers/ufs/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
include/ufs/ athierry@redhat.com ahalaney@redhat.com bmasney@redhat.com echanude@redhat.com
|
||||
|
||||
^[USB network drivers]
|
||||
drivers/net/usb/ jtornosm@redhat.com
|
||||
|
||||
^[USB SUBSYSTEM]
|
||||
drivers/usb/ torez@redhat.com
|
||||
drivers/usb/ desnesn@redhat.com
|
||||
|
||||
^[USERSPACE I/O DRIVERS (UIO)]
|
||||
include/linux/uio_driver.h arozansk@redhat.com
|
||||
|
|
@ -1701,16 +1695,16 @@ drivers/uio/ arozansk@redhat.com
|
|||
usr/ prarit@redhat.com wander@redhat.com
|
||||
|
||||
^[VFIO DRIVER]
|
||||
Documentation/vfio.txt alex.williamson@redhat.com eric.auger@redhat.com
|
||||
drivers/vfio/ alex.williamson@redhat.com eric.auger@redhat.com
|
||||
include/linux/vfio.h alex.williamson@redhat.com eric.auger@redhat.com
|
||||
include/uapi/linux/vfio.h alex.williamson@redhat.com eric.auger@redhat.com
|
||||
Documentation/vfio.txt alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
drivers/vfio/ alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
include/linux/vfio.h alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
include/uapi/linux/vfio.h alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
|
||||
^[VFIO MEDIATED DEVICE DRIVERS]
|
||||
Documentation/vfio-mediated-device.txt alex.williamson@redhat.com eric.auger@redhat.com
|
||||
drivers/vfio/mdev/ alex.williamson@redhat.com eric.auger@redhat.com
|
||||
include/linux/mdev.h alex.williamson@redhat.com eric.auger@redhat.com
|
||||
samples/vfio-mdev/ alex.williamson@redhat.com eric.auger@redhat.com
|
||||
Documentation/vfio-mediated-device.txt alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
drivers/vfio/mdev/ alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
include/linux/mdev.h alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
samples/vfio-mdev/ alex.williamson@redhat.com eric.auger@redhat.com clg@redhat.com
|
||||
|
||||
^[VIRT LIB]
|
||||
virt/lib/ alex.williamson@redhat.com pbonzini@redhat.com
|
||||
|
|
@ -1764,12 +1758,15 @@ include/uapi/linux/vhost.h mst@redhat.com jasowang@redhat.com
|
|||
drivers/virtio/virtio_input.c kraxel@redhat.com
|
||||
include/uapi/linux/virtio_input.h kraxel@redhat.com
|
||||
|
||||
^[VIRTUALIZATION SUPPORT DRIVERS]
|
||||
drivers/virt/ vkuznets@redhat.com cavery@redhat.com mgamal@redhat.com
|
||||
|
||||
^[VMWARE PVRDMA DRIVER (vmw_pvrdma)]
|
||||
drivers/infiniband/hw/vmw_pvrdma/ kheib@redhat.com
|
||||
include/uapi/rdma/vmw_pvrdma-abi.h kheib@redhat.com
|
||||
|
||||
^[VMWARE VMXNET3 ETHERNET DRIVER (vmxnet3)]
|
||||
drivers/net/vmxnet3/ kheib@redhat.com
|
||||
drivers/net/vmxnet3/ ibakolla@redhat.com kheib@redhat.com
|
||||
|
||||
^[WATCHDOG]
|
||||
Documentation/watchdog/ prarit@redhat.com
|
||||
|
|
@ -1778,6 +1775,10 @@ drivers/acpi/acpi_watchdog.c prarit@redhat.com
|
|||
include/linux/watchdog.h prarit@redhat.com
|
||||
include/uapi/linux/watchdog.h prarit@redhat.com
|
||||
|
||||
^[Wide Area Networks (WAN)]
|
||||
drivers/net/wan/ mschmidt@redhat.com
|
||||
Documentation/networking/device_drivers/wan/ mschmidt@redhat.com
|
||||
|
||||
[WIRELESS DRIVERS AND STACK]
|
||||
Documentation/networking/mac80211* ihuguet@redhat.com jtornosm@redhat.com
|
||||
Documentation/networking/regulatory* ihuguet@redhat.com jtornosm@redhat.com
|
||||
|
|
@ -1794,12 +1795,18 @@ include/uapi/linux/wireless.h ihuguet@redhat.com jtornosm@redhat.com
|
|||
|
||||
^[WIRELESS [LR-WPAN] (IEEE 802.15.4)]
|
||||
Documentation/networking/ieee802154.rst crecklin@redhat.com
|
||||
drivers/net/ieee802154/fakelb.c crecklin@redhat.com
|
||||
drivers/net/ieee802154/ crecklin@redhat.com
|
||||
include/linux/*802154* crecklin@redhat.com
|
||||
include/net/*802154* crecklin@redhat.com
|
||||
net/ieee802154/ crecklin@redhat.com
|
||||
net/mac802154/ crecklin@redhat.com
|
||||
|
||||
^[WWAN (Wireless WAN)]
|
||||
drivers/net/wwan/ jtornosm@redhat.com
|
||||
include/linux/wwan.h jtornosm@redhat.com
|
||||
include/uapi/linux/wwan.h jtornosm@redhat.com
|
||||
Documentation/networking/device_drivers/wwan/ jtornosm@redhat.com
|
||||
|
||||
[X86 ARCHITECTURE]
|
||||
arch/x86/ darcari@redhat.com prarit@redhat.com dnelson@redhat.com
|
||||
tools/arch/x86/ darcari@redhat.com prarit@redhat.com dnelson@redhat.com
|
||||
|
|
@ -1832,6 +1839,7 @@ drivers/cpufreq/amd_freq_sensitivity.c prarit@redhat.com darcari@redhat.com
|
|||
drivers/cpufreq/amd-pstate.c prarit@redhat.com darcari@redhat.com
|
||||
drivers/cpufreq/amd-pstate-trace.c prarit@redhat.com darcari@redhat.com
|
||||
drivers/idle/intel_idle.c prarit@redhat.com darcari@redhat.com
|
||||
drivers/idle/Kconfig prarit@redhat.com darcari@redhat.com
|
||||
|
||||
[X86 FPU SUBSYSTEM]
|
||||
arch/x86/include/asm/fpu/ dnelson@redhat.com
|
||||
|
|
@ -1855,18 +1863,18 @@ tools/testing/selftests/bpf/*xdp* brouer@redhat.com jbenc@redhat.com toke@redhat
|
|||
tools/testing/selftests/bpf/*/*xdp* brouer@redhat.com jbenc@redhat.com toke@redhat.com
|
||||
|
||||
^[XEN]
|
||||
drivers/block/xen-blkfront.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/input/misc/xen-kbdfront.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/net/xen-netfront.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/tty/hvc/hvc_xen.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/watchdog/xen_wdt.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/xen/ vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
include/trace/events/xen.h vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
include/uapi/xen/ vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
include/xen/ vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
arch/x86/include/asm/xen/ vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
arch/x86/pci/xen.c vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
arch/x86/xen/ vkuznets@redhat.com imammedo@redhat.com drjones@redhat.com
|
||||
drivers/block/xen-blkfront.c vkuznets@redhat.com imammedo@redhat.com
|
||||
drivers/input/misc/xen-kbdfront.c vkuznets@redhat.com imammedo@redhat.com
|
||||
drivers/net/xen-netfront.c vkuznets@redhat.com imammedo@redhat.com
|
||||
drivers/tty/hvc/hvc_xen.c vkuznets@redhat.com imammedo@redhat.com
|
||||
drivers/watchdog/xen_wdt.c vkuznets@redhat.com imammedo@redhat.com
|
||||
drivers/xen/ vkuznets@redhat.com imammedo@redhat.com
|
||||
include/trace/events/xen.h vkuznets@redhat.com imammedo@redhat.com
|
||||
include/uapi/xen/ vkuznets@redhat.com imammedo@redhat.com
|
||||
include/xen/ vkuznets@redhat.com imammedo@redhat.com
|
||||
arch/x86/include/asm/xen/ vkuznets@redhat.com imammedo@redhat.com
|
||||
arch/x86/pci/xen.c vkuznets@redhat.com imammedo@redhat.com
|
||||
arch/x86/xen/ vkuznets@redhat.com imammedo@redhat.com
|
||||
|
||||
^[XFS FILESYSTEM]
|
||||
Documentation/filesystems/xfs.txt bfoster@redhat.com cmaiolino@redhat.com esandeen@redhat.com bodonnel@redhat.com dchinner@redhat.com
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -2,5 +2,6 @@ RHMAINTAINERS_parser
|
|||
yaml2RHMAINTAINERS
|
||||
yaml2CODEOWNERS
|
||||
verifySubsystems
|
||||
searchowners
|
||||
*.patch
|
||||
*.swp
|
||||
|
|
|
|||
|
|
@ -3,7 +3,8 @@ fullbuild:
|
|||
go build yaml2RHMAINTAINERS.go
|
||||
go build yaml2CODEOWNERS.go
|
||||
go build verifySubsystems.go validSSTNames.go
|
||||
go build searchowners.go
|
||||
|
||||
clean:
|
||||
rm -f RHMAINTAINERS_parser yaml2RHMAINTAINERS yaml2CODEOWNERS verifySubsystems
|
||||
rm -f RHMAINTAINERS_parser yaml2RHMAINTAINERS yaml2CODEOWNERS verifySubsystems searchowners
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,113 @@
|
|||
package main
|
||||
|
||||
// This program outputs the name, email, and GitLab username based on a search
|
||||
// query. For example,
|
||||
//
|
||||
// searchowners ../info/owners.yaml prarit
|
||||
//
|
||||
// would output
|
||||
//
|
||||
// Name: Prarit Bhargava
|
||||
// Email: prarit@redhat.com
|
||||
// GitLab User: prarit
|
||||
//
|
||||
|
||||
import (
|
||||
"fmt"
|
||||
"log"
|
||||
"regexp"
|
||||
|
||||
"gopkg.in/yaml.v2"
|
||||
"os"
|
||||
"io/ioutil"
|
||||
)
|
||||
|
||||
type NameAndEmail struct {
|
||||
Name string `name`
|
||||
Email string `email`
|
||||
GLUser string `gluser`
|
||||
Restricted bool
|
||||
}
|
||||
|
||||
type SubSystem struct {
|
||||
Subsystem string `subsystem`
|
||||
Labels struct {
|
||||
Name string `name`
|
||||
ReadyForMergeDeps []string `readyForMergeDeps`
|
||||
NewLabels string `newLabels`
|
||||
EmailLabel string `emailLabel`
|
||||
}
|
||||
Status string `status`
|
||||
Maintainers []NameAndEmail `maintainers`
|
||||
Reviewers []NameAndEmail `reviewers`
|
||||
Paths struct {
|
||||
Includes []string
|
||||
IncludeRegexes []string
|
||||
Excludes []string
|
||||
}
|
||||
Scm string `scm`
|
||||
MailingList string `mailingList`
|
||||
}
|
||||
|
||||
type SubSystems struct {
|
||||
SubSys []SubSystem `subsystems`
|
||||
}
|
||||
|
||||
var matchesNames []NameAndEmail
|
||||
|
||||
func match(matchString string, name NameAndEmail) bool {
|
||||
|
||||
// do not report the same entry twice
|
||||
for _,entry := range matchesNames {
|
||||
if entry == name {
|
||||
return true
|
||||
}
|
||||
}
|
||||
|
||||
re := regexp.MustCompile(matchString)
|
||||
m := re.FindStringSubmatch(name.Name + " " + name.Email + " " + name.GLUser)
|
||||
if len(m) > 0 {
|
||||
fmt.Println("Name:", name.Name)
|
||||
fmt.Println("Email:", name.Email)
|
||||
fmt.Println("GitLab User:", name.GLUser, "\n")
|
||||
// add the entry to the reported names so it is not reported again
|
||||
matchesNames = append(matchesNames, name)
|
||||
return true
|
||||
}
|
||||
return false
|
||||
}
|
||||
|
||||
func main() {
|
||||
|
||||
var subSystems SubSystems
|
||||
|
||||
if len(os.Args) != 3 {
|
||||
fmt.Println("Usage: searchowners <location of owners.yaml> <search string>\n")
|
||||
fmt.Println("First argument is the location of the owners.yaml file, and the second arguments is the search string.")
|
||||
fmt.Println(" ex) findowners ../info/owners.yaml prarit")
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
filename := os.Args[1]
|
||||
source, err := ioutil.ReadFile(filename)
|
||||
if err != nil {
|
||||
fmt.Printf("Unable to open %s: %s\n", filename, err)
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
|
||||
err = yaml.Unmarshal(source, &subSystems)
|
||||
if err != nil {
|
||||
log.Fatalf("error: %v", err)
|
||||
}
|
||||
|
||||
for _, entry := range subSystems.SubSys {
|
||||
for _, name := range entry.Maintainers {
|
||||
match(os.Args[2], name)
|
||||
}
|
||||
|
||||
for _, name := range entry.Reviewers {
|
||||
match(os.Args[2], name)
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
package main
|
||||
|
||||
var validSSTNames = []string {"rhel-sst-null",
|
||||
"rhel-sst-accelerators",
|
||||
"rhel-ssg-arr",
|
||||
"rhel-sst-arch-hw",
|
||||
"rhel-sst-cee-supportability",
|
||||
|
|
|
|||
Loading…
Reference in New Issue