linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Colin Ian King <colin.king@canonical.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pinctrl: core: Handling pinmux and pinconf separately
Date: Thu, 11 Mar 2021 15:39:27 +0100	[thread overview]
Message-ID: <CACRpkdazxVZCwLK6sJb7-hqhzuWs-HJ=2yiVr-UX4+AoEAWAZw@mail.gmail.com> (raw)
In-Reply-To: <f6cd3eb3-c8ce-9b40-e5dc-82b6748d4084@xilinx.com>

On Thu, Mar 11, 2021 at 12:28 PM Michal Simek <michal.simek@xilinx.com> wrote:

> > It will take me 2 hours to re-run the analysis, but from eyeballing the
> > code I think the assignments will fix this.
>
> would be good if you can rerun it and get back to us on this.
> I will wait if something else will pop up and then will send v2 with
> this that Linus can apply this one instead.

Just send an incremental patch, that reflects the issues found
in a nice way in the development history.

Yours,
Linus Walleij

  parent reply	other threads:[~2021-03-11 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 10:57 pinctrl: core: Handling pinmux and pinconf separately Colin Ian King
2021-03-11 11:16 ` Michal Simek
2021-03-11 11:24   ` Colin Ian King
2021-03-11 11:28     ` Michal Simek
2021-03-11 14:03       ` Colin Ian King
2021-03-11 14:39       ` Linus Walleij [this message]
2021-03-12 12:45     ` Andy Shevchenko
2021-03-12 12:49       ` Colin Ian King

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='CACRpkdazxVZCwLK6sJb7-hqhzuWs-HJ=2yiVr-UX4+AoEAWAZw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=colin.king@canonical.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.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;
as well as URLs for NNTP newsgroup(s).