From: Aapo Vienamo <aapo.vienamo@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] gpio: Add Intel Granite Rapids-D vGPIO driver
Date: Fri, 19 Apr 2024 16:32:45 +0300 [thread overview]
Message-ID: <io2megd6ymifff3ae6bqvdig5de3loczdmbnhoao3e32vuiqvh@pkqmxl4p7yy2> (raw)
In-Reply-To: <CAHp75Ve=TUqba0Ga23QCiP7uM==VzY6kL=3A-5k5WNJAz4gGuA@mail.gmail.com>
On Fri, Apr 19, 2024 at 04:12:55PM GMT, Andy Shevchenko wrote:
> On Fri, Apr 19, 2024 at 11:07 AM Aapo Vienamo
> <aapo.vienamo@linux.intel.com> wrote:
> >
> > This driver provides a basic GPIO driver for the Intel Granite Rapids-D
> > virtual GPIOs. On SoCs with limited physical pins on the package, the
> > physical pins controlled by this driver would be exposed on an external
> > device such as a BMC or CPLD.
> >
> > Signed-off-by: Aapo Vienamo <aapo.vienamo@linux.intel.com>
> > Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Hmm... How did this happen?
This happened because the commits got mixed up between the internal tree
and my own branch. Apologies for that.
Sincerely,
Aapo
next prev parent reply other threads:[~2024-04-19 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:05 [PATCH] gpio: Add Intel Granite Rapids-D vGPIO driver Aapo Vienamo
2024-04-19 13:11 ` Linus Walleij
2024-04-19 14:42 ` Aapo Vienamo
2024-04-21 18:33 ` Linus Walleij
2024-04-19 13:12 ` Andy Shevchenko
2024-04-19 13:32 ` Aapo Vienamo [this message]
2024-04-19 19:59 ` Elliott, Robert (Servers)
2024-04-19 22:02 ` Andy Shevchenko
2024-04-22 10:20 ` Bartosz Golaszewski
2024-04-22 20:59 ` Elliott, Robert (Servers)
2024-04-23 13:47 ` Ilpo Järvinen
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=io2megd6ymifff3ae6bqvdig5de3loczdmbnhoao3e32vuiqvh@pkqmxl4p7yy2 \
--to=aapo.vienamo@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).