linux-kernel - Re: [PATCH 1/2] coresight: replicator: Add Qualcomm CoreSight Replicator driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1431016761.8171.79.camel@x220>
Date:	Thu, 07 May 2015 18:39:21 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Ivan T. Ivanov" <ivan.ivanov@...aro.org>
Cc:	Mathieu Poirier <mathieu.poirier@...aro.org>,
	Kumar Gala <galak@...eaurora.org>,
	Pratik Patel <pratikp@...eaurora.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 1/2] coresight: replicator: Add Qualcomm CoreSight
 Replicator driver

On Thu, 2015-05-07 at 17:46 +0300, Ivan T. Ivanov wrote:
> Thank you. I am going to fallow approach taken by Mathieu in [1].
> Is this OK with you?

I'm OK with anything that is coherent (ie, anything better than built-in
only code cross-dressing as modular code). I think Mathieu's approach
clears that bar. (Please note that macros like module_amba_driver() are
basically just a pet peeve.)

And, at the end of the day, what matters is what the maintainer of this
code accepts. I'm not the maintainer here.

Thanks,


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/