linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	Arend van Spriel <arend@broadcom.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless?] bcma: keep info about parallel flash presentence
Date: Fri, 10 Aug 2012 09:20:55 -0400	[thread overview]
Message-ID: <20120810132054.GA2229@tuxdriver.com> (raw)
In-Reply-To: <CACna6rxLe6PKqdfG7XVb4f7XH5nk_dKZX-sC1-KS19AManD1+Q@mail.gmail.com>

On Fri, Aug 10, 2012 at 02:25:48PM +0200, Rafał Miłecki wrote:
> 2012/8/10 Hauke Mehrtens <hauke@hauke-m.de>:
> > On 08/10/2012 11:32 AM, Rafał Miłecki wrote:
> >> 2012/8/10 Arend van Spriel <arend@broadcom.com>:
> >>> On 08/09/2012 10:38 PM, Rafał Miłecki wrote:
> >>>> This allows drivers to access flash conditionally and stop crashing some
> >>>> devices.
> >>>>
> >>>> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> >>>> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
> >>>> ---
> >>>> John: I suggest taking it for wirelesss, AKA fix
> >>>
> >>> Maybe you could mentioned devices and/or drivers crashes without this patch?
> >>
> >> Yes, sure! The problematic one for me is arch/mips/bcm47xx/nvram.c.
> >> Right now it assumes every BCMA board has pflash. I'll submit fix for
> >> mips tree when this patch hits it.
> >
> > Letting this patches get merged into the wireless tree and an other
> > patches which depends on this one into the mips tree will cause
> > problems, because the wireless tree only gets merged into the mips tree
> > indirectly round about the rc1 release in form of the rc1 release done
> > by Linus.
> >
> > The patch to arch/mips/bcm47xx/nvram.c will depend on this one and you
> > should submit them to the same tree.
> 
> I'm planning to wait until rc2 (or rc3 if needed). I know the dependency :)

Which rc2?  Because Ralf probably won't have it in his tree until
the 3.7-rc1 timeframe...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-08-10 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 20:38 [PATCH wireless?] bcma: keep info about parallel flash presentence Rafał Miłecki
2012-08-10  9:02 ` Arend van Spriel
2012-08-10  9:32   ` Rafał Miłecki
2012-08-10  9:32     ` Rafał Miłecki
2012-08-10 12:23     ` Hauke Mehrtens
2012-08-10 12:25       ` Rafał Miłecki
2012-08-10 13:20         ` John W. Linville [this message]
2012-08-10 13:36           ` Rafał Miłecki

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=20120810132054.GA2229@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).