From: Randy Dunlap <rdunlap@infradead.org>
To: Amy Parker <enbyamy@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] fs/efs/inode.c: follow style guide
Date: Tue, 26 Jan 2021 22:35:17 -0800 [thread overview]
Message-ID: <7b8f67a6-0f06-6bf6-2ecd-5a57693a64f8@infradead.org> (raw)
In-Reply-To: <CAE1WUT4qQ2=Qkz1xsTYCvxdr5NJp8wMKhV_AiXKdq_kwWw1mfg@mail.gmail.com>
On 1/26/21 9:13 PM, Amy Parker wrote:
> On Tue, Jan 26, 2021 at 7:59 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 1/26/21 7:46 PM, Randy Dunlap wrote:
>>> Hi Amy,
>>>
>>> What mail client did you use?
>>> It is breaking (splitting) long lines into shorter lines and that
>>> makes it not possible to apply the patch cleanly.
>
> Was worried about that, thought I had all my settings straightened out.
>
>>>
>>> You can see this problem below or on the web in an email archive.
>>>
>>> Possibly Documentation/process/email-clients.rst can help you.
>
> Yeah, read that. Thought I had everything fixed up.
>
>>
>> Also tabs in the source file have been converted to spaces.
>
> Was this inconsistent throughout the patch? I can't really seem to
> tell. If it's consistent, bet it's probably my mail client - if it's
> inconsistent it could be my editor, I had to switch out temporarily
> for a different editor today.
>
There are no tabs in the patch.
>>
>> It would be good if you could email a patch to yourself and then
>> see if you can apply cleanly it to your source tree (after removing
>> any conflicting patches, of course -- or use a different source
>> tree).
>
> Yeah, I'll make sure to double check with that in the future.
>
>>
>>
>> --
>> ~Randy
>> Reported-by: Randy Dunlap <rdunlap@infradead.org>
>> netiquette: https://people.kernel.org/tglx/notes-about-netiquette
>
> Should I send in a v2 of this patchset, or just attach the patch here?
> If I should just attach it here, then I'll do the same for patch 2/2.
An attachment might be OK once but it would be better if you
could get inline patches to work. You'll need to do that...
--
~Randy
next prev parent reply other threads:[~2021-01-27 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 20:58 Amy Parker
2021-01-27 3:46 ` Randy Dunlap
2021-01-27 3:59 ` Randy Dunlap
2021-01-27 5:13 ` Amy Parker
2021-01-27 6:35 ` Randy Dunlap [this message]
2021-01-27 17:08 ` Kari Argillander
2021-01-27 17:25 ` Amy Parker
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=7b8f67a6-0f06-6bf6-2ecd-5a57693a64f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=enbyamy@gmail.com \
--cc=linux-fsdevel@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
all inboxes | Powered by JetHome®