From: Lee Jones <lee@kernel.org>
To: Larry Lai <larry.lai@yunjingtech.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"GaryWang@aaeon.com.tw" <GaryWang@aaeon.com.tw>,
Musa Lin <musa.lin@yunjingtech.com>,
Jack Chang <jack.chang@yunjingtech.com>,
Noah Hung <noah.hung@yunjingtech.com>
Subject: Re: 回覆: [PATCH V6 2/3] pinctrl: Add support pin control for UP board CPLD/FPGA
Date: Thu, 21 Sep 2023 11:58:38 +0100 [thread overview]
Message-ID: <20230921105838.GF3449785@google.com> (raw)
In-Reply-To: <SEYPR06MB65077401CD3AA45A9D5E5C97F9FAA@SEYPR06MB6507.apcprd06.prod.outlook.com>
On Tue, 19 Sep 2023, Larry Lai wrote:
> Hi Linus,
>
> Thank you for spending time to review the V6 patch, for your question, please kindly to check our comments with ">>" beginning.
I don't know about anyone else, but I'm finding this format hard to
read. A full conversation using this style would be impossible to
decipher.
Please can you configure your editor/client to quote and reply properly?
That way previous responses and your comments can be easily
differentiated.
> 寄件者: Linus Walleij <linus.walleij@linaro.org>
> 寄件日期: 2023年9月15日 下午 05:02
> 收件者: Larry Lai <larry.lai@yunjingtech.com>
> 副本: lee@kernel.org <lee@kernel.org>; andriy.shevchenko@linux.intel.com <andriy.shevchenko@linux.intel.com>; pavel@ucw.cz <pavel@ucw.cz>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; linux-gpio@vger.kernel.org <linux-gpio@vger.kernel.org>; linux-leds@vger.kernel.org <linux-leds@vger.kernel.org>; GaryWang@aaeon.com.tw <GaryWang@aaeon.com.tw>; Musa Lin <musa.lin@yunjingtech.com>; Jack Chang <jack.chang@yunjingtech.com>; Noah Hung <noah.hung@yunjingtech.com>
> 主旨: Re: [PATCH V6 2/3] pinctrl: Add support pin control for UP board CPLD/FPGA
Your client should automatically strip this from the mail body.
>
> On Fri, Sep 15, 2023 at 5:12 AM larry.lai <larry.lai@yunjingtech.com> wrote:
>
> > The UP Squared board <http://www.upboard.com> implements certain
> > features (pin control) through an on-board FPGA.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Gary Wang <garywang@aaeon.com.tw>
> > Signed-off-by: larry.lai <larry.lai@yunjingtech.com>
>
> This v6 overall looks good to me!
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Can the patch be merged on its own?
>
> > +#include "core.h"
> > +#include "intel/pinctrl-intel.h"
>
> Didn't notice this before. But if Andy is OK with it, I'm
> OK with it, I guess there is a reason? Perhaps it warrants
> a comment explaining why you do this?
> >>
> Need struct intel_pinctrl gpp information to control dedicated Raspberry Pi compatible GPIOs.
> These products (Up boards) are intel approves foundation kits.
>
> Valid reasons:
> - You are using Intel-specific HW features also found in this
> FPGA
>
> Invalid reasons:
> - Using nifty macros or helpers, then either make them generic
> or (if they are small) duplicate them.
>
> If it was that thing I asked Andy to keep locally because I didn't
> agree with its generic usefulness, maybe I should be told to
> reconsider.
>
> Yours,
> Linus Walleij
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-09-21 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 3:11 [PATCH V6 0/3] Add support control UP board CPLD/FPGA pin control larry.lai
2023-09-15 3:11 ` [PATCH V6 1/3] mfd: Add support for UP board CPLD/FPGA larry.lai
2023-09-21 11:19 ` Lee Jones
2023-09-15 3:11 ` [PATCH V6 2/3] pinctrl: Add support pin control " larry.lai
2023-09-15 9:02 ` Linus Walleij
2023-09-19 10:10 ` 回覆: " Larry Lai
2023-09-21 10:58 ` Lee Jones [this message]
2023-10-31 2:16 ` larry
2023-09-15 18:46 ` kernel test robot
2023-09-15 3:11 ` [PATCH V6 3/3] leds: Add support for UP board CPLD onboard LEDS larry.lai
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=20230921105838.GF3449785@google.com \
--to=lee@kernel.org \
--cc=GaryWang@aaeon.com.tw \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jack.chang@yunjingtech.com \
--cc=larry.lai@yunjingtech.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=musa.lin@yunjingtech.com \
--cc=noah.hung@yunjingtech.com \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).