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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 70F84CA9EC5 for ; Wed, 30 Oct 2019 16:02:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3A129208E3 for ; Wed, 30 Oct 2019 16:02:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=netronome-com.20150623.gappssmtp.com header.i=@netronome-com.20150623.gappssmtp.com header.b="Kwx+ej5r" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727422AbfJ3QC5 (ORCPT ); Wed, 30 Oct 2019 12:02:57 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:45447 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726596AbfJ3QC5 (ORCPT ); Wed, 30 Oct 2019 12:02:57 -0400 Received: by mail-pg1-f193.google.com with SMTP id r1so1744937pgj.12 for ; Wed, 30 Oct 2019 09:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=VoUHDBkMmd0HSBoZsz/ANMDge7dtZlxy+cPZi/mFFJY=; b=Kwx+ej5rUUdH05bGpgZpyIashKuG83SmcQrnDsm+0lkzjNj+a/z/2AYj955t9lDk5J wM9pSqdj/pjkJ/9fqeY9vJA4+RepNJgc0XpETFOyHjZO784yLooJUr0S5S0azRi1xVCK 2npjQfJ7X7m5p+lT7hDQY7pxd7Hua4CD2zHNc1ilftvalB1GC9rxo0gSKg0jCBdKBn72 OTh7uP80F4rVatHRyeUPyZLMukEb62PvTqWNWARYt5PlbtxBy047yW0RiVnUHkzfbCml 0A9j5I62awVLtlW+2u7tjzfUrlwNFmqhQFW354VvHwHwdWDOJT7OZ7P21G5h7AJcmnFp jKTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=VoUHDBkMmd0HSBoZsz/ANMDge7dtZlxy+cPZi/mFFJY=; b=SnHiF+TuR3vWv8lpcPQ6tYEHmlnAYJldun9trOsj5ElzpfeXHAXl9TsC3TeOofOgHU shq/VPRKCpacXonml7p8JMjj/G+XKt1z6ZUbkprr+JBQCpjPzWLQQ2LIj6waMs5HMFPL Znlz+1EXc+ROwQzds171eb0/gglU1vfv0lTpq4VqRGdmyxELs0Wm5CttzthqhsBtf5dt oL7U6pp4l7FT3ueigLjyfD9Bz0TzhGtvyRC9d4fqdMxW0/zsZDiM3ppe2FE+lExFjCIP XQI51HyCSRKWztodYvFzazQm53XDIbHj1iNSTp+K5z7oxZ/LEhxyFBtj2erdcilnjbZy HCzg== X-Gm-Message-State: APjAAAVy+0gQTYKUvVStK4ouy2koiQpB0QGKbH3AjfWf9YSdSa8bOyoy Hsp7Hlf7+pw/rt6j2wvEzpVAsg== X-Google-Smtp-Source: APXvYqwKh2sNDkMWVEr8EZeiQYcDxBUIyGbXfa1wOACGtQkqflx1gjxVl6QWK3rDAjeFaaWgdy3PMg== X-Received: by 2002:a17:90a:db47:: with SMTP id u7mr14678517pjx.3.1572451376075; Wed, 30 Oct 2019 09:02:56 -0700 (PDT) Received: from cakuba.hsd1.ca.comcast.net (c-73-202-202-92.hsd1.ca.comcast.net. [73.202.202.92]) by smtp.gmail.com with ESMTPSA id 3sm366984pfh.45.2019.10.30.09.02.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Oct 2019 09:02:55 -0700 (PDT) Date: Wed, 30 Oct 2019 09:02:52 -0700 From: Jakub Kicinski To: Jonathan Corbet Cc: davem@davemloft.net, netdev@vger.kernel.org, oss-drivers@netronome.com, linux-doc@vger.kernel.org, Simon Horman Subject: Re: [PATCH net] Documentation: netdev-FAQ: make all questions into headings Message-ID: <20191030090252.7eedec35@cakuba.hsd1.ca.comcast.net> In-Reply-To: <20191030024430.719c73be@lwn.net> References: <20191029171215.6861-1-jakub.kicinski@netronome.com> <20191030024430.719c73be@lwn.net> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, 30 Oct 2019 02:44:30 -0600, Jonathan Corbet wrote: > On Tue, 29 Oct 2019 10:12:15 -0700 > Jakub Kicinski wrote: > > -Q: I see a network patch and I think it should be backported to stable. > > ------------------------------------------------------------------------ > > -Q: Should I request it via stable@vger.kernel.org like the references in > > -the kernel's Documentation/process/stable-kernel-rules.rst file say? > > +Q: I see a network patch and I think it should be backported to stable. Should I request it via stable@vger.kernel.org like the references in the kernel's Documentation/process/stable-kernel-rules.rst file say? > > +------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > I don't think that making these massive heading lines actually improves the > experience - for readers of either the plain-text or formatted docs. If > you really want to create headings, the heading here should be "Stable > backports" or some such with the question appearing below. But do the > questions really need to be headings? I agree that this is suboptimal. I couldn't come up with a better way of handling this. I think consistently formatting all questions in one way and answers in another make the document far easier to interpret. I had hard time follow the current formatting: https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html#q-i-have-created-a-network-patch-and-i-think-it-should-be-backported-to-stable Is there a more appropriate form of emphasis we could use here? Even if we add independent headings questions should remain emphasised _somehow_ I reckon..