All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC 5/7] Docs: Expectations for bug reporters and maintainers
Date: Thu, 18 Apr 2013 23:08:54 -0700	[thread overview]
Message-ID: <20130419060854.GA16563@kroah.com> (raw)
In-Reply-To: <20130417182328.GA7690@xanatos>

On Wed, Apr 17, 2013 at 11:23:28AM -0700, Sarah Sharp wrote:
> TLDR version: Yes, it would be nice if bug reporters could go up the
> hierarchy, but they don't have an easy way to know which subsystem
> maintainers to contact.  Perhaps a new line in MAINTAINERS for the
> subsystem maintainer would be helpful?

We have that already for a number of subsystems, look at the entry for
"USB SUBSYSTEM" for one such example, and there are 49 others in there
as well :)

Thanks for rewriting this document, it looks much better now.

greg k-h

  parent reply	other threads:[~2013-04-19  6:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 17:33 [RFC 0/7] Update REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 1/7] Trivial: docs: Remove six-space indentation in REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 2/7] Docs: Step-by-step directions for reporting bugs Sarah Sharp
2013-04-15 17:33 ` [RFC 3/7] Docs: Add "Gather info" section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 4/7] Docs: Add info on supported kernels " Sarah Sharp
2013-04-17  0:24   ` Rob Landley
2013-04-15 17:33 ` [RFC 5/7] Docs: Expectations for bug reporters and maintainers Sarah Sharp
2013-04-17  2:15   ` Rob Landley
2013-04-17 18:23     ` Sarah Sharp
2013-04-17 23:49       ` Rob Landley
2013-04-18 23:52         ` Sarah Sharp
2013-04-20  6:24           ` Rob Landley
2013-04-19  6:08       ` Greg KH [this message]
2013-05-01 15:26       ` Mark Brown
2013-04-15 17:33 ` [RFC 6/7] Docs: Add a tips section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 7/7] Docs: Move ref to Frohwalt Egerer to end of REPORTING-BUGS Sarah Sharp
2013-04-15 21:40 ` [RFC 0/7] Update REPORTING-BUGS Linus Torvalds
2013-04-16  1:47 ` Theodore Ts'o
2013-04-16 21:58   ` Sarah Sharp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130419060854.GA16563@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.