linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH v2] docs/sp_SP: Add memory-barriers.txt Spanish translation
Date: Sat, 3 Dec 2022 17:11:33 -0600	[thread overview]
Message-ID: <a3ea1633-98bd-0748-e5a0-774dfe8875d9@amd.com> (raw)
In-Reply-To: <878rjoohy2.fsf@meer.lwn.net>

On 12/3/22 5:16 AM, Jonathan Corbet wrote:
> Carlos Bilbao <carlos.bilbao@amd.com> writes:
> 
>> Translate the following documents into Spanish:
>>
>> - memory-barriers.txt
>>
>> using the wrapper documents system.
>>
>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
>> ---
>>  Documentation/translations/sp_SP/index.rst    |    1 +
>>  .../translations/sp_SP/memory-barriers.txt    | 3134 +++++++++++++++++
>>  .../sp_SP/wrappers/memory-barriers.rst        |   19 +
>>  3 files changed, 3154 insertions(+)
>>  create mode 100644 Documentation/translations/sp_SP/memory-barriers.txt
>>  create mode 100644 Documentation/translations/sp_SP/wrappers/memory-barriers.rst
> 
> I've applied this, thanks.
> 
> For future reference, it would make life just a little easier if you'd
> put patches inline rather than as attachments.

That's weird, I just used git send-email. Maybe it showed up as an
attachment due to its large size.

> 
> Thanks,
> 
> jon

Thanks,
Carlos

      reply	other threads:[~2022-12-03 23:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 17:47 [PATCH] docs/sp_SP: Add memory-barriers.txt Spanish translation Carlos Bilbao
2022-11-21 21:10 ` Jonathan Corbet
2022-11-28 14:53   ` Carlos Bilbao
2022-11-28 15:23     ` [PATCH v2] " Carlos Bilbao
2022-12-03 11:16       ` Jonathan Corbet
2022-12-03 23:11         ` Carlos Bilbao [this message]

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=a3ea1633-98bd-0748-e5a0-774dfe8875d9@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).