All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
	Grant Likely <Grant.Likely@arm.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Satoru OKAMOTO <okamoto.satoru@socionext.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Yang Zhang <yang.zhang@96boards.org>
Subject: Re: [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue
Date: Mon, 6 Nov 2017 11:28:05 +0000	[thread overview]
Message-ID: <CAKv+Gu_Wkdd3EdOjKJYZN5Ypjodpu5kFU=Ubg9H5e6ER3zq8Mg@mail.gmail.com> (raw)
In-Reply-To: <c3c5b129-cd30-335d-80fd-05e9e4756121@suse.de>

On 6 November 2017 at 06:58, Andreas Färber <afaerber@suse.de> wrote:
> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
[...]
>>
>> Again, I am not the one who is ranting here. You hit a nerve by
>> accusing me of 'rebelling against linux.git' while this is quite the
>> opposite of what I am doing.
>
> Actually you did confirm that point by starting an argument about not
> needing a central repository and you not liking Linux as the location.
> That was exactly what I meant with my original comment.
>
> Adding Actions Semi was somewhat easy as a new vendor and now - roughly
> a year after the board went to market - there's Linaro contributions
> from Mani that I'm thankful for.
>
> Whereas patches keep falling into a dark hole when there's already other
> work for a certain vendor, such as Marvell and now Socionext, with no
> one feeling responsible for either taking them or saying, "hey, we're
> not going to submit any conflicting DT bindings for SynQuacer because we
> use ACPI, so please go ahead with proposal X, thanks for your efforts".
>
> Don't complain about me ranting if you belittle my volunteer work that I
> believe Linaro and its partners should've done in the first place: If I
> can get an initial mainline PoC done as an individual on a few
> evenings/weekends, then the same should be super-easy for an
> organization with lots of engineers and paying member companies.

The only person doing the ranting, rebelling and belittling in this
thread is you. I have never commented on the nature of your work, let
alone belittle it.

I understand you are frustrated with how some of the upstreaming of
96boards is handled. I don't have anything to do with that. The only
96boards i have in my drawer (and never use) is an original HiKey.

I work for the enterprise group, not the 96boards team, and I make a
point of not working with vendor trees at all. The only reason I
submitted some patches to the upcoming release of the ERP is so that
we have an installer that works out of the box, but all the patches I
did contribute were already queued for v4.15 at that point.

> As I've pointed out, an ever-increasing frustration builds over Linaro
> continuing to announce new boards (such as SynQuacer) that will be the
> best since sliced bread, while neglecting the 96boards that are already
> on the market and equally are promoted under the "96Boards" brand.
> The Linaro CEO has been promoting the Orange Pi i96 in keynotes, so
> management is aware of that hardware, and yet not a single patch came
> from Xunlong, RDA Micro or Linaro. No patch review from RDA either. And
> my patches got stuck on the bindings not including interrupts property
> for the UART yet, since I still do not have their custom interrupt
> controller working... So the context here is that not just my 4.14+
> pulls got stuck but three other 96Boards patch series, too.
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg)

WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh@kernel.org>,
	Satoru OKAMOTO <okamoto.satoru@socionext.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Yang Zhang <yang.zhang@96boards.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Grant Likely <Grant.Likely@arm.com>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	Olof Johansson <olof@lixom.net>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue
Date: Mon, 6 Nov 2017 11:28:05 +0000	[thread overview]
Message-ID: <CAKv+Gu_Wkdd3EdOjKJYZN5Ypjodpu5kFU=Ubg9H5e6ER3zq8Mg@mail.gmail.com> (raw)
In-Reply-To: <c3c5b129-cd30-335d-80fd-05e9e4756121@suse.de>

On 6 November 2017 at 06:58, Andreas Färber <afaerber@suse.de> wrote:
> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
[...]
>>
>> Again, I am not the one who is ranting here. You hit a nerve by
>> accusing me of 'rebelling against linux.git' while this is quite the
>> opposite of what I am doing.
>
> Actually you did confirm that point by starting an argument about not
> needing a central repository and you not liking Linux as the location.
> That was exactly what I meant with my original comment.
>
> Adding Actions Semi was somewhat easy as a new vendor and now - roughly
> a year after the board went to market - there's Linaro contributions
> from Mani that I'm thankful for.
>
> Whereas patches keep falling into a dark hole when there's already other
> work for a certain vendor, such as Marvell and now Socionext, with no
> one feeling responsible for either taking them or saying, "hey, we're
> not going to submit any conflicting DT bindings for SynQuacer because we
> use ACPI, so please go ahead with proposal X, thanks for your efforts".
>
> Don't complain about me ranting if you belittle my volunteer work that I
> believe Linaro and its partners should've done in the first place: If I
> can get an initial mainline PoC done as an individual on a few
> evenings/weekends, then the same should be super-easy for an
> organization with lots of engineers and paying member companies.

The only person doing the ranting, rebelling and belittling in this
thread is you. I have never commented on the nature of your work, let
alone belittle it.

I understand you are frustrated with how some of the upstreaming of
96boards is handled. I don't have anything to do with that. The only
96boards i have in my drawer (and never use) is an original HiKey.

I work for the enterprise group, not the 96boards team, and I make a
point of not working with vendor trees at all. The only reason I
submitted some patches to the upcoming release of the ERP is so that
we have an installer that works out of the box, but all the patches I
did contribute were already queued for v4.15 at that point.

> As I've pointed out, an ever-increasing frustration builds over Linaro
> continuing to announce new boards (such as SynQuacer) that will be the
> best since sliced bread, while neglecting the 96boards that are already
> on the market and equally are promoted under the "96Boards" brand.
> The Linaro CEO has been promoting the Orange Pi i96 in keynotes, so
> management is aware of that hardware, and yet not a single patch came
> from Xunlong, RDA Micro or Linaro. No patch review from RDA either. And
> my patches got stuck on the bindings not including interrupts property
> for the UART yet, since I still do not have their custom interrupt
> controller working... So the context here is that not just my 4.14+
> pulls got stuck but three other 96Boards patch series, too.
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue
Date: Mon, 6 Nov 2017 11:28:05 +0000	[thread overview]
Message-ID: <CAKv+Gu_Wkdd3EdOjKJYZN5Ypjodpu5kFU=Ubg9H5e6ER3zq8Mg@mail.gmail.com> (raw)
In-Reply-To: <c3c5b129-cd30-335d-80fd-05e9e4756121@suse.de>

On 6 November 2017 at 06:58, Andreas F?rber <afaerber@suse.de> wrote:
> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
[...]
>>
>> Again, I am not the one who is ranting here. You hit a nerve by
>> accusing me of 'rebelling against linux.git' while this is quite the
>> opposite of what I am doing.
>
> Actually you did confirm that point by starting an argument about not
> needing a central repository and you not liking Linux as the location.
> That was exactly what I meant with my original comment.
>
> Adding Actions Semi was somewhat easy as a new vendor and now - roughly
> a year after the board went to market - there's Linaro contributions
> from Mani that I'm thankful for.
>
> Whereas patches keep falling into a dark hole when there's already other
> work for a certain vendor, such as Marvell and now Socionext, with no
> one feeling responsible for either taking them or saying, "hey, we're
> not going to submit any conflicting DT bindings for SynQuacer because we
> use ACPI, so please go ahead with proposal X, thanks for your efforts".
>
> Don't complain about me ranting if you belittle my volunteer work that I
> believe Linaro and its partners should've done in the first place: If I
> can get an initial mainline PoC done as an individual on a few
> evenings/weekends, then the same should be super-easy for an
> organization with lots of engineers and paying member companies.

The only person doing the ranting, rebelling and belittling in this
thread is you. I have never commented on the nature of your work, let
alone belittle it.

I understand you are frustrated with how some of the upstreaming of
96boards is handled. I don't have anything to do with that. The only
96boards i have in my drawer (and never use) is an original HiKey.

I work for the enterprise group, not the 96boards team, and I make a
point of not working with vendor trees at all. The only reason I
submitted some patches to the upcoming release of the ERP is so that
we have an installer that works out of the box, but all the patches I
did contribute were already queued for v4.15 at that point.

> As I've pointed out, an ever-increasing frustration builds over Linaro
> continuing to announce new boards (such as SynQuacer) that will be the
> best since sliced bread, while neglecting the 96boards that are already
> on the market and equally are promoted under the "96Boards" brand.
> The Linaro CEO has been promoting the Orange Pi i96 in keynotes, so
> management is aware of that hardware, and yet not a single patch came
> from Xunlong, RDA Micro or Linaro. No patch review from RDA either. And
> my patches got stuck on the bindings not including interrupts property
> for the UART yet, since I still do not have their custom interrupt
> controller working... So the context here is that not just my 4.14+
> pulls got stuck but three other 96Boards patch series, too.
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
> GF: Felix Imend?rffer, Jane Smithard, Graham Norton
> HRB 21284 (AG N?rnberg)

  parent reply	other threads:[~2017-11-06 11:28 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 17:00 [PATCH 0/5] ARM: Socionext MB86S71 and Fujitsu F-Cue enablement Andreas Färber
2017-06-25 17:00 ` Andreas Färber
2017-06-25 17:00 ` Andreas Färber
2017-06-25 17:00 ` [PATCH 1/5] clk: mb86s7x: Suppress build Andreas Färber
2017-06-25 17:00   ` Andreas Färber
2017-06-28 16:13   ` Stephen Boyd
2017-06-28 16:13     ` Stephen Boyd
2017-06-28 17:32     ` Jassi Brar
2017-06-28 17:32       ` Jassi Brar
2017-06-28 17:32       ` Jassi Brar
2017-06-28 22:29       ` Stephen Boyd
2017-06-28 22:29         ` Stephen Boyd
2017-06-29 11:17         ` Andreas Färber
2017-06-29 11:17           ` Andreas Färber
2017-06-29 11:17           ` Andreas Färber
2017-06-25 17:00 ` [PATCH 2/5] ARM: Prepare Socionext MB86S71 Andreas Färber
2017-06-25 17:00   ` Andreas Färber
2017-06-25 17:00 ` [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue Andreas Färber
2017-06-25 17:00   ` Andreas Färber
2017-06-25 17:00   ` Andreas Färber
2017-06-28 16:46   ` Rob Herring
2017-06-28 16:46     ` Rob Herring
2017-06-28 16:46     ` Rob Herring
2017-06-29 12:18     ` Masahiro Yamada
2017-06-29 12:18       ` Masahiro Yamada
2017-06-29 12:18       ` Masahiro Yamada
2017-06-29 12:53       ` Andreas Färber
2017-06-29 12:53         ` Andreas Färber
2017-06-29 12:53         ` Andreas Färber
2017-06-29 17:18         ` Masahiro Yamada
2017-06-29 17:18           ` Masahiro Yamada
2017-06-29 17:18           ` Masahiro Yamada
2017-11-04 13:44           ` Andreas Färber
2017-11-04 13:44             ` Andreas Färber
2017-11-04 13:44             ` Andreas Färber
2017-11-04 14:57             ` Ard Biesheuvel
2017-11-04 14:57               ` Ard Biesheuvel
2017-11-04 15:30               ` Andreas Färber
2017-11-04 15:30                 ` Andreas Färber
2017-11-04 15:30                 ` Andreas Färber
2017-11-04 15:39                 ` Ard Biesheuvel
2017-11-04 15:39                   ` Ard Biesheuvel
2017-11-04 20:06                   ` Andreas Färber
2017-11-04 20:06                     ` Andreas Färber
2017-11-04 20:06                     ` Andreas Färber
2017-11-04 20:39                     ` Ard Biesheuvel
2017-11-04 20:39                       ` Ard Biesheuvel
2017-11-06  6:58                       ` Andreas Färber
2017-11-06  6:58                         ` Andreas Färber
2017-11-06  6:58                         ` Andreas Färber
2017-11-06  8:05                         ` Yang Zhang
2017-11-06  8:05                           ` Yang Zhang
2017-11-06 11:28                         ` Ard Biesheuvel [this message]
2017-11-06 11:28                           ` Ard Biesheuvel
2017-11-06 11:28                           ` Ard Biesheuvel
2017-11-13 15:40                           ` Andreas Färber
2017-11-13 15:40                             ` Andreas Färber
2017-11-13 15:40                             ` Andreas Färber
2017-11-13 15:55                             ` Ard Biesheuvel
2017-11-13 15:55                               ` Ard Biesheuvel
2017-06-25 17:00 ` [PATCH 4/5] ARM: dts: Add " Andreas Färber
2017-06-25 17:00   ` Andreas Färber
2017-06-25 17:00 ` [PATCH 5/5] ARM: dts: mb86s71-f-cue: Add fake UART0 clock Andreas Färber
2017-06-25 17:00   ` Andreas Färber

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='CAKv+Gu_Wkdd3EdOjKJYZN5Ypjodpu5kFU=Ubg9H5e6ER3zq8Mg@mail.gmail.com' \
    --to=ard.biesheuvel@linaro.org \
    --cc=Grant.Likely@arm.com \
    --cc=afaerber@suse.de \
    --cc=amit.kucheria@linaro.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=okamoto.satoru@socionext.com \
    --cc=olof@lixom.net \
    --cc=robh@kernel.org \
    --cc=yamada.masahiro@socionext.com \
    --cc=yang.zhang@96boards.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.