public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Pull request for MIPS-specific driver bits
Date: Tue, 1 Dec 2009 17:46:12 +0000	[thread overview]
Message-ID: <20091201174612.GA18799@linux-mips.org> (raw)

Below three patches for MIPS-specific drivers that I can't get anybody
else interested in merging.  To be accurate drivers/video/gbefb.c is
shared with SGI's x86-based Visual Workstation which is more or less
the same system architecture than the MIPS-based O2.

Please pull them from

    git://ftp.linux-mips.org/pub/scm/upstream-linus.git upstream

This would be the last MIPS-related patches I have pending for 2.6.32.

Thanks,

  Ralf

commit 3063ae66aa9024d92d613e41264b590838a56a92
Author: Maxime Bizon <mbizon@freebox.fr>
Date:   Wed Nov 4 14:11:15 2009 +0100

    MIPS: BCM63xx: Fix serial driver compile breakage.
    
    The driver missed an API change.
    
    Signed-off-by: Maxime Bizon <mbizon@freebox.fr>
    Cc: linux-mips@linux-mips.org
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

commit 6a830e0a79a530328fb24aca0dc1682db9e163e0
Author: Julia Lawall <julia@diku.dk>
Date:   Sun Aug 9 11:42:32 2009 +0200

    VIDEO: Correct use of request_region/request_mem_region
    
    request_region should be used with release_region, not request_mem_region.
    
    Geert Uytterhoeven pointed out that in the case of drivers/video/gbefb.c,
    the problem is actually the other way around; request_mem_region should be
    used instead of request_region.
    
    The semantic patch that finds/fixes this problem is as follows:
    (http://coccinelle.lip6.fr/)
    
    // <smpl>
    @r1@
    expression start;
    @@
    
    request_region(start,...)
    
    @b1@
    expression r1.start;
    @@
    
    request_mem_region(start,...)
    
    @depends on !b1@
    expression r1.start;
    expression E;
    @@
    
    - release_mem_region
    + release_region
      (start,E)
    // </smpl>
    
    Signed-off-by: Julia Lawall <julia@diku.dk>
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

commit 5a635a204e649d997b9f67c62d6e7d0e615d2619
Author: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date:   Thu Sep 3 22:59:01 2009 +0900

    SPI: spi_txx9: Fix bit rate calculation
    
    TXx9 SPI bit rate is calculated by:
            fBR = (spi-baseclk) / (n + 1)
    Fix calculation of min_speed_hz, max_speed_hz and n.
    
    Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

 drivers/serial/bcm63xx_uart.c |    4 ++--
 drivers/spi/spi_txx9.c        |   13 ++++++-------
 drivers/video/gbefb.c         |    2 +-
 3 files changed, 9 insertions(+), 10 deletions(-)

             reply	other threads:[~2009-12-01 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 17:46 Ralf Baechle [this message]
2009-12-02 23:46 ` Pull request for MIPS-specific driver bits Linus Torvalds
2009-12-03  0:01   ` Ralf Baechle

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=20091201174612.GA18799@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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