LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Michal Simek <michal.simek@xilinx.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Michal Simek <monstr@monstr.eu>,
	Steffen Trumtrar <s.trumtrar@pengutronix.de>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Rob Herring <robherring2@gmail.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID
Date: Wed, 23 May 2018 12:26:54 +0200	[thread overview]
Message-ID: <fa24761b-1025-53bc-7706-9c67c0112cdf@xilinx.com> (raw)
In-Reply-To: <CACRpkdb6pN=XYgWN7rPBGDwgpMjNLhgxVk_=QRTrHb=DZuU-xQ@mail.gmail.com>

On 23.5.2018 11:44, Linus Walleij wrote:
> On Tue, May 15, 2018 at 3:26 PM, Michal Simek <michal.simek@xilinx.com> wrote:
> 
>> Have you done any decision about this patch?
> 
> Yeah I applied the patch. It's a bit of "choose the lesser evil" approach
> but what can I do...

Thanks,
Michal

  reply	other threads:[~2018-05-23 10:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 13:55 [PATCH] gpio: zynq: Setup chip->base based on alias ID Michal Simek
2018-04-26 13:08 ` Linus Walleij
2018-04-26 13:35   ` Michal Simek
2018-05-02 10:10     ` Linus Walleij
2018-05-02 10:15       ` Michal Simek
2018-05-02 13:01         ` Linus Walleij
2018-05-02 13:41           ` Michal Simek
2018-05-02 13:56             ` Linus Walleij
2018-05-02 14:19               ` Michal Simek
2018-05-15 13:26                 ` Michal Simek
2018-05-23  9:44                   ` Linus Walleij
2018-05-23 10:26                     ` Michal Simek [this message]
2018-05-23  9:42                 ` Linus Walleij
2018-05-23 10:17                   ` Michal Simek

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=fa24761b-1025-53bc-7706-9c67c0112cdf@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=robherring2@gmail.com \
    --cc=s.trumtrar@pengutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).