From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH v2 2/6] mfd: Add ChromeOS EC implementation Date: Tue, 12 Feb 2013 19:35:46 -0800 Message-ID: <1360726546.2220.6.camel@joe-AO722> References: <1360723347-28701-1-git-send-email-sjg@chromium.org> <1360723347-28701-3-git-send-email-sjg@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1360723347-28701-3-git-send-email-sjg@chromium.org> Sender: linux-doc-owner@vger.kernel.org To: Simon Glass Cc: LKML , Samuel Ortiz , Che-Liang Chiou , Jonathan Kliegman , Luigi Semenzato , Olof Johansson , Vincent Palatin , Grant Likely , Rob Herring , Rob Landley , devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org List-Id: devicetree@vger.kernel.org On Tue, 2013-02-12 at 18:42 -0800, Simon Glass wrote: > This is the base EC implementation, which provides a high level > interface to the EC for use by the rest of the kernel. The actual > communcations is dealt with by a separate protocol driver which > registers itself with this interface. trivial logging message comments... > diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c [] > +struct cros_ec_device *cros_ec_alloc(const char *name) > +{ > + struct cros_ec_device *ec_dev; > + > + ec_dev = kzalloc(sizeof(*ec_dev), GFP_KERNEL); > + if (ec_dev == NULL) { > + dev_err(ec_dev->dev, "cannot allocate\n"); allocation OOM messages aren't useful as there's a standard one on all allocs without __GFP_WARN > +int cros_ec_register(struct cros_ec_device *ec_dev) > +{ [] > + ec_dev->din = kmalloc(ec_dev->din_size, GFP_KERNEL); > + if (!ec_dev->din) { > + err = -ENOMEM; > + dev_err(dev, "cannot allocate din\n"); etc... > + if (err) { > + dev_err(dev, "failed to add mfd devices"); missing terminating newline