From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: Introduce generic BAT_ATTR_* macros
Date: Sat, 16 Oct 2010 04:11:06 +0200 [thread overview]
Message-ID: <201010160411.08260.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <1286922125-18097-4-git-send-email-linus.luessing@web.de>
[-- Attachment #1: Type: Text/Plain, Size: 1478 bytes --]
Linus Lüssing wrote:
> This makes exposing bat_priv's atomic_ts storing boolean or uint values
> possible with only two additional lines of code in the future. It also
> further reduces the amount of duplicate code in bat_sysfs.c.
>
> Signed-off-by: Linus Lüssing <linus.luessing@web.de>
> ---
Please fix the checkpatch problems first:
WARNING: please, no space before tabs
#47: FILE: batman-adv/bat_sysfs.c:55:
+ssize_t show_##_name(struct kobject *kobj, struct attribute *attr, ^I\$
WARNING: storage class should be at the beginning of the declaration
#101: FILE: batman-adv/bat_sysfs.c:139:
+inline static ssize_t __store_bool_attr(char *buff, size_t count,
ERROR: inline keyword should sit between storage class and type
#101: FILE: batman-adv/bat_sysfs.c:139:
+inline static ssize_t __store_bool_attr(char *buff, size_t count,
WARNING: storage class should be at the beginning of the declaration
#126: FILE: batman-adv/bat_sysfs.c:191:
+inline static ssize_t __store_uint_attr(char *buff, size_t count,
ERROR: inline keyword should sit between storage class and type
#126: FILE: batman-adv/bat_sysfs.c:191:
+inline static ssize_t __store_uint_attr(char *buff, size_t count,
total: 2 errors, 3 warnings, 0 checks, 241 lines checked
0003-batman-adv-Introduce-generic-BAT_ATTR_-macros.patch has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-10-16 2:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 22:22 [B.A.T.M.A.N.] Simplifying sysfs code Linus Lüssing
2010-10-12 22:22 ` [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: Unify sysfs file names with their bat_priv atomics Linus Lüssing
2010-10-12 22:22 ` [B.A.T.M.A.N.] [PATCH 2/4] batman-adv: Wrapper functions for sysfs storing Linus Lüssing
2010-10-12 22:22 ` [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: Introduce generic BAT_ATTR_* macros Linus Lüssing
2010-10-16 2:11 ` Sven Eckelmann [this message]
2010-10-17 17:31 ` [B.A.T.M.A.N.] [PATCHv2 " Linus Lüssing
2010-10-12 22:22 ` [B.A.T.M.A.N.] [PATCH 4/4] batman-adv: Ommit storing struct device in sysfs functions Linus Lüssing
2010-10-13 11:33 ` [B.A.T.M.A.N.] [PATCH 5/4] batman-adv: Make hop_penalty configurable via sysfs Linus Lüssing
2010-10-15 16:01 ` Marek Lindner
2010-10-18 10:01 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Adding sysfs API documentation for hop_penalty Linus Lüssing
2010-10-18 10:11 ` Marek Lindner
2010-10-18 21:44 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Adding sysfs ABI " Linus Lüssing
2010-10-23 1:46 ` Marek Lindner
2010-10-23 1:45 ` [B.A.T.M.A.N.] [PATCH 5/4] batman-adv: Make hop_penalty configurable via sysfs Marek Lindner
2010-10-15 16:06 ` [B.A.T.M.A.N.] Simplifying sysfs code Marek Lindner
2010-10-18 10:06 ` Marek Lindner
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=201010160411.08260.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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