From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "larry.lai" <larry.lai@yunjingtech.com>
Cc: lee@kernel.org, linus.walleij@linaro.org, pavel@ucw.cz,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-leds@vger.kernel.org, GaryWang@aaeon.com.tw,
musa.lin@yunjingtech.com, jack.chang@yunjingtech.com,
noah.hung@yunjingtech.com
Subject: Re: [RFC 0/3] Add support control UP board CPLD/FPGA pin control
Date: Wed, 7 Dec 2022 23:38:50 +0200 [thread overview]
Message-ID: <Y5EH6nKyMxe90eLo@smile.fi.intel.com> (raw)
In-Reply-To: <Y5EHZX8xHDSjG3FI@smile.fi.intel.com>
On Wed, Dec 07, 2022 at 11:36:37PM +0200, Andy Shevchenko wrote:
> On Thu, Dec 08, 2022 at 12:33:56AM +0800, larry.lai wrote:
> > The UP board <http://www.upboard.com> is the computer board for
> > Professional Makers and Industrial Applications. We want to upstream
> > the UP board 40-pin GP-bus Kernel driver for giving the users better
> > experience on the software release. (not just download from UP board
> > github)
> >
> > These patches are generated from the Linux kernel mainline tag v6.0.
>
> I have just checked the v3 (previous version of this) and I haven't found any
> evidence that I gave my tag or permission to use it. What the heck is going on
> here?!
NAK to this series.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-12-07 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 16:33 [RFC 0/3] Add support control UP board CPLD/FPGA pin control larry.lai
2022-12-07 16:33 ` [RFC 1/3] mfd: Add support for UP board CPLD/FPGA larry.lai
2022-12-07 21:10 ` Andy Shevchenko
2023-04-25 15:28 ` 回覆: " Larry Lai
2022-12-07 16:33 ` [RFC 2/3] pinctrl: Add support pin control " larry.lai
2022-12-07 21:32 ` Andy Shevchenko
2023-04-25 15:28 ` 回覆: " Larry Lai
2022-12-07 22:55 ` kernel test robot
2022-12-07 16:33 ` [RFC 3/3] leds: Add support for UP board CPLD onboard LEDS larry.lai
2022-12-07 21:09 ` [RFC 0/3] Add support control UP board CPLD/FPGA pin control Linus Walleij
2022-12-07 21:33 ` Andy Shevchenko
2022-12-07 21:36 ` Andy Shevchenko
2022-12-07 21:38 ` Andy Shevchenko [this message]
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=Y5EH6nKyMxe90eLo@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=GaryWang@aaeon.com.tw \
--cc=jack.chang@yunjingtech.com \
--cc=larry.lai@yunjingtech.com \
--cc=lee@kernel.org \
--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 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.