Re: [PATCH] Documentation: android: binderfs: add 'stats' mount option
On Wed, 8 Apr 2020 21:08:09 +0200
Christian Brauner wrote:
> On Wed, Apr 08, 2020 at 10:29:50AM -0700, Randy Dunlap wrote:
> > From: Randy Dunlap
> >
> > Add documentation of the binderfs 'stats' mount option.
> >
> > Description taken from the commit message.
> >
> > Fixes: f00834518ed3 ("binder: add a mount option to show global stats")
> > Signed-off-by: Randy Dunlap
> > Cc: Hridya Valsaraju
> > Cc: Christian Brauner
> > Cc: Christian Brauner
> > Cc: Greg Kroah-Hartman
> > Cc: de...@driverdev.osuosl.org
>
> Thanks!
> Acked-by: Christian Brauner
Applied, thanks.
jon
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] vme: Convert documentation to reStructuredText, move under driver APIs
On Fri, 21 Oct 2016 22:15:27 +0100 Martyn Welch wrote: > Perform a relatively simple conversion of vme_api.txt to reStructuredText > and move under driver-api, which seems the most logical place for this > documentation. Makes sense to me, applied to the docs tree. Now if only the VME stuff had proper kerneldoc comments in the source! :) Thanks, jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH v2 3/3] doc: add documentation for uio-hv-generic
On Mon, 17 Oct 2016 12:33:19 -0700 Stephen Hemminger wrote: > From: Stephen Hemminger > > Update UIO documentation to include basic information about > uio_hv_generic. I've applied this to the docs tree, thanks. jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] doc-rst: DocBook to reST migration of the uio-howto.tmpl
On Tue, 18 Oct 2016 17:52:57 +0200 Markus Heiser wrote: > this is the DocBook to reST migration of the uio-howto.tmpl as ordered by > Stephen Hemminger [1]. Markus, slow down just a little bit, please. Let me get docs-next going for 4.9 (will happen once I get LWN together for this week) and get Steve's patch applied. Then I'll be happy to see it reworked. When you do that, it should almost certainly be folded into the driver-api book. Thanks, jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf
On Wed, 6 Jan 2016 12:06:22 +0300 Dan Carpenter wrote: > It's not really necessary to CC linux-kernel. No one reads it. I have to take issue with this too; more of us read it than you might think. The fact that we're probably all crazy doesn't really figure into it. Think of linux-kernel as the blockchain of kernel development; it's a messy thing that takes a lot of resources to maintain (and keep up with), but when you need to see what happened (or is happening) it's invaluable. jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [patch v2] Documentation/SubmittingPatches: Reported-by tags and permission
On Wed, 29 Oct 2014 13:01:36 +0300 Dan Carpenter wrote: > The reported-by text says you have to ask for permission, but that > should only be if the bug was reported in private. These days the > standard is to always give reported-by credit or it's considered a bit > rude. > > Signed-off-by: Dan Carpenter Applied, thanks. jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [patch] Documentation/SubmittingPatches: Reported-by tags and permission
On Tue, 28 Oct 2014 12:58:27 -0400 Jason Cooper wrote: > At the risk of upsetting the apple cart, I'd prefer we downplay anything > that walks down the path of gamification (by focusing on credit). > > As best anyone has ever explained it to me, the Acked-by, Reviewed-by, > etc are there to impart information regarding a specific commit. In the > event that a commit is fingered in a bisect, you have a much better list > of names to Cc, instead of just the maintainer from MAINTAINERS and the > author from the top of the offending file. The author has often moved > on, and the maintainer may not have been around for the bugfix. As I understand it, having been in the room when these tags were developed and encouraged, was that credit was a big part of the initial motivation. We need more testers and bug reporters; this was a way to give them credit for the valuable work that they do. I still think that's important, for whatever that's worth. > I know Greg has spoken out against gamification before, and I also > understand the desire to encourage bug reporters. Perhaps I should just > suggest the following: > > """ > The Reported-by tag helps us maintain contact info for people with > intimate knowledge of a commit or a bug fix. Please seek the reporter's > permission before adding the tag to the commit. That said, if we > diligently credit our bug reporters, they will, hopefully, be inspired > to help us again in the future. > """ That addresses my concern, but loses the point of the initial patch: publicly reporting a bug can be seen as implicit permission to credit the reporter. Thanks, jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [patch] Documentation/SubmittingPatches: Reported-by tags and permission
On Fri, 14 Feb 2014 12:30:01 +0300 Dan Carpenter wrote: > -If this patch fixes a problem reported by somebody else, consider adding a > -Reported-by: tag to credit the reporter for their contribution. Please > -note that this tag should not be added without the reporter's permission, > -especially if the problem was not reported in a public forum. That said, > -if we diligently credit our bug reporters, they will, hopefully, be > -inspired to help us again in the future. > +The Reported-by tag is to give credit to people who find bugs and report > them. > +Please note that if the bug was reported in private, then ask for permission > +first before using the Reported-by tag. As the guy who wrote the original text, I think this is an improvement...but can we get a version that retains the motivation for crediting bug reporters in the first place? Thanks, jon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
