From: Amy Parker <enbyamy@gmail.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] fs/efs: Use correct brace styling for statements
Date: Thu, 4 Feb 2021 21:12:14 -0800 [thread overview]
Message-ID: <CAE1WUT4cFXq3VMPKVt7LZ+fPeZDKQCdCN5EFG+cwNm0WhweVRQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR04MB49723F2FCDD6E7D11489CD0186B29@DM6PR04MB4972.namprd04.prod.outlook.com>
On Thu, Feb 4, 2021 at 9:09 PM Chaitanya Kulkarni
<Chaitanya.Kulkarni@wdc.com> wrote:
>
> On 2/4/21 21:01, Amy Parker wrote:
> >> Commit message is too long. Follow the style present in the tree.
> > Are you referring to the per-line length? That was supposed to have
> > been broken up, my apologies. Or is it the overall length that is the
> > issue?
> >
> > -Amy IP
> >
> Per line length. I think it should be < 73.
Alright. Working on it, expect the v2 patchset soon - sorry about that!
-Amy IP
next prev parent reply other threads:[~2021-02-05 5:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 4:52 [PATCH 0/3] fs/efs: Follow kernel style guide Amy Parker
2021-02-05 4:52 ` [PATCH 1/3] fs/efs: Use correct brace styling for statements Amy Parker
2021-02-05 4:57 ` Chaitanya Kulkarni
2021-02-05 5:00 ` Amy Parker
2021-02-05 5:09 ` Chaitanya Kulkarni
2021-02-05 5:12 ` Amy Parker [this message]
2021-02-05 4:52 ` [PATCH 2/3] fs/efs: Correct spacing after C keywords Amy Parker
2021-02-05 4:52 ` [PATCH 3/3] fs/efs: Fix line breakage for " Amy Parker
2021-02-05 13:19 ` [PATCH 0/3] fs/efs: Follow kernel style guide David Sterba
2021-02-05 15:36 ` Amy Parker
2021-02-05 22:37 ` Richard Weinberger
2021-02-05 22:49 ` Amy Parker
2021-02-08 0:15 ` David Sterba
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=CAE1WUT4cFXq3VMPKVt7LZ+fPeZDKQCdCN5EFG+cwNm0WhweVRQ@mail.gmail.com \
--to=enbyamy@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.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;
as well as URLs for NNTP newsgroup(s).