All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	spi-devel-general@lists.sourceforge.net,
	Grant Likely <grant.likely@secretlab.ca>,
	Maxime Bizon <mbizon@freebox.fr>,
	Kevin Cernekee <cernekee@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 3.7] spi/bcm63xx: fix transfer bits_per_words check
Date: Mon, 26 Nov 2012 14:11:20 +0100	[thread overview]
Message-ID: <2175243.jGVtISFVra@flexo> (raw)
In-Reply-To: <CAOiHx=nXRgF6YCLJ+U77boeuuWb6TOdT9dg=cie=Gruz6eS6xQ@mail.gmail.com>

On Saturday 24 November 2012 19:19:34 Jonas Gorski wrote:
> On 24 November 2012 19:01, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Sat, Nov 24, 2012 at 06:53:10PM +0100, Jonas Gorski wrote:
> >> On 24 November 2012 18:28, Mark Brown
> >
> >> > This is now done by the SPI core, there's no need for individual drivers
> >> > to do this.
> >
> >> So that will go to stable kernels, too?
> >
> > No, I hadn't sent it there.  I'd really expect that anyone using a
> > release kernel would've noticed this if there were a problem, it's
> > pretty obvious when it goes wrong, and I tend to be extremely
> > conservative with changes to stable kernels especially framework ones.
> 
> Well, I noticed this particular problem on a 3.6 kernel (3.6.7 to be
> exact), so by that definition at least one noticed, unless I don't
> count as anyone ;-). So, how can I make this driver less broken for
> release kernels? I somewhat doubt the framework change will be picked
> up by release kernel maintainers.

Considering it is a simple one-liner in spi-bcm63xx and that you don't want to
propagate a framework-level change back to -stable (which makes sense), don't
you want to pick that one?

At least two other users told me about this bug in private conversations.
--
Florian

  reply	other threads:[~2012-11-26 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 13:44 [PATCH 3.7] spi/bcm63xx: fix transfer bits_per_words check Jonas Gorski
     [not found] ` <1353764690-5961-1-git-send-email-jonas.gorski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-24 15:02   ` Florian Fainelli
     [not found] ` <20121124172801.GC4719@opensource.wolfsonmicro.com>
     [not found]   ` <20121124172801.GC4719-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-24 17:53     ` Jonas Gorski
     [not found]       ` <20121124180151.GJ4719@opensource.wolfsonmicro.com>
     [not found]         ` <20121124180151.GJ4719-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-24 18:19           ` Jonas Gorski
2012-11-26 13:11             ` Florian Fainelli [this message]
2012-11-26 13:23               ` 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=2175243.jGVtISFVra@flexo \
    --to=florian@openwrt.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cernekee@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jonas.gorski@gmail.com \
    --cc=mbizon@freebox.fr \
    --cc=spi-devel-general@lists.sourceforge.net \
    --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.