All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver
Date: Tue, 19 Jan 2021 00:06:46 +0000	[thread overview]
Message-ID: <BL0PR04MB6514F31612704D9338EBB3F9E7A30@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: CACRpkdbTazK7yLPVe79SoneD+tdiXv9GPvN29dSMgCZkf8Pjbg@mail.gmail.com

On 2021/01/18 22:33, Linus Walleij wrote:
> Hi Damien,
> 
> this looks all right to me.
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Thanks !

> 
> Shall I apply just this one patch to the pinctrl tree?
> 
> I think the line that touches arch/*/Kconfig should be dropped
> then, that better go to the SoC tree.

Good point. I can send a v14 series that does that. Or simpler, if that is OK
with you and Palmer, Palmer could may be take the patch through the riscv tree ?

> 
> Yours,
> Linus Walleij
> 


-- 
Damien Le Moal
Western Digital Research

WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH v11 02/10] pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver
Date: Tue, 19 Jan 2021 00:06:46 +0000	[thread overview]
Message-ID: <BL0PR04MB6514F31612704D9338EBB3F9E7A30@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: CACRpkdbTazK7yLPVe79SoneD+tdiXv9GPvN29dSMgCZkf8Pjbg@mail.gmail.com

On 2021/01/18 22:33, Linus Walleij wrote:
> Hi Damien,
> 
> this looks all right to me.
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Thanks !

> 
> Shall I apply just this one patch to the pinctrl tree?
> 
> I think the line that touches arch/*/Kconfig should be dropped
> then, that better go to the SoC tree.

Good point. I can send a v14 series that does that. Or simpler, if that is OK
with you and Palmer, Palmer could may be take the patch through the riscv tree ?

> 
> Yours,
> Linus Walleij
> 


-- 
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-19  0:08 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 [this message]
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
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=BL0PR04MB6514F31612704D9338EBB3F9E7A30@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.