From: Borislav Petkov <bp@alien8.de>
To: Manish Narani <MNARANI@xilinx.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
Michal Simek <michals@xilinx.com>,
"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"amit.kucheria@linaro.org" <amit.kucheria@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [v7,4/7] edac: synopsys: Add macro defines for ZynqMP DDRC
Date: Mon, 24 Sep 2018 12:41:52 +0200 [thread overview]
Message-ID: <20180924104152.GD20187@zn.tnic> (raw)
On Mon, Sep 24, 2018 at 10:29:44AM +0000, Manish Narani wrote:
> > Is there some significance here or can they all be vertically aligned?
> Should I increase the alignment of the existing macros in the 'code
> formatting' patches? New macros will need an increased indentation.
If there is no significance to that different alignment, you probably
should so that it is all on one column.
WARNING: multiple messages have this Message-ID (diff)
From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 4/7] edac: synopsys: Add macro defines for ZynqMP DDRC
Date: Mon, 24 Sep 2018 12:41:52 +0200 [thread overview]
Message-ID: <20180924104152.GD20187@zn.tnic> (raw)
In-Reply-To: <DM6PR02MB5227D961C992C3BB6A4421B7C1170@DM6PR02MB5227.namprd02.prod.outlook.com>
On Mon, Sep 24, 2018 at 10:29:44AM +0000, Manish Narani wrote:
> > Is there some significance here or can they all be vertically aligned?
> Should I increase the alignment of the existing macros in the 'code
> formatting' patches? New macros will need an increased indentation.
If there is no significance to that different alignment, you probably
should so that it is all on one column.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Manish Narani <MNARANI@xilinx.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
Michal Simek <michals@xilinx.com>,
"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"amit.kucheria@linaro.org" <amit.kucheria@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 4/7] edac: synopsys: Add macro defines for ZynqMP DDRC
Date: Mon, 24 Sep 2018 12:41:52 +0200 [thread overview]
Message-ID: <20180924104152.GD20187@zn.tnic> (raw)
In-Reply-To: <DM6PR02MB5227D961C992C3BB6A4421B7C1170@DM6PR02MB5227.namprd02.prod.outlook.com>
On Mon, Sep 24, 2018 at 10:29:44AM +0000, Manish Narani wrote:
> > Is there some significance here or can they all be vertically aligned?
> Should I increase the alignment of the existing macros in the 'code
> formatting' patches? New macros will need an increased indentation.
If there is no significance to that different alignment, you probably
should so that it is all on one column.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next reply other threads:[~2018-09-24 10:41 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 10:41 Borislav Petkov [this message]
2018-09-24 10:41 ` [PATCH v7 4/7] edac: synopsys: Add macro defines for ZynqMP DDRC Borislav Petkov
2018-09-24 10:41 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2018-09-24 10:29 [v7,4/7] " Manish Narani
2018-09-24 10:29 ` [PATCH v7 4/7] " Manish Narani
2018-09-24 10:29 ` Manish Narani
2018-09-24 10:20 [v7,5/7] edac: synopsys: Add EDAC ECC support " Manish Narani
2018-09-24 10:20 ` [PATCH v7 5/7] " Manish Narani
2018-09-24 10:20 ` Manish Narani
2018-09-24 10:16 [v7,2/7] edac: synps: Add platform specific structures for ddrc controller Manish Narani
2018-09-24 10:16 ` [PATCH v7 2/7] " Manish Narani
2018-09-24 10:16 ` Manish Narani
2018-09-24 10:07 [v7,2/7] " Manish Narani
2018-09-24 10:07 ` [PATCH v7 2/7] " Manish Narani
2018-09-24 10:07 ` Manish Narani
2018-09-24 9:53 [v7,7/7] edac: synopsys: Add Error Injection support for ZynqMP DDRC Borislav Petkov
2018-09-24 9:53 ` [PATCH v7 7/7] " Borislav Petkov
2018-09-24 9:53 ` Borislav Petkov
2018-09-24 9:22 [v7,4/7] edac: synopsys: Add macro defines " Borislav Petkov
2018-09-24 9:22 ` [PATCH v7 4/7] " Borislav Petkov
2018-09-24 9:22 ` Borislav Petkov
2018-09-21 12:57 [v7,6/7] arm64: zynqmp: Add DDRC node Borislav Petkov
2018-09-21 12:57 ` [PATCH v7 6/7] " Borislav Petkov
2018-09-21 12:57 ` Borislav Petkov
2018-09-21 12:56 [v7,5/7] edac: synopsys: Add EDAC ECC support for ZynqMP DDRC Borislav Petkov
2018-09-21 12:56 ` [PATCH v7 5/7] " Borislav Petkov
2018-09-21 12:56 ` Borislav Petkov
2018-09-21 9:15 [v7,2/7] edac: synps: Add platform specific structures for ddrc controller Borislav Petkov
2018-09-21 9:15 ` [PATCH v7 2/7] " Borislav Petkov
2018-09-21 9:15 ` Borislav Petkov
2018-09-21 9:07 [v7,2/7] " Borislav Petkov
2018-09-21 9:07 ` [PATCH v7 2/7] " Borislav Petkov
2018-09-21 9:07 ` Borislav Petkov
2018-09-19 13:33 [v7,2/7] " Manish Narani
2018-09-19 13:33 ` [PATCH v7 2/7] " Manish Narani
2018-09-19 13:33 ` Manish Narani
2018-09-19 11:15 [v7,2/7] " Borislav Petkov
2018-09-19 11:15 ` [PATCH v7 2/7] " Borislav Petkov
2018-09-19 11:15 ` Borislav Petkov
2018-09-19 5:14 [v7,2/7] " Manish Narani
2018-09-19 5:14 ` [PATCH v7 2/7] " Manish Narani
2018-09-19 5:14 ` Manish Narani
2018-09-19 5:08 [v7,1/7] edac: synopsys: Fix code comments and naming convention Manish Narani
2018-09-19 5:08 ` [PATCH v7 1/7] " Manish Narani
2018-09-19 5:08 ` Manish Narani
2018-09-18 7:55 [v7,2/7] edac: synps: Add platform specific structures for ddrc controller Borislav Petkov
2018-09-18 7:55 ` [PATCH v7 2/7] " Borislav Petkov
2018-09-18 7:55 ` Borislav Petkov
2018-09-18 7:55 ` Borislav Petkov
2018-09-18 7:53 [v7,1/7] edac: synopsys: Fix code comments and naming convention Borislav Petkov
2018-09-18 7:53 ` [PATCH v7 1/7] " Borislav Petkov
2018-09-18 7:53 ` Borislav Petkov
2018-09-17 14:25 [v7,7/7] edac: synopsys: Add Error Injection support for ZynqMP DDRC Manish Narani
2018-09-17 14:25 ` [PATCH v7 7/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 [v7,6/7] arm64: zynqmp: Add DDRC node Manish Narani
2018-09-17 14:25 ` [PATCH v7 6/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 [v7,5/7] edac: synopsys: Add EDAC ECC support for ZynqMP DDRC Manish Narani
2018-09-17 14:25 ` [PATCH v7 5/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 [v7,4/7] edac: synopsys: Add macro defines " Manish Narani
2018-09-17 14:25 ` [PATCH v7 4/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 [v7,3/7] dt: bindings: Document ZynqMP DDRC in Synopsys documentation Manish Narani
2018-09-17 14:25 ` [PATCH v7 3/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 [v7,2/7] edac: synps: Add platform specific structures for ddrc controller Manish Narani
2018-09-17 14:25 ` [PATCH v7 2/7] " Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:25 ` Manish Narani
2018-09-17 14:24 [v7,1/7] edac: synopsys: Fix code comments and naming convention Manish Narani
2018-09-17 14:24 ` [PATCH v7 1/7] " Manish Narani
2018-09-17 14:24 ` Manish Narani
2018-09-17 14:24 ` Manish Narani
2018-09-17 14:24 [PATCH v7 0/7] EDAC: Enhancements to Synopsys EDAC driver Manish Narani
2018-09-17 14:24 ` Manish Narani
2018-09-17 14:24 ` Manish Narani
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=20180924104152.GD20187@zn.tnic \
--to=bp@alien8.de \
--cc=MNARANI@xilinx.com \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=michals@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.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 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.