public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gregungerer@westnet.com.au>
To: Paul Bolle <pebolle@tiscali.nl>, Jiri Kosina <trivial@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] m68k: Fix typo 'COFNIG_MBAR'
Date: Mon, 29 Sep 2014 10:10:40 +1000	[thread overview]
Message-ID: <5428A380.9030408@westnet.com.au> (raw)
In-Reply-To: <1411753216.7866.65.camel@x220>

Hi Paul,

On 27/09/14 03:40, Paul Bolle wrote:
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Untested!

Thanks. I have applied this to the m68knommu git tree (since
that is where we tend to keep all ColdFire fixes).


> Geert, PASR is obviously unused. Is it needed?

Not at the moment. It will be if/when we implement better error
handling for external master errors.

Regards
Greg

 
>  arch/m68k/include/asm/m54xxpci.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/m68k/include/asm/m54xxpci.h b/arch/m68k/include/asm/m54xxpci.h
> index 6fbf54f72f2e..4687f5aa3741 100644
> --- a/arch/m68k/include/asm/m54xxpci.h
> +++ b/arch/m68k/include/asm/m54xxpci.h
> @@ -72,7 +72,7 @@
>  #define	PCIRFWPR	(CONFIG_MBAR + 0x84d4)	/* RX FIFO write pointer */
>  
>  #define	PACR		(CONFIG_MBAR + 0xc00)	/* PCI arbiter control */
> -#define	PASR		(COFNIG_MBAR + 0xc04)	/* PCI arbiter status */
> +#define	PASR		(CONFIG_MBAR + 0xc04)	/* PCI arbiter status */
>  
>  /*
>   *	Definitions for the Global status and control register.
> 


      reply	other threads:[~2014-09-29  0:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 17:40 [PATCH] [TRIVIAL] m68k: Fix typo 'COFNIG_MBAR' Paul Bolle
2014-09-29  0:10 ` Greg Ungerer [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=5428A380.9030408@westnet.com.au \
    --to=gregungerer@westnet.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox