From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Esben Haabendal
<esben.haabendal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Subject: Re: Backport of spi-fsl-spi bugfix to 3.14.y
Date: Sun, 25 Jan 2015 14:07:23 -0800 [thread overview]
Message-ID: <20150125220723.GD29924@kroah.com> (raw)
In-Reply-To: <20150125201254.GX21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Sun, Jan 25, 2015 at 08:12:54PM +0000, Mark Brown wrote:
> On Sun, Jan 25, 2015 at 09:38:53AM -0800, Greg Kroah-Hartman wrote:
> > On Fri, Jan 23, 2015 at 12:45:29PM +0000, Mark Brown wrote:
>
> > > So, I now see this has actually been merged into stable without getting
> > > to the bottom of why it's helping anything... this is a bit worrying
> > > since it's adding new functionality and not really a bug fix. It'd have
> > > been good to at least get a followup here.
>
> > Do you want me to revert something from the stable tree? If so, has it
> > also been reverted upstream?
>
> The patch just isn't an obvious -stable patch - it's adding new
> functionality, not fixing a bug, and I was surprised to discover it had
> been added as a result. It's fine as new functionality and therefore
> hasn't been reverted upstream.
>
> We can probably leave it there, though if this is OK that's a bit of a
> change, but if this new functionality is a good fix then we're probably
> leaving other systems unfixed which isn't good, I would be very much
> happier if we understood what had changed here. If new functionality is
> OK there's a probably a bunch of other changes we should be pulling
> back.
New functionality shouldn't be added, but sometimes things slip in due
to the volume of patches and how people word-smith changelog entries :(
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Esben Haabendal <esben.haabendal@gmail.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, Stefan Roese <sr@denx.de>
Subject: Re: Backport of spi-fsl-spi bugfix to 3.14.y
Date: Sun, 25 Jan 2015 14:07:23 -0800 [thread overview]
Message-ID: <20150125220723.GD29924@kroah.com> (raw)
In-Reply-To: <20150125201254.GX21293@sirena.org.uk>
On Sun, Jan 25, 2015 at 08:12:54PM +0000, Mark Brown wrote:
> On Sun, Jan 25, 2015 at 09:38:53AM -0800, Greg Kroah-Hartman wrote:
> > On Fri, Jan 23, 2015 at 12:45:29PM +0000, Mark Brown wrote:
>
> > > So, I now see this has actually been merged into stable without getting
> > > to the bottom of why it's helping anything... this is a bit worrying
> > > since it's adding new functionality and not really a bug fix. It'd have
> > > been good to at least get a followup here.
>
> > Do you want me to revert something from the stable tree? If so, has it
> > also been reverted upstream?
>
> The patch just isn't an obvious -stable patch - it's adding new
> functionality, not fixing a bug, and I was surprised to discover it had
> been added as a result. It's fine as new functionality and therefore
> hasn't been reverted upstream.
>
> We can probably leave it there, though if this is OK that's a bit of a
> change, but if this new functionality is a good fix then we're probably
> leaving other systems unfixed which isn't good, I would be very much
> happier if we understood what had changed here. If new functionality is
> OK there's a probably a bunch of other changes we should be pulling
> back.
New functionality shouldn't be added, but sometimes things slip in due
to the volume of patches and how people word-smith changelog entries :(
greg k-h
next prev parent reply other threads:[~2015-01-25 22:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 15:42 Backport of spi-fsl-spi bugfix to 3.14.y Esben Haabendal
2015-01-05 15:42 ` Esben Haabendal
2015-01-05 15:48 ` Mark Brown
2015-01-06 21:15 ` Esben Haabendal
[not found] ` <CAOR3GqUBWyfUvNG-8JiPVkis6b_25Eq_REtcp=kLN3CUoqsG6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-23 12:45 ` Mark Brown
2015-01-23 12:45 ` Mark Brown
[not found] ` <20150123124529.GU21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-01-25 17:38 ` Greg Kroah-Hartman
2015-01-25 17:38 ` Greg Kroah-Hartman
2015-01-25 20:12 ` Mark Brown
[not found] ` <20150125201254.GX21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-01-25 22:07 ` Greg Kroah-Hartman [this message]
2015-01-25 22:07 ` Greg Kroah-Hartman
2015-02-04 9:03 ` Esben Haabendal
2015-02-05 14:33 ` Mark Brown
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=20150125220723.GD29924@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=esben.haabendal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sr-ynQEQJNshbs@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.