From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: lucas.demarchi@profusion.mobi, andrei.emeltchenko.news@gmail.com,
dh.herrmann@googlemail.com, gustavo@padovan.org,
linville@tuxdriver.com, linux-bluetooth@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix coding style
Date: Mon, 07 May 2012 17:41:07 -0400 (EDT) [thread overview]
Message-ID: <20120507.174107.946344637365261681.davem@davemloft.net> (raw)
In-Reply-To: <1336426419.5970.131.camel@aeonflux>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Mon, 07 May 2012 14:33:39 -0700
>> > Doing so also means we don't create our own rules and impose them on
>> > others, like happened some time ago
>> > (https://lkml.org/lkml/2012/4/16/473).
>>
>> You conveniently forgot to show that Linus said that it's OK for a
>> subsystem maintainer to request that kind of coding style, it's just
>> not OK to impose it tree-wide.
>
> may I ask some clarification on to what level of subsystem maintainers
> this applies. Is this only 1st level subsystem. Or would this extend to
> 2nd level subsystems as well?
It's a perogative of whatever the desire is of the trees your changes
percolate up into on the way to Linus.
John may want certain things to look certain ways in the wireless
code, and I may have such requirements too. Therefore a wireless
change is subjected to both John's and my tastes.
I'm really done talking about this, and I'm absolutely not working on
documentation or checkpatch.pl changes.
Instead I'm going to work on fixing bugs, reviewing patches, and
putting together -stable submissions.
next prev parent reply other threads:[~2012-05-07 21:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 18:59 [PATCH] Bluetooth: Fix coding style Gustavo Padovan
2012-05-06 16:02 ` Marcel Holtmann
2012-05-06 16:36 ` David Miller
2012-05-06 17:46 ` David Herrmann
2012-05-06 18:53 ` David Miller
2012-05-07 8:14 ` Andrei Emeltchenko
2012-05-07 8:21 ` Arend van Spriel
2012-05-07 8:29 ` Andrei Emeltchenko
2012-05-07 10:06 ` Arend van Spriel
2012-05-07 15:52 ` David Miller
2012-05-07 19:49 ` Lucas De Marchi
2012-05-07 20:06 ` David Miller
2012-05-07 20:14 ` Arend van Spriel
2012-05-07 21:33 ` Marcel Holtmann
2012-05-07 21:41 ` David Miller [this message]
2012-05-07 17:06 ` Marcel Holtmann
2012-05-07 17:55 ` David Miller
2012-05-07 21:22 ` Marcel Holtmann
2012-05-07 23:24 ` Joe Perches
2012-05-07 19:40 ` Lucas De Marchi
2012-05-07 15:24 ` Gustavo Padovan
2012-05-07 15:56 ` David Miller
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=20120507.174107.946344637365261681.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lucas.demarchi@profusion.mobi \
--cc=marcel@holtmann.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).