From: Jason Gunthorpe <jgg@mellanox.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH RESEND] clang-format: Set IndentWrappedFunctionNames false
Date: Tue, 26 Jun 2018 13:33:25 -0600 [thread overview]
Message-ID: <20180626193325.GA5356@mellanox.com> (raw)
In-Reply-To: <CANiq72mcwTkmEo+CnJ2P33TrTHgXaJEpjuxQjwGx5RTXjDyvhA@mail.gmail.com>
On Tue, Jun 26, 2018 at 05:05:40PM +0200, Miguel Ojeda wrote:
> Hi,
>
> On Tue, Jun 26, 2018 at 12:44 AM, Jason Gunthorpe <jgg@mellanox.com> wrote:
> > The true option causes this indenting for functions:
> >
> > static struct something_very_very_long *
> > function(void *arg)
> > {
> >
> > While a quick survey suggests that the usual Linux fallback is the GNU
> > style:
> >
> > static struct something_very_very_long *
> > function(void *arg)
> > {
> >
> > Eg as seen in:
> >
> > kernel/cpu.c
> > kernel/fork.c
> > etc
> >
> > Acked-by: Joe Perches <joe@perches.com>
> > Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
> > .clang-format | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Resending outside the merge window with no change..
> >
> > If there is no clear upstream path for this file (it has no
> > MAINTAINERS entry?) I could take it to Linus via the rdma.git tree, eg
>
> We can add an specific entry, yeah. Is there any policy for "general
> files" (or some general/catch-all entry)?
>
> > as a 'collectively maintained' file.
>
> As you prefer -- I can also pick it up through auxdisplay; but I am
> not sure if we should put it in any "unrelated" tree, though. (Since
> the file will not probably receive many patches, I originally thought
> that it would be picked up by Andrew or some other "general" tree
> instead.)
Well, I'd rather you take it as the owner of the file, honestly :)
Along with a MAINTAINERS update...
I also don't know too well what the policy is for these sorts of files
- other catch all files like kernel.h I run through rdma.git from time
to time, but that is in relation to patches that depend on them..
> > Would prefer Miguel's Ack to do that though. Looks like Andrew Morton
> > took the original patch introducing the file?
>
> Yep, I sent it to Andrew and he kindly picked it up. Probably he
> didn't notice this one.
>
> As for the patch:
>
> Acked-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Lets give Andrew some time, he is probably very busy. If it gets to
rc5 without it getting picked up one of us can grab it instead to help
out..
Thanks,
Jason
next prev parent reply other threads:[~2018-06-26 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 22:44 Jason Gunthorpe
2018-06-26 15:05 ` Miguel Ojeda
2018-06-26 19:33 ` Jason Gunthorpe [this message]
2018-06-27 14:07 ` Miguel Ojeda
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=20180626193325.GA5356@mellanox.com \
--to=jgg@mellanox.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rdunlap@infradead.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®