linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] .clang-format: update column limit
Date: Wed, 10 Jun 2020 08:58:36 -0700	[thread overview]
Message-ID: <20200610155836.GA2360592@ubuntu-n2-xlarge-x86> (raw)
In-Reply-To: <CANiq72m_p2BRXswCGhUZi-Nta2y0uNXDQLRjPUFydB7YGV-6HQ@mail.gmail.com>

On Wed, Jun 10, 2020 at 05:55:14PM +0200, Miguel Ojeda wrote:
> Hi Christian,
> 
> On Wed, Jun 10, 2020 at 2:51 PM Christian Brauner
> <christian.brauner@ubuntu.com> wrote:
> >
> > The provided clang-format file wraps at 80 chars. If no one minds, I'd like
> > to adjust this limit to 100 similar to what checkpatch (cf. [1]) uses now.
> 
> Thanks! Picking this up with a few changes to the commit message.
> 
> Cheers,
> Miguel
> 

If it isn't too late:

Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>

  reply	other threads:[~2020-06-10 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 12:51 [PATCH] .clang-format: update column limit Christian Brauner
2020-06-10 15:55 ` Miguel Ojeda
2020-06-10 15:58   ` Nathan Chancellor [this message]
2020-06-10 16:23     ` Sedat Dilek
2020-06-10 17:13 ` Joe Perches
2020-06-10 17:32   ` Christian Brauner
2020-06-11 10:03   ` Miguel Ojeda
2020-06-11 10:36     ` Joe Perches
2020-06-11 11:54       ` Miguel Ojeda
2020-06-11 16:22         ` Joe Perches
2020-06-11 18:51           ` Miguel Ojeda
2020-06-11 19:26             ` Joe Perches
2020-06-22  0:03               ` Miguel Ojeda
2023-12-18 10:18                 ` Alexander Potapenko

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=20200610155836.GA2360592@ubuntu-n2-xlarge-x86 \
    --to=natechancellor@gmail.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    /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).