From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
Jiri Kosina <trivial@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
v9fs-developer@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [RESEND TRIVIAL] fs: Fix Kconfig indentation
Date: Fri, 4 Oct 2019 17:19:09 +0200 [thread overview]
Message-ID: <CAJKOXPdn4j2vNcsBZOOZeO3_c4f--eJvoUzsf_1nY7LK4-uubA@mail.gmail.com> (raw)
In-Reply-To: <20191004151448.GA19056@nautica>
On Fri, 4 Oct 2019 at 17:17, Dominique Martinet <asmadeus@codewreck.org> wrote:
>
> Krzysztof Kozlowski wrote on Fri, Oct 04, 2019:
> > Adjust indentation from spaces to tab (+optional two spaces) as in
> > coding style with command like:
> > $ sed -e 's/^ /\t/' -i */Kconfig
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Send this to kernel-janitors@vger.kernel.org ?
>
> I can't pick this up as a 9p maintainer and most probably everyone else
> in copy feel similar, this is stuff where they might be able to handle
> this smoothly.
>
> (I have no problem with the 9p part of the patch, so add my ack or
> whatever if you feel that is useful, but it's honestly trivial as you
> wrote yourself)
Thanks, indeed I forgot about kernel-janitors. I sent it only to Jiri
Kosina who is mentioned as handler of trivial patches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2019-10-04 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 14:50 [RESEND TRIVIAL] fs: Fix Kconfig indentation Krzysztof Kozlowski
2019-10-04 15:14 ` Dominique Martinet
2019-10-04 15:19 ` Krzysztof Kozlowski [this message]
2019-10-21 17:29 [RESEND trivial] " Krzysztof Kozlowski
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=CAJKOXPdn4j2vNcsBZOOZeO3_c4f--eJvoUzsf_1nY7LK4-uubA@mail.gmail.com \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=miklos@szeredi.hu \
--cc=tglx@linutronix.de \
--cc=trivial@kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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).