From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function Date: Mon, 1 Jun 2015 15:01:25 +0200 Message-ID: References: <1432111351-21336-1-git-send-email-yamada.masahiro@socionext.com> <20150520142358.GS31550@xsjsorenbubuntu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-ob0-f172.google.com ([209.85.214.172]:33321 "EHLO mail-ob0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752387AbbFANB0 convert rfc822-to-8bit (ORCPT ); Mon, 1 Jun 2015 09:01:26 -0400 Received: by obbnx5 with SMTP id nx5so102230585obb.0 for ; Mon, 01 Jun 2015 06:01:25 -0700 (PDT) In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu> Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: =?UTF-8?Q?S=C3=B6ren_Brinkmann?= Cc: Masahiro Yamada , "linux-gpio@vger.kernel.org" , Michal Simek , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" On Wed, May 20, 2015 at 4:23 PM, S=C3=B6ren Brinkmann wrote: > For the series: > Reviewed-by: S=C3=B6ren Brinkmann Ah that is S=C3=B6ren'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" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753071AbbFANBf (ORCPT ); Mon, 1 Jun 2015 09:01:35 -0400 Received: from mail-oi0-f51.google.com ([209.85.218.51]:35832 "EHLO mail-oi0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752619AbbFANB0 convert rfc822-to-8bit (ORCPT ); Mon, 1 Jun 2015 09:01:26 -0400 MIME-Version: 1.0 In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu> References: <1432111351-21336-1-git-send-email-yamada.masahiro@socionext.com> <20150520142358.GS31550@xsjsorenbubuntu> Date: Mon, 1 Jun 2015 15:01:25 +0200 Message-ID: Subject: Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function From: Linus Walleij To: =?UTF-8?Q?S=C3=B6ren_Brinkmann?= Cc: Masahiro Yamada , "linux-gpio@vger.kernel.org" , Michal Simek , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 20, 2015 at 4:23 PM, Sören Brinkmann wrote: > For the series: > Reviewed-by: Sören Brinkmann 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: linus.walleij@linaro.org (Linus Walleij) Date: Mon, 1 Jun 2015 15:01:25 +0200 Subject: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function In-Reply-To: <20150520142358.GS31550@xsjsorenbubuntu> References: <1432111351-21336-1-git-send-email-yamada.masahiro@socionext.com> <20150520142358.GS31550@xsjsorenbubuntu> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, May 20, 2015 at 4:23 PM, S?ren Brinkmann wrote: > For the series: > Reviewed-by: S?ren Brinkmann 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