From: Peter Rosin <peda@axentia.se>
To: Vadim Pasternak <vadimp@nvidia.com>, wsa@the-dreams.de
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH i2c-next v2 2/7] platform/x86: mlxcpld: Update module license
Date: Thu, 28 Jan 2021 11:10:44 +0100 [thread overview]
Message-ID: <6d23cba3-ac6c-f209-478d-18bcb8d843c4@axentia.se> (raw)
In-Reply-To: <20210122192502.17645-3-vadimp@nvidia.com>
On 2021-01-22 20:24, Vadim Pasternak wrote:
> Update license to SPDX-License.
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
Acked-by: Peter Rosin <peda@axentia.se>
Cheers,
Peter
next prev parent reply other threads:[~2021-01-28 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:24 [PATCH i2c-next v2 0/7] i2c: mux: mlxcpld: Extend driver functionality and update licenses Vadim Pasternak
2021-01-22 19:24 ` [PATCH i2c-next v2 1/7] i2c: mux: mlxcpld: Update module license Vadim Pasternak
2021-01-28 10:09 ` Peter Rosin
2021-02-01 21:56 ` Wolfram Sang
2021-01-22 19:24 ` [PATCH i2c-next v2 2/7] platform/x86: " Vadim Pasternak
2021-01-28 10:10 ` Peter Rosin [this message]
2021-02-01 21:56 ` Wolfram Sang
2021-01-22 19:24 ` [PATCH i2c-next v2 3/7] i2c: mux: mlxcpld: Move header file out of x86 realm Vadim Pasternak
2021-01-28 10:11 ` Peter Rosin
2021-02-01 21:56 ` Wolfram Sang
2021-01-22 19:24 ` [PATCH i2c-next v2 4/7] i2c: mux: mlxcpld: Convert driver to platform driver Vadim Pasternak
2021-01-22 19:25 ` [PATCH i2c-next v2 5/7] i2c: mux: mlxcpld: Extend driver to support word address space devices Vadim Pasternak
2021-01-25 21:37 ` Peter Rosin
[not found] ` <DM6PR12MB38987A5C2B8A8429289BA6CDAFBA9@DM6PR12MB3898.namprd12.prod.outlook.com>
2021-01-29 23:00 ` Peter Rosin
2021-01-22 19:25 ` [PATCH i2c-next v2 6/7] i2c: mux: mlxcpld: Extend supported mux number Vadim Pasternak
2021-01-22 19:25 ` [PATCH i2c-next v2 7/7] i2c: mux: mlxcpld: Add callback to notify mux creation completion Vadim Pasternak
2021-01-28 8:53 ` [PATCH i2c-next v2 0/7] i2c: mux: mlxcpld: Extend driver functionality and update licenses Wolfram Sang
2021-01-28 10:14 ` Peter Rosin
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=6d23cba3-ac6c-f209-478d-18bcb8d843c4@axentia.se \
--to=peda@axentia.se \
--cc=linux-i2c@vger.kernel.org \
--cc=vadimp@nvidia.com \
--cc=wsa@the-dreams.de \
/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).