Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Shane McDonald <mcdonald.shane@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] msp71xx: resolve compilation problem in msp_setup.c
Date: Mon, 18 Aug 2008 22:28:12 +0100	[thread overview]
Message-ID: <20080818212812.GA28692@linux-mips.org> (raw)
In-Reply-To: <E1KUmPs-0005uZ-Du@localhost>

On Sun, Aug 17, 2008 at 11:51:48AM -0600, Shane McDonald wrote:
> From: Shane McDonald <mcdonald.shane@gmail.com>
> Date: Sun, 17 Aug 2008 11:51:48 -0600
> To: linux-mips@linux-mips.org, ralf@linux-mips.org
> Subject: [MIPS] msp71xx: resolve compilation problem in msp_setup.c
> 
> The msp71xx_defconfig has never compiled in a kernel release.  This is
> because the file msp_setup.c relies on some definitions from the PMCMSP
> GPIO driver, which has not yet been accepted into the kernel.
> This patch checks for the existence of the PMCMSP GPIO driver;
> if it doesn't exist, no GPIO functions are referenced.
> 
> This patch will continue to work after the GPIO driver has been accepted,
> so no changes will be necessary when that happens.

Has the driver actually been submitted?  In its current form I doubt it'll
be accepted since there is now a generic GPIO framework so there should
be no more new drivers/char/ GPIO drivers.

  Ralf

  reply	other threads:[~2008-08-18 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 17:51 [MIPS] msp71xx: resolve compilation problem in msp_setup.c Shane McDonald
2008-08-18 21:28 ` Ralf Baechle [this message]
2008-08-18 23:11   ` Patrick Glass
2008-08-18 23:11     ` Patrick Glass
2008-08-18 23:22     ` Shane McDonald
2008-08-19  9:17     ` 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=20080818212812.GA28692@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mcdonald.shane@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