On 13 November 2017 at 15:40, Andreas Färber wrote:
> Am 06.11.2017 um 12:28 schrieb Ard Biesheuvel:
>> On 6 November 2017 at 06:58, Andreas Färber wrote:
>>> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
>> [...]
Again, I am not the one who is
On 13 November 2017 at 15:40, Andreas Färber wrote:
> Am 06.11.2017 um 12:28 schrieb Ard Biesheuvel:
>> On 6 November 2017 at 06:58, Andreas Färber 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
Am 06.11.2017 um 12:28 schrieb Ard Biesheuvel:
> On 6 November 2017 at 06:58, Andreas Färber 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'
Am 06.11.2017 um 12:28 schrieb Ard Biesheuvel:
> On 6 November 2017 at 06:58, Andreas Färber 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
On 6 November 2017 at 06:58, Andreas Färber 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.
On 6 November 2017 at 06:58, Andreas Färber 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
> On 6 Nov 2017, at 06:58, Andreas Färber wrote:
>
>> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 20:06, Andreas Färber wrote:
Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 15:30, Andreas Färber
> On 6 Nov 2017, at 06:58, Andreas Färber wrote:
>
>> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 20:06, Andreas Färber wrote:
Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 15:30, Andreas Färber wrote:
>> Am 04.11.2017 um
Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 20:06, Andreas Färber wrote:
>> Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 15:30, Andreas Färber wrote:
Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 20:06, Andreas Färber wrote:
>> Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 15:30, Andreas Färber wrote:
Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
> On 4 November 2017 at 13:44,
On 4 November 2017 at 20:06, Andreas Färber wrote:
> Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
>> On 4 November 2017 at 15:30, Andreas Färber wrote:
>>> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
On 4 November 2017 at 13:44, Andreas Färber
On 4 November 2017 at 20:06, Andreas Färber wrote:
> Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
>> On 4 November 2017 at 15:30, Andreas Färber wrote:
>>> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
On 4 November 2017 at 13:44, Andreas Färber wrote:
> Hi everyone,
>
> The
Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 15:30, Andreas Färber wrote:
>> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 13:44, Andreas Färber wrote:
Hi everyone,
The non-building clk driver
Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 15:30, Andreas Färber wrote:
>> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 13:44, Andreas Färber wrote:
Hi everyone,
The non-building clk driver has been removed for 4.14, but this
On 4 November 2017 at 15:30, Andreas Färber wrote:
> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
>> On 4 November 2017 at 13:44, Andreas Färber wrote:
>>> Hi everyone,
>>>
>>> The non-building clk driver has been removed for 4.14, but this patchset
>>>
On 4 November 2017 at 15:30, Andreas Färber wrote:
> Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
>> On 4 November 2017 at 13:44, Andreas Färber wrote:
>>> Hi everyone,
>>>
>>> The non-building clk driver has been removed for 4.14, but this patchset
>>> seems stuck on matters of naming and
Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
> On 4 November 2017 at 13:44, Andreas Färber wrote:
>> Hi everyone,
>>
>> The non-building clk driver has been removed for 4.14, but this patchset
>> seems stuck on matters of naming and maintenance...
>>
>> Am 30.06.2017 um 01:18
Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
> On 4 November 2017 at 13:44, Andreas Färber wrote:
>> Hi everyone,
>>
>> The non-building clk driver has been removed for 4.14, but this patchset
>> seems stuck on matters of naming and maintenance...
>>
>> Am 30.06.2017 um 01:18 schrieb Masahiro
On 4 November 2017 at 13:44, Andreas Färber wrote:
> Hi everyone,
>
> The non-building clk driver has been removed for 4.14, but this patchset
> seems stuck on matters of naming and maintenance...
>
> Am 30.06.2017 um 01:18 schrieb Masahiro Yamada:
>> Hi Andreas,
>>
>>
On 4 November 2017 at 13:44, Andreas Färber wrote:
> Hi everyone,
>
> The non-building clk driver has been removed for 4.14, but this patchset
> seems stuck on matters of naming and maintenance...
>
> Am 30.06.2017 um 01:18 schrieb Masahiro Yamada:
>> Hi Andreas,
>>
>> 2017-06-29 21:53 GMT+09:00
Hi everyone,
The non-building clk driver has been removed for 4.14, but this patchset
seems stuck on matters of naming and maintenance...
Am 30.06.2017 um 01:18 schrieb Masahiro Yamada:
> Hi Andreas,
>
> 2017-06-29 21:53 GMT+09:00 Andreas Färber :
>> Hi Masahiro-san,
>>
>> Am
Hi everyone,
The non-building clk driver has been removed for 4.14, but this patchset
seems stuck on matters of naming and maintenance...
Am 30.06.2017 um 01:18 schrieb Masahiro Yamada:
> Hi Andreas,
>
> 2017-06-29 21:53 GMT+09:00 Andreas Färber :
>> Hi Masahiro-san,
>>
>> Am 29.06.2017 um
Hi Andreas,
2017-06-29 21:53 GMT+09:00 Andreas Färber :
> Hi Masahiro-san,
>
> Am 29.06.2017 um 14:18 schrieb Masahiro Yamada:
>> 2017-06-29 1:46 GMT+09:00 Rob Herring :
>>> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
For consistency
Hi Andreas,
2017-06-29 21:53 GMT+09:00 Andreas Färber :
> Hi Masahiro-san,
>
> Am 29.06.2017 um 14:18 schrieb Masahiro Yamada:
>> 2017-06-29 1:46 GMT+09:00 Rob Herring :
>>> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
For consistency with existing SoC bindings, use
Hi Masahiro-san,
Am 29.06.2017 um 14:18 schrieb Masahiro Yamada:
> 2017-06-29 1:46 GMT+09:00 Rob Herring :
>> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
>>> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
>>> socionext.txt.
>>>
>>>
Hi Masahiro-san,
Am 29.06.2017 um 14:18 schrieb Masahiro Yamada:
> 2017-06-29 1:46 GMT+09:00 Rob Herring :
>> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
>>> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
>>> socionext.txt.
>>>
>>> Signed-off-by: Andreas
2017-06-29 1:46 GMT+09:00 Rob Herring :
> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
>> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
>> socionext.txt.
>>
>> Signed-off-by: Andreas Färber
>> ---
>>
2017-06-29 1:46 GMT+09:00 Rob Herring :
> On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
>> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
>> socionext.txt.
>>
>> Signed-off-by: Andreas Färber
>> ---
>> Documentation/devicetree/bindings/arm/socionext.txt |
On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
> socionext.txt.
>
> Signed-off-by: Andreas Färber
> ---
> Documentation/devicetree/bindings/arm/socionext.txt | 17 +
> 1
On Sun, Jun 25, 2017 at 07:00:18PM +0200, Andreas Färber wrote:
> For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
> socionext.txt.
>
> Signed-off-by: Andreas Färber
> ---
> Documentation/devicetree/bindings/arm/socionext.txt | 17 +
> 1 file changed, 17
For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
socionext.txt.
Signed-off-by: Andreas Färber
---
Documentation/devicetree/bindings/arm/socionext.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
socionext.txt.
Signed-off-by: Andreas Färber
---
Documentation/devicetree/bindings/arm/socionext.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
32 matches
Mail list logo