All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Michal Simek <michal.simek@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function
Date: Mon, 1 Jun 2015 15:01:25 +0200	[thread overview]
Message-ID: <CACRpkdbpW6i2SNz254gt+T8TPw=gBzB68dQ2TmVNbwc41dT=1Q@mail.gmail.com> (raw)
In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu>

On Wed, May 20, 2015 at 4:23 PM, Sören Brinkmann
<soren.brinkmann@xilinx.com> wrote:

> For the series:
> Reviewed-by: Sören Brinkmann <soren.brinkmann@xilinx.com>

Ah that is Sören's Review tag.

> It may be a good ides to add
>   Fixes: add958cee967 "pinctrl: Add driver for Zynq"
> (I suspect that bug is there from the beginning) and ask Linus to
> consider this for stable.

I added it but still merging for -next at this point. No need to
rush this fix since it's been around so long.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Michal Simek <michal.simek@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function
Date: Mon, 1 Jun 2015 15:01:25 +0200	[thread overview]
Message-ID: <CACRpkdbpW6i2SNz254gt+T8TPw=gBzB68dQ2TmVNbwc41dT=1Q@mail.gmail.com> (raw)
In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu>

On Wed, May 20, 2015 at 4:23 PM, Sören Brinkmann
<soren.brinkmann@xilinx.com> wrote:

> For the series:
> Reviewed-by: Sören Brinkmann <soren.brinkmann@xilinx.com>

Ah that is Sören's Review tag.

> It may be a good ides to add
>   Fixes: add958cee967 "pinctrl: Add driver for Zynq"
> (I suspect that bug is there from the beginning) and ask Linus to
> consider this for stable.

I added it but still merging for -next at this point. No need to
rush this fix since it's been around so long.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function
Date: Mon, 1 Jun 2015 15:01:25 +0200	[thread overview]
Message-ID: <CACRpkdbpW6i2SNz254gt+T8TPw=gBzB68dQ2TmVNbwc41dT=1Q@mail.gmail.com> (raw)
In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu>

On Wed, May 20, 2015 at 4:23 PM, S?ren Brinkmann
<soren.brinkmann@xilinx.com> wrote:

> For the series:
> Reviewed-by: S?ren Brinkmann <soren.brinkmann@xilinx.com>

Ah that is S?ren's Review tag.

> It may be a good ides to add
>   Fixes: add958cee967 "pinctrl: Add driver for Zynq"
> (I suspect that bug is there from the beginning) and ask Linus to
> consider this for stable.

I added it but still merging for -next at this point. No need to
rush this fix since it's been around so long.

Yours,
Linus Walleij

  parent reply	other threads:[~2015-06-01 13:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  8:42 [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function Masahiro Yamada
2015-05-20  8:42 ` Masahiro Yamada
2015-05-20  8:42 ` [RESEND PATCH 1/2] pinctrl: zynq: fix DEFINE_ZYNQ_PINMUX_FUNCTION_MUX macro Masahiro Yamada
2015-05-20  8:42   ` Masahiro Yamada
2015-06-01 12:44   ` Linus Walleij
2015-06-01 12:44     ` Linus Walleij
2015-06-01 12:44     ` Linus Walleij
2015-05-20  8:42 ` [RESEND PATCH 2/2] pinctrl: zynq: fix offset address for {SD0,SD1}_WP_CD_SEL Masahiro Yamada
2015-05-20  8:42   ` [RESEND PATCH 2/2] pinctrl: zynq: fix offset address for {SD0, SD1}_WP_CD_SEL Masahiro Yamada
2015-06-01 12:44   ` [RESEND PATCH 2/2] pinctrl: zynq: fix offset address for {SD0,SD1}_WP_CD_SEL Linus Walleij
2015-06-01 12:44     ` [RESEND PATCH 2/2] pinctrl: zynq: fix offset address for {SD0, SD1}_WP_CD_SEL Linus Walleij
2015-06-01 12:44     ` [RESEND PATCH 2/2] pinctrl: zynq: fix offset address for {SD0,SD1}_WP_CD_SEL Linus Walleij
2015-05-20 14:23 ` [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function Sören Brinkmann
2015-05-20 14:23   ` Sören Brinkmann
2015-05-20 14:23   ` Sören Brinkmann
2015-05-21 14:31   ` Masahiro Yamada
2015-05-21 14:31     ` Masahiro Yamada
2015-05-21 14:31     ` Masahiro Yamada
2015-06-01 13:01   ` Linus Walleij [this message]
2015-06-01 13:01     ` Linus Walleij
2015-06-01 13:01     ` Linus Walleij

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='CACRpkdbpW6i2SNz254gt+T8TPw=gBzB68dQ2TmVNbwc41dT=1Q@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=yamada.masahiro@socionext.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 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.