Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [3.14 FIX][PATCH] MIPS: BCM47XX: Check all (32) GPIOs when looking for a pin
Date: Wed, 19 Mar 2014 09:47:42 +0100	[thread overview]
Message-ID: <20140319084742.GR4365@linux-mips.org> (raw)
In-Reply-To: <CACna6rwzB_eD+SfTo6gc20ec9O4-0+6R5ZajgEMuqx6fzHnumg@mail.gmail.com>

On Wed, Mar 19, 2014 at 07:43:17AM +0100, Rafał Miłecki wrote:
> Date:   Wed, 19 Mar 2014 07:43:17 +0100
> From: Rafał Miłecki <zajec5@gmail.com>
> To: Hauke Mehrtens <hauke@hauke-m.de>
> Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>, Ralf Baechle
>  <ralf@linux-mips.org>
> Subject: Re: [3.14 FIX][PATCH] MIPS: BCM47XX: Check all (32) GPIOs when
>  looking for a pin
> Content-Type: text/plain; charset=UTF-8
> 
> 2014-03-14 22:30 GMT+01:00 Hauke Mehrtens <hauke@hauke-m.de>:
> > On 02/13/2014 05:48 PM, Rafał Miłecki wrote:
> >> Broadcom boards support 32 GPIOs and NVRAM may have entires for higher
> >> ones too. Example:
> >> gpio23=wombo_reset
> >>
> >> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> >
> > Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
> 
> Ralf: could you get it for 3.15 at least, please?

Funny, I applied your patch minutes before seeing this email.

  Ralf

      reply	other threads:[~2014-03-19  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 16:48 [3.14 FIX][PATCH] MIPS: BCM47XX: Check all (32) GPIOs when looking for a pin Rafał Miłecki
2014-02-28  6:27 ` Rafał Miłecki
2014-03-13 15:22   ` Rafał Miłecki
2014-03-14 21:30 ` Hauke Mehrtens
2014-03-19  6:43   ` Rafał Miłecki
2014-03-19  8:47     ` Ralf Baechle [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=20140319084742.GR4365@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-mips@linux-mips.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