Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751945AbcDOFo4 (ORCPT ); Fri, 15 Apr 2016 01:44:56 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:48613 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751145AbcDOFoz (ORCPT ); Fri, 15 Apr 2016 01:44:55 -0400 Date: Thu, 14 Apr 2016 22:44:52 -0700 From: Darren Hart To: Jonathan Woithe Cc: Micha?? K??pie?? , platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fujitsu-laptop: Support radio LED Message-ID: <20160415054417.GA127188@f23x64.localdomain> References: <1458127687-25366-1-git-send-email-kernel@kempniu.pl> <20160318120418.GA29889@marvin.atrad.com.au> <20160322133051.GA3379@eudyptula.hq.kempniu.pl> <20160324113513.GA5129@marvin.atrad.com.au> <20160410023020.GA27081@dvhart-mobl5.amr.corp.intel.com> <20160410105258.GA2922@marvin.atrad.com.au> <20160412123634.GA8195@marvin.atrad.com.au> <20160415044255.GE3232@f23x64.localdomain> <20160415053333.GP12741@marvin.atrad.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160415053333.GP12741@marvin.atrad.com.au> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2055 Lines: 44 On Fri, Apr 15, 2016 at 03:03:33PM +0930, Jonathan Woithe wrote: > On Thu, Apr 14, 2016 at 09:42:55PM -0700, Darren Hart wrote: > > > Signed-off-by: Michał Kępień > > > > Jonathan, please check your character set, a few mangled characters here > > which I have to fix up to use. UTF-8 seems to work reliably. > > Sorry about that. Normally UTF-8 stuff goes through just fine so I'm not sure > what happened there. I'll admit I've never touched the default mutt charset > settings though so perhaps there's a corner case that's not being handled. > I'll look into it. > > > > Acked-by: Jonathan Woithe > > > > > > Michał hasn't indicated that a revised patch is in the works so I'm fine if > > > you proceed with the one below. I've selected the relevant parts of his > > > preamble for inclusion in the commit message, but feel free to edit further > > > to your taste. > > > > Yeah, tough call, some guess work involved here, and where we are > > uncertain, we should document it. I don't think we need to include bits > > about uncertain future plans or speculation on how things might be done. > > Keep it to what this patch does and any qualifiers a developer should be > > aware of. > > I agree. Also note that a followup post from the original submitter > indicated they were happy to go with what I proposed. > > > I've made a couple cosmetic changes and queued to for-next. Please review > > and let me know if you have any concerns. > > Sure. Pardon my ignorance of such things, but what is the most > straight-forward way to review the queued commit (preferrably without > cloning an entire kernel git repo)? You can see the tree in the MAINTAINERS file, but I suppose that doesn't make it obvious how to browse it. You can do that via the git web interface on infradead. The direct link to this patch is here: http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git/commit/34b5199d2b69f9be731233af2425c53cc7ff995b -- Darren Hart Intel Open Source Technology Center