From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller
Date: Thu, 10 Apr 2014 11:21:44 +0200 [thread overview]
Message-ID: <20140410092144.GD29093@pd.tnic> (raw)
In-Reply-To: <534633C0.9090905@monstr.eu>
On Thu, Apr 10, 2014 at 08:01:36AM +0200, Michal Simek wrote:
> Just add it to Zynq maintainer fragment as we are doing for non
> zynq/xilinx drivers.
Yep, as a file pattern F:
> At least the is the first time when someone saying that only some
> functions should be documented.
I don't see the need to document simple functions which are *obvious*.
But if you want to do that, I'm not going to stop you so be my guest.
> I don't think this is good to do. When we remove this prefix entirely
> it is bigger chance that the same function name will be used by
> another driver. It is not a problem with linking but the same
> functions names will be listed in System.map which will complicate
> debugging.
Ok, fair enough. You probably still want to make them shorter, though,
so that your code doesn't have to be line-broken too much. For example,
since we only load a single edac driver per system, you can shorten the
prefix to "edac_" only.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Michal Simek <monstr@monstr.eu>
Cc: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>,
dougthompson@xmission.com, linux-edac@vger.kernel.org,
michal.simek@xilinx.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, rob@landley.net, sorenb@xilinx.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kpc528@gmail.com,
kalluripunnaiahchoudary@gmail.com, punnaia@xilinx.com
Subject: Re: [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller
Date: Thu, 10 Apr 2014 11:21:44 +0200 [thread overview]
Message-ID: <20140410092144.GD29093@pd.tnic> (raw)
In-Reply-To: <534633C0.9090905@monstr.eu>
On Thu, Apr 10, 2014 at 08:01:36AM +0200, Michal Simek wrote:
> Just add it to Zynq maintainer fragment as we are doing for non
> zynq/xilinx drivers.
Yep, as a file pattern F:
> At least the is the first time when someone saying that only some
> functions should be documented.
I don't see the need to document simple functions which are *obvious*.
But if you want to do that, I'm not going to stop you so be my guest.
> I don't think this is good to do. When we remove this prefix entirely
> it is bigger chance that the same function name will be used by
> another driver. It is not a problem with linking but the same
> functions names will be listed in System.map which will complicate
> debugging.
Ok, fair enough. You probably still want to make them shorter, though,
so that your code doesn't have to be line-broken too much. For example,
since we only load a single edac driver per system, you can shorten the
prefix to "edac_" only.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-04-10 9:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:23 [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller Punnaiah Choudary Kalluri
2014-03-17 5:23 ` Punnaiah Choudary Kalluri
2014-03-17 5:23 ` Punnaiah Choudary Kalluri
2014-04-03 15:00 ` Michal Simek
2014-04-03 15:00 ` Michal Simek
2014-04-08 20:40 ` Borislav Petkov
2014-04-08 20:40 ` Borislav Petkov
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 11:03 ` Borislav Petkov
2014-04-09 11:03 ` Borislav Petkov
2014-04-09 17:45 ` punnaiah choudary kalluri
2014-04-09 17:45 ` punnaiah choudary kalluri
2014-04-09 17:48 ` Borislav Petkov
2014-04-09 17:48 ` Borislav Petkov
2014-04-10 6:01 ` Michal Simek
2014-04-10 6:01 ` Michal Simek
2014-04-10 9:21 ` Borislav Petkov [this message]
2014-04-10 9:21 ` Borislav Petkov
2014-04-10 9:49 ` Michal Simek
2014-04-10 9:49 ` Michal Simek
2014-04-10 9:49 ` Michal Simek
2014-04-10 10:00 ` Borislav Petkov
2014-04-10 10:00 ` Borislav Petkov
2014-04-10 10:05 ` Borislav Petkov
2014-04-10 10:05 ` Borislav Petkov
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
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=20140410092144.GD29093@pd.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.