All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: "linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"seanga2@gmail.com" <seanga2@gmail.com>
Subject: Re: [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver
Date: Sat, 23 Jan 2021 06:19:51 +0000	[thread overview]
Message-ID: <BL0PR04MB6514540BF8CC35309C376394E7BF0@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: mhng-4406eaf7-474a-41a6-8a23-8d75e79c8521@palmerdabbelt-glaptop

On 2021/01/23 13:15, Palmer Dabbelt wrote:
> On Thu, 21 Jan 2021 00:32:38 PST (-0800), Damien Le Moal wrote:
>>> On 2021/01/21 17:25, Linus Walleij wrote:
>>> On Thu, Jan 21, 2021 at 1:15 AM Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
>>>> On 2021/01/21 3:21, Palmer Dabbelt wrote:
>>>>> On Mon, 18 Jan 2021 05:33:05 PST (-0800), linus.walleij@linaro.org wrote:
>>>>>> Hi Damien,
>>>>>>
>>>>>> this looks all right to me.
>>>>>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>>>>>
>>>>>> Shall I apply just this one patch to the pinctrl tree?
>>>>>
>>>>> That's fine with me.  The DT bindings are in riscv/for-next, maybe it's best to
>>>>> take those as well and I'll drop them?  I don't generally like to drop stuff
>>>>> from for-next, but that's probably better than having everything all mixed up.
>>>>>
>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=for-next&id=ed3137edb31b86702511e7ad12b4abe8686b6805
>>>>>
>>>>>> I think the line that touches arch/*/Kconfig should be dropped
>>>>>> then, that better go to the SoC tree.
>>>>>
>>>>> I'm OK with you taking them along with my Ack, but if you don't want to that's
>>>>> fine.  Just LMK
>>>>>
>>>>> Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
>>>>
>>>> Linus,
>>>>
>>>> Please let me know which way you want to proceed. If you want to take the patch,
>>>> I will resend without the Kconfig change and move that change to another patch.
>>>
>>> It's fine to proceed as is, since Palmer already applied the bindings to
>>> his tree, just apply the pinctrl driver there as well. I don't see any
>>> risk of collisions in the tree.
>>
>> Sounds good. Thanks !
> 
> I don't see an actual Ack here, but I'm OK taking it.  IIRC there were some
> issues with the DT stuff as well, I don't remember if they got resolved or if I
> should be expecting a v14.

Palmer,

Linus sent a reviewed-by tag (see above).

For the dt-bindings problems, the v13 that I sent already addresses all make
dtbs_check warning and also addresses Rob's comments. The v13 dt-bindings
patches need review, as well as the clk driver patch. Will ping Stephen about
that one.
I will send a v14 only if there are more comments that need to be addressed.



-- 
Damien Le Moal
Western Digital Research

WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"seanga2@gmail.com" <seanga2@gmail.com>
Subject: Re: [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver
Date: Sat, 23 Jan 2021 06:19:51 +0000	[thread overview]
Message-ID: <BL0PR04MB6514540BF8CC35309C376394E7BF0@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: mhng-4406eaf7-474a-41a6-8a23-8d75e79c8521@palmerdabbelt-glaptop

On 2021/01/23 13:15, Palmer Dabbelt wrote:
> On Thu, 21 Jan 2021 00:32:38 PST (-0800), Damien Le Moal wrote:
>>> On 2021/01/21 17:25, Linus Walleij wrote:
>>> On Thu, Jan 21, 2021 at 1:15 AM Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
>>>> On 2021/01/21 3:21, Palmer Dabbelt wrote:
>>>>> On Mon, 18 Jan 2021 05:33:05 PST (-0800), linus.walleij@linaro.org wrote:
>>>>>> Hi Damien,
>>>>>>
>>>>>> this looks all right to me.
>>>>>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>>>>>
>>>>>> Shall I apply just this one patch to the pinctrl tree?
>>>>>
>>>>> That's fine with me.  The DT bindings are in riscv/for-next, maybe it's best to
>>>>> take those as well and I'll drop them?  I don't generally like to drop stuff
>>>>> from for-next, but that's probably better than having everything all mixed up.
>>>>>
>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=for-next&id=ed3137edb31b86702511e7ad12b4abe8686b6805
>>>>>
>>>>>> I think the line that touches arch/*/Kconfig should be dropped
>>>>>> then, that better go to the SoC tree.
>>>>>
>>>>> I'm OK with you taking them along with my Ack, but if you don't want to that's
>>>>> fine.  Just LMK
>>>>>
>>>>> Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
>>>>
>>>> Linus,
>>>>
>>>> Please let me know which way you want to proceed. If you want to take the patch,
>>>> I will resend without the Kconfig change and move that change to another patch.
>>>
>>> It's fine to proceed as is, since Palmer already applied the bindings to
>>> his tree, just apply the pinctrl driver there as well. I don't see any
>>> risk of collisions in the tree.
>>
>> Sounds good. Thanks !
> 
> I don't see an actual Ack here, but I'm OK taking it.  IIRC there were some
> issues with the DT stuff as well, I don't remember if they got resolved or if I
> should be expecting a v14.

Palmer,

Linus sent a reviewed-by tag (see above).

For the dt-bindings problems, the v13 that I sent already addresses all make
dtbs_check warning and also addresses Rob's comments. The v13 dt-bindings
patches need review, as well as the clk driver patch. Will ping Stephen about
that one.
I will send a v14 only if there are more comments that need to be addressed.



-- 
Damien Le Moal
Western Digital Research

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

  reply	other threads:[~2021-01-23  6:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  1:03 [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver Damien Le Moal
2021-01-12  1:03 ` Damien Le Moal
2021-01-18 13:33 ` Linus Walleij
2021-01-18 13:33   ` Linus Walleij
2021-01-19  0:06   ` Damien Le Moal
2021-01-19  0:06     ` Damien Le Moal
2021-01-20 18:21   ` Palmer Dabbelt
2021-01-20 18:21     ` Palmer Dabbelt
2021-01-21  0:15     ` Damien Le Moal
2021-01-21  0:15       ` Damien Le Moal
2021-01-21  8:25       ` Linus Walleij
2021-01-21  8:25         ` Linus Walleij
2021-01-21  8:32         ` Damien Le Moal
2021-01-21  8:32           ` Damien Le Moal
2021-01-23  4:15           ` Palmer Dabbelt
2021-01-23  4:15             ` Palmer Dabbelt
2021-01-23  6:19             ` Damien Le Moal [this message]
2021-01-23  6:19               ` Damien Le Moal
2021-01-27  5:46               ` Palmer Dabbelt
2021-01-27  5:46                 ` Palmer Dabbelt
  -- strict thread matches above, loose matches on Subject: below --
2021-01-12  0:58 [PATCH v11 00/10] RISC-V Kendryte K210 support improvements Damien Le Moal
2021-01-12  0:58 ` [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver Damien Le Moal
2021-01-14 23:32   ` Palmer Dabbelt
2021-01-15  0:17     ` Damien Le Moal
2021-01-15  0:39       ` Sean Anderson

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=BL0PR04MB6514540BF8CC35309C376394E7BF0@BL0PR04MB6514.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=seanga2@gmail.com \
    /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.