From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tsugikazu Shibata <shibata@linuxfoundation.org>
Subject: Re: [PATCH] docs/ja_JP/SubmittingPatches: Remove reference to submitting-drivers.rst
Date: Fri, 19 Aug 2022 07:55:52 -0600 [thread overview]
Message-ID: <878rnkbamv.fsf@meer.lwn.net> (raw)
In-Reply-To: <83347b74-5075-90ad-1f8e-575bf4cdaf50@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> On Thu, 18 Aug 2022 11:02:40 -0600, Jonathan Corbet wrote:
>> Akira Yokosawa <akiyks@gmail.com> writes:
>>
>>> Reflect changes made in commit 9db370de2780 ("docs: process: remove
>>> outdated submitting-drivers.rst")
>>>
>>> Reported-by: Mauro Carvalho Chehab <mchehab@kernel.org>
>>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>>> Fixes: 9db370de2780 ("docs: process: remove outdated submitting-drivers.rst")
>>> Cc: Tsugikazu Shibata <shibata@linuxfoundation.org>
>>
>> So I can't get this patch to apply; I'm not really sure what the problem
>> is. Does it apply on your side?
>
> Looks like thunderbird used "Content-Transfer-Encoding: base64".
> Resent using "git send-email" with "Content-Transfer-Encoding: 8bit"
> Hopefully it works for you.
I'd noticed that, but "git am" can handle the decoding - it was able to
show me the patch it couldn't apply. Dunno...in any case, the new patch
applied just fine, thanks.
jon
next prev parent reply other threads:[~2022-08-19 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:12 [PATCH] docs/ja_JP/SubmittingPatches: Remove reference to submitting-drivers.rst Akira Yokosawa
2022-08-18 17:02 ` Jonathan Corbet
2022-08-18 22:42 ` Akira Yokosawa
2022-08-19 13:55 ` Jonathan Corbet [this message]
2022-08-18 22:34 ` [PATCH RESEND] " Akira Yokosawa
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=878rnkbamv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=shibata@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.