From: "Andreas Färber" <afaerber@suse.de>
To: Andrei Stefanescu <andrei.stefanescu@nxp.com>,
Chester Lin <clin@suse.com>
Cc: dl-S32 <S32@nxp.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linus Walleij <linus.walleij@linaro.org>,
Larisa Ileana Grigore <larisa.grigore@nxp.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>,
Radu Pirea <radu-nicolae.pirea@nxp.com>,
Matthias Brugger <mbrugger@suse.com>,
Matthew Nunez <matthew.nunez@nxp.com>,
Phu Luu An <phu.luuan@nxp.com>,
Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>, Jacky Bai <ping.bai@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 2/2] pinctrl: add NXP S32 SoC family support
Date: Tue, 8 Nov 2022 17:51:51 +0100 [thread overview]
Message-ID: <d3905a85-4746-09e8-ecf9-b39757bf6d85@suse.de> (raw)
In-Reply-To: <AM9PR04MB8487C664E75EBA4D3678DD03E33F9@AM9PR04MB8487.eurprd04.prod.outlook.com>
Hi Chester and Andrei,
Am 08.11.22 um 15:54 schrieb Andrei Stefanescu:
>> diff --git a/drivers/pinctrl/freescale/pinctrl-s32.h b/drivers/pinctrl/freescale/pinctrl-s32.h
>> new file mode 100644
>> index 000000000000..7b48fe3d73c9
>> --- /dev/null
>> +++ b/drivers/pinctrl/freescale/pinctrl-s32.h
>> @@ -0,0 +1,65 @@
>> +/* SPDX-License-Identifier: GPL-2.0-or-later
>> + *
>> + * S32 pinmux core definitions
>> + *
>> + * Copyright (C) 2016-2020,2022 NXP
>
> Could we also add: " * Copyright 2015-2016 Freescale Semiconductor, Inc."?
... and insert a space before 2022, while at it.
@Andrei: Intentionally no (C) or (c) for Freescale? (column alignment)
Cheers,
Andreas
--
SUSE Software Solutions Germany GmbH
Frankenstraße 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2022-11-08 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 10:08 [PATCH 0/2] Add pinctrl support for S32 SoC family Chester Lin
2022-10-31 10:08 ` [PATCH 1/2] dt-bindings: pinctrl: add schema for NXP S32 SoCs Chester Lin
2022-11-02 15:49 ` Rob Herring
2022-11-09 15:04 ` Chester Lin
2022-11-08 12:31 ` Linus Walleij
2022-11-09 16:45 ` Chester Lin
2022-11-10 10:00 ` Linus Walleij
2022-11-10 11:18 ` Andrei Stefanescu
2022-10-31 10:08 ` [PATCH 2/2] pinctrl: add NXP S32 SoC family support Chester Lin
2022-11-08 12:35 ` Linus Walleij
2022-11-08 14:54 ` Andrei Stefanescu
2022-11-08 16:51 ` Andreas Färber [this message]
2022-11-09 9:06 ` Andrei Stefanescu
2022-11-09 9:18 ` Chester Lin
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=d3905a85-4746-09e8-ecf9-b39757bf6d85@suse.de \
--to=afaerber@suse.de \
--cc=S32@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=andrei.stefanescu@nxp.com \
--cc=clin@suse.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@nxp.com \
--cc=kernel@pengutronix.de \
--cc=larisa.grigore@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.nunez@nxp.com \
--cc=mbrugger@suse.com \
--cc=phu.luuan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=radu-nicolae.pirea@nxp.com \
--cc=shawnguo@kernel.org \
--cc=stefan-gabriel.mirea@nxp.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 NNTP newsgroup(s).