From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69D09C3F2D1 for ; Thu, 5 Mar 2020 18:57:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3B64F206E2 for ; Thu, 5 Mar 2020 18:57:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="fv4ovc1q" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726179AbgCES5W (ORCPT ); Thu, 5 Mar 2020 13:57:22 -0500 Received: from bombadil.infradead.org ([198.137.202.133]:46106 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725974AbgCES5W (ORCPT ); Thu, 5 Mar 2020 13:57:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To: Subject:Sender:Reply-To:Content-ID:Content-Description; bh=90PsQ4qn7idAg8om1vCTJLAiN2890cMWcnF24IYxgDc=; b=fv4ovc1qV3pLntR67dk++yLkwb 45T5B35drA0dkhLce4yh+6gnblKeOzfzPIOSFOI2LpFQoAMokFXJ7oaInLrFjbLbKEN85r/gaNC6J u4400F13PHMp2TsMjbyzThatMdz84ck0N7RKtRL0JLbmulrJr5fRZEKEzXL2amqsxbf+VZEywOxZd KqizugKOXlJKSb6+jdP5+1+JCQIqECD2lmV6DcZCa6Dl1P+tB40aGSwAyBjmZaBUPLcn97ZSed22o GmRzUPwQp6JGn49ZWxnkOJQxk6cHa4Td9AmO3aaUXw23mB5IRlHLbLwUC7i8tMpKe1QDxSI6CT04S 1WG/5TSQ==; Received: from [2601:1c0:6280:3f0:897c:6038:c71d:ecac] by bombadil.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1j9vgP-0007Kr-Ks; Thu, 05 Mar 2020 18:57:21 +0000 Subject: Re: [v5] Documentation: bootconfig: Update boot configuration documentation To: Markus Elfring , linux-doc@vger.kernel.org Cc: Masami Hiramatsu , Steven Rostedt , Jonathan Corbet , linux-kernel@vger.kernel.org References: <158339065180.26602.26457588086834858.stgit@devnote2> <158339066140.26602.7533299987467005089.stgit@devnote2> <3fb124a6-07d2-7a40-8981-07561aeb3c1e@web.de> <29c599ef-991d-a253-9f27-5999fb55b228@web.de> <997f73af-dc6c-bc8b-12ba-69270ee4b95d@infradead.org> From: Randy Dunlap Message-ID: Date: Thu, 5 Mar 2020 10:57:20 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/5/20 10:43 AM, Markus Elfring wrote: >>>> If you would (could) be more concrete (or discrete) in your suggestions, >>>> I would be glad to comment on them. >>> >>> Does this view indicate any communication difficulties? >> >> Probably. >> >>> Which of the possibly unanswered issues do you find not concrete enough so far? >> >> e.g.: >>>>> Will the clarification become more constructive for remaining challenges? > > Do you expect that known open issues need to be repeated for each patch revision? Ideally not, but not very much is ideal. IOW, it is sometimes required (if one cares enough; sometimes one just gives up). > How do you think about the desired tracking of bug reports > also for this software? I expect that more users will begin to use it and report problems as they see fit. They can use mailing list(s) and/or bugzilla.kernel.org. I'm not terribly concerned about it. Masami seems to be responsive. thanks. -- ~Randy