mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Joe Perches <joe@perches.com>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Kalle Valo <kvalo@codeaurora.org>
Cc: Daniel Drake <dsd@gentoo.org>,
	Ulrich Kunitz <kune@deine-taler.de>,
	"David S. Miller" <davem@davemloft.net>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] zd1211rw/zd_usb.h: Replace zero-length array with flexible-array member
Date: Tue, 10 Mar 2020 18:33:13 -0400	[thread overview]
Message-ID: <e65fd08d-984f-0bdc-5fbf-6abceacf819a@gmail.com> (raw)
In-Reply-To: <8b6213e51131deacbdac29a8d9c088ae49933724.camel@perches.com>

On 3/10/20 6:28 PM, Joe Perches wrote:
> On Tue, 2020-03-10 at 17:21 -0500, Gustavo A. R. Silva wrote:
>> On 3/10/20 5:15 PM, Joe Perches wrote:
>>> As far as I can tell, it doesn't actually make a difference as
>>> all the compilers produce the same object code with either form.
>>>
>>
>> That's precisely why we can implement these changes, cleanly(the fact
>> that the compiler produces the same object code). So, the resulting
>> object code is not the point here.
> 
> You are making Jes' point.
> 
> There's nothing wrong with making changes just for consistent
> style across the kernel.
> 
> This change is exactly that.
> 
> I have no objection to this patch.
> 
> Jes does, though Jes is not a maintainer of this file.

I responded to this thread because my previous comments to files I
maintain were ignored.

This is a bulk change across the tree, so it affects a lot of places.

> I think "churn" arguments are overstated.

Again, the changes are not harmful to the code, but add no value. So far
I haven't seen any good arguments for making these changes, and having
this kind of churn is a nuisance for anyone hitting patch conflicts due
to them.

Jes

  reply	other threads:[~2020-03-10 22:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 11:12 Gustavo A. R. Silva
2020-03-05 14:50 ` Kalle Valo
2020-03-05 15:20   ` Joe Perches
2020-03-05 16:10     ` Kalle Valo
2020-03-05 18:28       ` Gustavo A. R. Silva
2020-03-10 13:56         ` Kalle Valo
2020-03-10 21:52           ` Gustavo A. R. Silva
2020-03-10 22:07             ` Jes Sorensen
2020-03-10 22:13               ` Gustavo A. R. Silva
2020-03-10 22:15                 ` Joe Perches
2020-03-10 22:21                   ` Gustavo A. R. Silva
2020-03-10 22:28                     ` Joe Perches
2020-03-10 22:33                       ` Jes Sorensen [this message]
2020-03-10 22:41                         ` Joe Perches
2020-03-10 22:46                           ` Gustavo A. R. Silva
2020-03-10 22:33                       ` Gustavo A. R. Silva
2020-03-10 22:20                 ` Jes Sorensen
2020-03-10 22:31                   ` Gustavo A. R. Silva
2020-03-10 22:34                     ` Jes Sorensen
2020-03-10 22:36                       ` Gustavo A. R. Silva
2020-03-23 16:46                         ` Kalle Valo
2020-03-23 17:14 ` [PATCH][next] zd1211rw: " Kalle Valo

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=e65fd08d-984f-0bdc-5fbf-6abceacf819a@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=gustavo@embeddedor.com \
    --cc=joe@perches.com \
    --cc=kune@deine-taler.de \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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

Powered by JetHome