From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH v2 2/3] fpga manager: framework core Date: Sat, 6 Dec 2014 14:55:33 +0100 Message-ID: <20141206135533.GA19672@amd> References: <1414007405-32186-1-git-send-email-atull@opensource.altera.com> <1414007405-32186-3-git-send-email-atull@opensource.altera.com> <20141024105200.GA20775@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Grant Likely Cc: atull , Pantelis Antoniou , Greg Kroah-Hartman , Jason Gunthorpe , "H. Peter Anvin" , Michal Simek , Michal Simek , Randy Dunlap , linux-kernel , "devicetree@vger.kernel.org" , Rob Herring , Ira Snyder , "linux-doc@vger.kernel.org" , Mark Brown , philip@balister.org, rubini , Steffen Trumtrar , Jason , kyle.teske@ni.com, Nicolas Pitre , Felipe Balbi , Mauro Carvalho Chehab , David Brown List-Id: devicetree@vger.kernel.org Hi! > > I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a > > while I am a bonehead and forget the '-n' and spend a few minutes > > wondering why this thing that worked last week suddenly rejects all > > commands. I'm just trying to make my user interface a bit user-friendly. > > > > I will take out the '\n' stripping and update the documentation. I didn't > > realize this would be controversial. > > Don't. You're doing the right thing by scrubbing your input. Requiring > 'echo -n' is just stupid when it is so easy to make work easily. 'foo\nbar\n' is unusual but valid filename in linux. It is bad idea to echo filenames into files in the first place... and arbitrarily disallowing certain filenames is not helping. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html