Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-mips@linux-mips.org
Cc: ralf@linux-mips.org, blogic@openwrt.org, cernekee@gmail.com,
	jogo@openwrt.org, jaedon.shin@gmail.com, jfraser@broadcom.com,
	pgynther@google.com, dragan.stancevic@gmail.com
Subject: Re: [PATCH 0/6] MIPS: BMIPS: Random fixes for BMIPS5000/5200
Date: Sun, 3 Apr 2016 11:39:15 -0700	[thread overview]
Message-ID: <57016353.7070500@gmail.com> (raw)
In-Reply-To: <56F9DBF3.5060309@gmail.com>

Le 28/03/2016 18:35, Florian Fainelli a écrit :
> Le 29/01/2016 21:17, Florian Fainelli a écrit :
>> Hi all,
>>
>> This patch series contains a bunch of fixes for the BMIPS5000 processor class.
>>
>> The first 4 patches are addressing some functional and cosmetic issues, while
>> the last 2 patches fix the existing code to support BMIPS5200 processors.
>>
>> Kevin, Jon, Jonas, please review!
>>
>> These were tested on BCM7425 and BCM7435.
>>
>> BMIPS5200 SMP patches will be submitted on top of this patch series
> 
> Ralf, can you queue these patches for 4.6? Thank you!

Ping? Any chance we can get these patches in 4.6?

> 
>>
>> Florian Fainelli (6):
>>   MIPS: BMIPS: BMIPS5000 has I cache filing from D cache
>>   MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier
>>   BMIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache
>>   MIPS: BMIPS: Add cpu-feature-overrides.h
>>   MIPS: BMIPS: Pretty print BMIPS5200 processor name
>>   MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200
>>
>>  .../include/asm/mach-bmips/cpu-feature-overrides.h |   14 ++++++++++++++
>>  arch/mips/kernel/bmips_vec.S                       |    9 +++++++--
>>  arch/mips/kernel/cpu-probe.c                       |    5 ++++-
>>  arch/mips/mm/c-r4k.c                               |   13 +++++++++++--
>>  4 files changed, 36 insertions(+), 5 deletions(-)
>>  create mode 100644 arch/mips/include/asm/mach-bmips/cpu-feature-overrides.h
>>
> 
> 


-- 
Florian

      reply	other threads:[~2016-04-03 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  5:17 [PATCH 0/6] MIPS: BMIPS: Random fixes for BMIPS5000/5200 Florian Fainelli
2016-01-30  5:17 ` [PATCH 1/6] MIPS: BMIPS: BMIPS5000 has I cache filing from D cache Florian Fainelli
2016-01-30  5:17 ` [PATCH 2/6] MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier Florian Fainelli
2016-01-30  5:17 ` [PATCH 3/6] BMIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache Florian Fainelli
2016-01-30  5:17 ` [PATCH 4/6] MIPS: BMIPS: Add cpu-feature-overrides.h Florian Fainelli
2016-01-30  5:17 ` [PATCH 5/6] MIPS: BMIPS: Pretty print BMIPS5200 processor name Florian Fainelli
2016-01-30  5:17 ` [PATCH 6/6] MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200 Florian Fainelli
2016-03-29  1:35 ` [PATCH 0/6] MIPS: BMIPS: Random fixes for BMIPS5000/5200 Florian Fainelli
2016-04-03 18:39   ` Florian Fainelli [this message]

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=57016353.7070500@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=blogic@openwrt.org \
    --cc=cernekee@gmail.com \
    --cc=dragan.stancevic@gmail.com \
    --cc=jaedon.shin@gmail.com \
    --cc=jfraser@broadcom.com \
    --cc=jogo@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pgynther@google.com \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox