All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: John Crispin <john@phrozen.org>
Cc: "André Draszik" <git@andred.net>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
	"Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: ralink: fix mt7628 alternative functions names
Date: Fri, 10 Feb 2017 17:06:31 +0000	[thread overview]
Message-ID: <20170210170631.GD24226@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <17885154-71f7-2d1e-7046-757e092de508@phrozen.org>

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

On Fri, Feb 10, 2017 at 10:12:24AM +0100, John Crispin wrote:
> 
> 
> On 10/02/2017 10:06, André Draszik wrote:
> > They're all referenced as utif in the datasheet, not util.
> > 
> > Fixes: 53263a1c6852 ("MIPS: ralink: add mt7628an support")
> > Fixes: 2b436a351803 ("MIPS: ralink: add MT7628 EPHY LEDs pinmux support")
> > 
> > Signed-off-by: André Draszik <git@andred.net>
> 
> I was under the impression that I had sent this patch already, maybe it
> got lost somewhere along the line

Yep:
https://patchwork.linux-mips.org/patch/14899/
Applied as commit 58181a117d353427127a2e7afc7cf1ab44759828

Though without Fixes or stable tag, so if that matters we'll have to
explicitly request backports.

Cheers
James

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2017-02-10 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10  9:06 [PATCH] MIPS: ralink: fix mt7628 alternative functions names André Draszik
2017-02-10  9:12 ` John Crispin
2017-02-10 17:06   ` James Hogan [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=20170210170631.GD24226@jhogan-linux.le.imgtec.org \
    --to=james.hogan@imgtec.com \
    --cc=git@andred.net \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.