Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752682AbbFVQK5 (ORCPT ); Mon, 22 Jun 2015 12:10:57 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:33800 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751667AbbFVQKt (ORCPT ); Mon, 22 Jun 2015 12:10:49 -0400 Date: Mon, 22 Jun 2015 17:10:44 +0100 From: Richard Fitzgerald To: Mark Brown Cc: gregkh@linuxfoundation.org, patches@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] regmap: debugfs: Allow writes to cache state settings Message-ID: <20150622161044.GA29071@opensource.wolfsonmicro.com> References: <1434987034-17673-1-git-send-email-rf@opensource.wolfsonmicro.com> <1434987034-17673-2-git-send-email-rf@opensource.wolfsonmicro.com> <20150622154915.GV14071@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150622154915.GV14071@sirena.org.uk> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1244 Lines: 33 On Mon, Jun 22, 2015 at 04:49:15PM +0100, Mark Brown wrote: > On Mon, Jun 22, 2015 at 04:30:34PM +0100, Richard Fitzgerald wrote: > > This looks basically good but: > > > +static ssize_t regmap_bool_read_file(struct file *file, > > + char __user *user_buf, > > + size_t count, loff_t *ppos, > > + bool value) > > +{ > > + char buf[2]; > > + > > + buf[0] = value ? 'Y' : 'N'; > > + buf[1] = '\n'; > > + return simple_read_from_buffer(user_buf, count, ppos, buf, sizeof(buf)); > > +} > > > +static ssize_t regmap_bool_write_file(struct file *file, > > + const char __user *user_buf, > > + size_t count, loff_t *ppos, > > + bool *value) > > +{ > > Can we not export read/write_file_bool() instead? For the read this > seems to be an almost cut'n'paste with slight differences that look > like taste changes. For the write path we can just stash the current > value in the calling functions instead of cut'n'pasting the code. They assume that file->private_data points at the actual bool, and it doesn't here, which means temporarily patching it around the call. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/