[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160716090041.GC32247@mwanda>
Date: Sat, 16 Jul 2016 12:00:41 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Brian Norris <computersforpeace@...il.com>
Cc: David Woodhouse <dwmw2@...radead.org>,
Frans Klaver <fransklaver@...il.com>,
linux-mtd@...ts.infradead.org, kernel-janitors@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch] mtd: maps: sa1100-flash: potential NULL dereference
I like the Fixes tag because it was my invention. :) It's a separate
thing from -stable.
It's nice for reviewing so you can see the original intent of the patch
you're fixing. Also it forces you to find the original authors and CC
them so hopefully they Ack the patch. The other thing is it lets you
collect data about which patches introduce bugs and how quickly they
get fixed. So for example, lwn.net recently had an article about bug
that are backported into the -stable tree.
regards,
dan carpenter
Powered by blists - more mailing lists