docs: add mailing list destination to send-patches page

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !

[Copilot]

The send-patches how-to never told readers where to send patches — no mailing list address, no subscription link.

Changes

• Mailing list destination — opening paragraph now states patches go to kernel-team@lists.ubuntu.com with a link to the list info/subscription page, and notes that non-subscriber messages are held for moderation
• --to in identity config — adds git config set sendemail.ubuntu-kernel.to kernel-team@lists.ubuntu.com to the reusable identity block so the address is configured once
• Heading fix — "mailing-list" → "mailing list" for consistency with body text

---

• Added or updated meta description (if this PR includes documentation changes)
• Reviewed all GitHub Actions / CI results; any unresolved failures are explained in a comment

• Fixespatch submission page does not mention where to send to #124

[anthonywong]

Changes are accurate and correct.

[Copilot]

Pull request overview

This PR updates the kernel docs “send patches” how-to to explicitly tell contributors where to send patches (the Ubuntu Kernel Team mailing list) and how to configure that destination in git send-email, addressing the gap reported in issue #124.

Changes:

• Adds an opening paragraph stating patches must be sent to kernel-team@lists.ubuntu.com, with a subscription/info link and moderation note for non-subscribers.
• Extends the reusable git send-email identity snippet to set sendemail.ubuntu-kernel.to once via git config.
• Normalizes the main heading from “mailing-list” to “mailing list”.

Suppressed comments (1)

docs/how-to/source-code/send-patches.rst:78

• There appears to be trailing whitespace on the blank line after the new hyperlink target at the end of the file. Trailing whitespace can cause lint/spelling checks to fail.

.. _Ubuntu kernel-team mailing list: https://lists.ubuntu.com/mailman/listinfo/kernel-team

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[AnneCYH]

Thanks for adding the actual mailing list @anthonywong !