All of lore.kernel.org
 help / color / mirror / Atom feed
From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: BCM5301X: Add DT for Netgear R6300 V2
Date: Wed, 03 Dec 2014 09:40:40 +0100	[thread overview]
Message-ID: <547ECC88.1080308@hauke-m.de> (raw)
In-Reply-To: <CACna6rwg7+jqiRy9N+RHKJo9EadRzcq-4-8zJziq_Tvko3LYtg@mail.gmail.com>

On 12/03/2014 06:59 AM, Rafa? Mi?ecki wrote:
> On 3 December 2014 at 00:15, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>> On 11/30/2014 06:28 PM, Rafa? Mi?ecki wrote:
>>> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
>>> ---
>>>  arch/arm/boot/dts/Makefile                     |  4 +-
>>>  arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts | 84 ++++++++++++++++++++++++++
>>>  2 files changed, 87 insertions(+), 1 deletion(-)
>>>  create mode 100644 arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts
>>>
>>> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
>>> index 35f3e12..22bb87f 100644
>>> --- a/arch/arm/boot/dts/Makefile
>>> +++ b/arch/arm/boot/dts/Makefile
>>> @@ -55,7 +55,9 @@ dtb-$(CONFIG_ARCH_ATLAS6) += atlas6-evb.dtb
>>>  dtb-$(CONFIG_ARCH_AXXIA) += axm5516-amarillo.dtb
>>>  dtb-$(CONFIG_ARCH_BCM2835) += bcm2835-rpi-b.dtb
>>>  dtb-$(CONFIG_ARCH_BCM2835) += bcm2835-rpi-b-plus.dtb
>>> -dtb-$(CONFIG_ARCH_BCM_5301X) += bcm4708-netgear-r6250.dtb
>>> +dtb-$(CONFIG_ARCH_BCM_5301X) += \
>>> +     bcm4708-netgear-r6250.dtb \
>>> +     bcm4708-netgear-r6300-v2.dtb
>>
>> This part does not apply cleanly on top of v3.18-rc1.
> 
> I think we want these changes to be merged merged into the arm-soc.git
> next/dt, right? So I based my changes on that tree. This way Arnd
> won't get neither: any conflicts or any unwanted stuff.

Arnd wants the changes based on -rc1, at least the last time. ;-) The
merge gets ugly if the changes are based on different versions.

>>>  dtb-$(CONFIG_ARCH_BCM_63XX) += bcm963138dvt.dtb
>>>  dtb-$(CONFIG_ARCH_BCM_CYGNUS) += bcm911360_entphn.dtb \
>>>       bcm911360k.dtb \
>>> diff --git a/arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts b/arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts
>>> new file mode 100644
>>> index 0000000..e18b636
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts
>>> @@ -0,0 +1,84 @@
>>> +/*
>>> + * Broadcom BCM470X / BCM5301X ARM platform code.
>>> + * DTS for Netgear R6300 V2
>>> + *
>>> + * Copyright ? 2014 Rafa? Mi?ecki <zajec5@gmail.com>
>>
>> Is this ? needed here?
> 
> Do you mean the whole line or the "?" sign? I think we usually have
> "Copyright" lines in files. I can see using "?" is much less common on
> the other hand. I think the most common forms are
> 1) Copyright (C) <year>
> 2) Copyright <year>
> Should I use some of them?
> Btw. do you know if this documented anywhere?
> 
It was just the  "?" sign, it's usage is pretty uncommon and I think it
is not an ASCII symbol. I would like if you choose 1 or 2, what exactly
does not matter for me.

Hauke

Hauke

  reply	other threads:[~2014-12-03  8:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 17:28 [PATCH 1/5] ARM: BCM5301X: Add buttons for Netgear R6250 Rafał Miłecki
2014-11-30 17:28 ` [PATCH 2/5] ARM: BCM5301X: Add DT for Netgear R6300 V2 Rafał Miłecki
2014-12-02 23:15   ` Hauke Mehrtens
2014-12-03  5:59     ` Rafał Miłecki
2014-12-03  8:40       ` Hauke Mehrtens [this message]
2014-12-03 10:25         ` Arnd Bergmann
2014-12-04  9:22   ` [PATCH V2 " Rafał Miłecki
2014-11-30 17:28 ` [PATCH 3/5] ARM: BCM5301X: Add DT for Buffalo WZR-1750DHP Rafał Miłecki
2014-12-04  9:22   ` [PATCH V2 " Rafał Miłecki
2014-11-30 17:28 ` [PATCH 4/5] ARM: BCM5301X: Add DT for Asus RT-N18U Rafał Miłecki
2014-12-02 23:19   ` Hauke Mehrtens
2014-12-03  5:40     ` Rafał Miłecki
2014-12-03  6:01       ` Rafał Miłecki
2014-12-03  7:50         ` Uwe Kleine-König
2014-12-03  8:34       ` Hauke Mehrtens
2014-12-04  9:12       ` Rafał Miłecki
2014-12-04  9:23   ` [PATCH V2 " Rafał Miłecki
2014-11-30 17:28 ` [PATCH 5/5] ARM: BCM5301X: Add DT for Buffalo WZR-600DHP2 Rafał Miłecki
2014-12-04  9:24   ` [PATCH V2 " Rafał Miłecki

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=547ECC88.1080308@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.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.