mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lucas Adryell Ramalho <lucasadramalho@gmail.com>
To: danielmaraboo@gmail.com, corbet@lwn.net
Cc: skhan@linuxfoundation.org, rdunlap@infradead.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lucas Adryell Ramalho <lucasadramalho@gmail.com>
Subject: [PATCH v2 0/3] docs: translations: pt_BR: Add process documentation
Date: Tue, 20 Oct 2026 01:13:35 -0300	[thread overview]
Message-ID: <20261020041340.447727-1-lucasadramalho@gmail.com> (raw)
In-Reply-To: <cover.1791933697.git.lucasadramalho@gmail.com>

Changes in v2:
- Patch 1: Use "registradores" for hardware registers in the DebugFS
  section.
- Patch 3: Use the Portuguese Sphinx labels for submitting patches and
  security bugs.

Link to v1:
https://lore.kernel.org/r/cover.1791933697.git.lucasadramalho@gmail.com/

Lucas Adryell Ramalho (3):
  docs: translations: pt_BR: process: add
    driver_development_debugging_guide
  docs: translations: pt_BR: process: Translate
    researcher-guidelines.rst
  docs: translations: pt_BR: Translate stable-kernel-rules.rst

 .../driver_development_debugging_guide.rst    | 244 +++++++++++++++++
 .../pt_BR/process/debugging/index.rst         |   6 +-
 .../translations/pt_BR/process/index.rst      |   2 +
 .../pt_BR/process/researcher-guidelines.rst   | 188 +++++++++++++
 .../pt_BR/process/stable-kernel-rules.rst     | 258 ++++++++++++++++++
 5 files changed, 697 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/translations/pt_BR/process/debugging/driver_development_debugging_guide.rst
 create mode 100644 Documentation/translations/pt_BR/process/researcher-guidelines.rst
 create mode 100644 Documentation/translations/pt_BR/process/stable-kernel-rules.rst

Range-diff against v1:
1:  3f9bdd755 ! 1:  498f9fa62 docs: translations: pt_BR: process: add driver_development_debugging_guide
    @@ Metadata
      ## Commit message ##
         docs: translations: pt_BR: process: add driver_development_debugging_guide
     
    -    Translate driver_development_debugging_guide and add to debugging/index.rst.
    +    Translate the driver debugging guide and update debugging/index.rst.
     
         Signed-off-by: Lucas Adryell Ramalho <lucasadramalho@gmail.com>
     
    @@ Documentation/translations/pt_BR/process/debugging/driver_development_debugging_
     +no log do kernel nem adiciona rastros ao código. Em vez disso, permite que o
     +desenvolvedor gerencie um conjunto de arquivos.
     +Com esses arquivos, é possível armazenar valores de variáveis ou gerar
    -+dumps de registros/memória, ou ainda tornar esses arquivos graváveis e modificar
    ++dumps de registradores/memória, ou ainda tornar esses arquivos graváveis e modificar
     +valores/configurações no driver.
     +
     +Possíveis casos de uso, entre outros:
     +
    -+- Armazenar valores de registros
    ++- Armazenar valores de registradores
     +- Acompanhar variáveis
     +- Armazenar erros
     +- Armazenar configurações
2:  d262b5c50 = 2:  588e080a3 docs: translations: pt_BR: process: Translate researcher-guidelines.rst
3:  ee88fc5b7 ! 3:  314ef8529 docs: translations: pt_BR: Translate stable-kernel-rules.rst
    @@ Documentation/translations/pt_BR/process/stable-kernel-rules.rst (new)
     +- Não pode ter mais de 100 linhas, incluindo o contexto.
     +- Deve seguir as regras de
     +  :ref:`Documentation/translations/pt_BR/process/submitting-patches.rst
    -+  <submittingpatches>`.
    ++  <pt_BR_submittingpatches>`.
     +- Deve corrigir um erro real que afete as pessoas ou apenas adicionar um ID
     +  de dispositivo. Em mais detalhes, o primeiro caso inclui:
     +
    @@ Documentation/translations/pt_BR/process/stable-kernel-rules.rst (new)
     +   Correções de segurança não devem ser tratadas exclusivamente pelo
     +   processo de revisão -stable; devem seguir os procedimentos em
     +   :ref:`Documentation/translations/pt_BR/process/security-bugs.rst
    -+   <securitybugs>`.
    ++   <pt_BR_securitybugs>`.
     +
     +Há três opções para enviar uma alteração às árvores -stable:
     +
-- 
2.55.0


  parent reply	other threads:[~2026-10-20  4:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 23:45 [PATCH v1 " Lucas Adryell Ramalho
2026-10-13 23:45 ` [PATCH v1 1/3] docs: translations: pt_BR: process: add driver_development_debugging_guide Lucas Adryell Ramalho
2026-10-14 17:02   ` Daniel Pereira
2026-10-13 23:45 ` [PATCH v1 2/3] docs: translations: pt_BR: process: Translate researcher-guidelines.rst Lucas Adryell Ramalho
2026-10-13 23:45 ` [PATCH v1 3/3] docs: translations: pt_BR: Translate stable-kernel-rules.rst Lucas Adryell Ramalho
2026-10-14 17:16   ` Daniel Pereira
2026-10-20  4:13 ` Lucas Adryell Ramalho [this message]
2026-10-20  4:13   ` [PATCH v2 1/3] docs: translations: pt_BR: process: add driver_development_debugging_guide Lucas Adryell Ramalho
2026-10-20  4:13   ` [PATCH v2 2/3] docs: translations: pt_BR: process: Translate researcher-guidelines.rst Lucas Adryell Ramalho
2026-10-20  4:13   ` [PATCH v2 3/3] docs: translations: pt_BR: Translate stable-kernel-rules.rst Lucas Adryell Ramalho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261020041340.447727-1-lucasadramalho@gmail.com \
    --to=lucasadramalho@gmail.com \
    --cc=corbet@lwn.net \
    --cc=danielmaraboo@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®