From: Dan Carpenter <dan.carpenter@oracle.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Frans Klaver <fransklaver@gmail.com>,
linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] mtd: maps: sa1100-flash: potential NULL dereference
Date: Sat, 16 Jul 2016 12:00:41 +0300 [thread overview]
Message-ID: <20160716090041.GC32247@mwanda> (raw)
In-Reply-To: <20160716003209.GC76613@google.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Frans Klaver <fransklaver@gmail.com>,
linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] mtd: maps: sa1100-flash: potential NULL dereference
Date: Sat, 16 Jul 2016 09:00:41 +0000 [thread overview]
Message-ID: <20160716090041.GC32247@mwanda> (raw)
In-Reply-To: <20160716003209.GC76613@google.com>
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
next prev parent reply other threads:[~2016-07-16 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 11:06 [patch] mtd: maps: sa1100-flash: potential NULL dereference Dan Carpenter
2016-07-15 11:06 ` Dan Carpenter
2016-07-16 0:32 ` Brian Norris
2016-07-16 0:32 ` Brian Norris
2016-07-16 0:48 ` Greg Kroah-Hartman
2016-07-16 0:48 ` Greg Kroah-Hartman
2016-07-16 1:46 ` Brian Norris
2016-07-16 1:46 ` Brian Norris
2016-07-16 9:00 ` Dan Carpenter [this message]
2016-07-16 9:00 ` Dan Carpenter
2016-07-17 3:54 ` Brian Norris
2016-07-17 3:54 ` Brian Norris
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=20160716090041.GC32247@mwanda \
--to=dan.carpenter@oracle.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fransklaver@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@vger.kernel.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.