From: Krzysztof Kozlowski <krzk@kernel.org>
To: wangshuaijie@awinic.com, dmitry.torokhov@gmail.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jeff@labundy.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: liweilei@awinic.com, kangjiajun@awinic.com
Subject: Re: [PATCH V2 3/5] Add aw9610x series related interfaces to the aw_sar driver.
Date: Wed, 5 Jun 2024 12:22:16 +0200 [thread overview]
Message-ID: <4d8b7fe5-a566-49f7-8924-3c310af2f7cd@kernel.org> (raw)
In-Reply-To: <20240605091143.163789-4-wangshuaijie@awinic.com>
On 05/06/2024 11:11, wangshuaijie@awinic.com wrote:
> From: shuaijie wang <wangshuaijie@awinic.com>
>
No commit msg, no proper subject prefix.
> Signed-off-by: shuaijie wang <wangshuaijie@awinic.com>
> | Reported-by: kernel test robot <lkp@intel.com>
> | Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> | Reported-by: Dan Carpenter <error27@gmail.com>
Drop all these, this is some bogus tags. Tag never starts with pipe, btw.
> ---
> drivers/input/misc/aw_sar/aw9610x/aw9610x.c | 884 ++++++++++++++++++++
> drivers/input/misc/aw_sar/aw9610x/aw9610x.h | 327 ++++++++
> 2 files changed, 1211 insertions(+)
> create mode 100644 drivers/input/misc/aw_sar/aw9610x/aw9610x.c
> create mode 100644 drivers/input/misc/aw_sar/aw9610x/aw9610x.h
...
> +struct aw_reg_data {
> + unsigned char rw;
> + unsigned short reg;
> +};
> +/********************************************
> + * Register Access
> + *******************************************/
> +#define REG_NONE_ACCESS (0)
> +#define REG_RD_ACCESS (1 << 0)
> +#define REG_WR_ACCESS (1 << 1)
> +
> +static const struct aw_reg_data g_aw9610x_reg_access[] = {
Ehh... so we are at basics of C. Data structures do not go to headers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-05 10:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 9:11 [PATCH V2 0/5] Add support for Awinic SAR sensor wangshuaijie
2024-06-05 9:11 ` [PATCH V2 1/5] dt-bindings: input: Add YAML to Awinic sar sensor wangshuaijie
2024-06-05 10:20 ` Krzysztof Kozlowski
2024-07-12 9:47 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 2/5] Add universal interface for the aw_sar driver wangshuaijie
2024-06-05 9:11 ` [PATCH V2 3/5] Add aw9610x series related interfaces to " wangshuaijie
2024-06-05 10:22 ` Krzysztof Kozlowski [this message]
2024-07-12 9:50 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 4/5] Add aw963xx " wangshuaijie
2024-06-05 10:29 ` Krzysztof Kozlowski
2024-07-12 9:48 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 5/5] Add support for Awinic sar sensor wangshuaijie
2024-06-05 10:33 ` Krzysztof Kozlowski
2024-07-12 9:48 ` wangshuaijie
2024-06-05 12:09 ` kernel test robot
2024-06-06 18:32 ` kernel test robot
2024-06-08 2:22 ` kernel test robot
2024-06-06 3:04 ` [PATCH V2 0/5] Add support for Awinic SAR sensor Jeff LaBundy
2024-07-12 9:49 ` wangshuaijie
2024-07-12 12:02 ` Krzysztof Kozlowski
2024-07-25 12:48 ` wangshuaijie
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=4d8b7fe5-a566-49f7-8924-3c310af2f7cd@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=kangjiajun@awinic.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liweilei@awinic.com \
--cc=robh@kernel.org \
--cc=wangshuaijie@awinic.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).