All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Linus Walleij" <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"Ryan Chen" <ryan_chen@aspeedtech.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Joel Stanley" <joel@jms.id.au>,
	linux-aspeed@lists.ozlabs.org,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/8] pinctrl: aspeed: Preparation for AST2600
Date: Thu, 04 Jul 2019 10:28:45 +1000	[thread overview]
Message-ID: <022b6528-7ab3-449f-807d-d711b6d2db51@www.fastmail.com> (raw)
In-Reply-To: <CACRpkdaxiFR3ezt4FzhRxpqc4DYYjsbBeysPUaaQH+_QgYjudw@mail.gmail.com>



On Wed, 3 Jul 2019, at 18:40, Linus Walleij wrote:
> Hi Andrew,
> 
> On Fri, Jun 28, 2019 at 4:39 AM Andrew Jeffery <andrew@aj.id.au> wrote:
> >
> > Hello!
> >
> > The ASPEED AST2600 is in the pipeline, and we have enough information to start
> > preparing to upstream support for it. This series lays some ground work;
> > splitting the bindings and dicing the implementation up a little further to
> > facilitate differences between the 2600 and previous SoC generations.
> >
> > v2 addresses Rob's comments on the bindings conversion patches. v1 can be found
> > here:
> 
> I have applied this series, I had to strip some changes of the header
> because it was based on some SPDX cleanups upstream but no
> big deal I think. Check the result please.

Thanks. Have you pushed the branch yet? I just fetched your pinctrl tree
and can't see the patches.

Andrew

WARNING: multiple messages have this Message-ID (diff)
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Linus Walleij" <linus.walleij@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Ryan Chen <ryan_chen@aspeedtech.com>,
	linux-aspeed@lists.ozlabs.org,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/8] pinctrl: aspeed: Preparation for AST2600
Date: Thu, 04 Jul 2019 10:28:45 +1000	[thread overview]
Message-ID: <022b6528-7ab3-449f-807d-d711b6d2db51@www.fastmail.com> (raw)
In-Reply-To: <CACRpkdaxiFR3ezt4FzhRxpqc4DYYjsbBeysPUaaQH+_QgYjudw@mail.gmail.com>



On Wed, 3 Jul 2019, at 18:40, Linus Walleij wrote:
> Hi Andrew,
> 
> On Fri, Jun 28, 2019 at 4:39 AM Andrew Jeffery <andrew@aj.id.au> wrote:
> >
> > Hello!
> >
> > The ASPEED AST2600 is in the pipeline, and we have enough information to start
> > preparing to upstream support for it. This series lays some ground work;
> > splitting the bindings and dicing the implementation up a little further to
> > facilitate differences between the 2600 and previous SoC generations.
> >
> > v2 addresses Rob's comments on the bindings conversion patches. v1 can be found
> > here:
> 
> I have applied this series, I had to strip some changes of the header
> because it was based on some SPDX cleanups upstream but no
> big deal I think. Check the result please.

Thanks. Have you pushed the branch yet? I just fetched your pinctrl tree
and can't see the patches.

Andrew

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-07-04  0:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  2:38 [PATCH v2 0/8] pinctrl: aspeed: Preparation for AST2600 Andrew Jeffery
2019-06-28  2:38 ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 1/8] dt-bindings: pinctrl: aspeed: Split bindings document in two Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 2/8] dt-bindings: pinctrl: aspeed: Convert AST2400 bindings to json-schema Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28 15:46   ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28  2:38 ` [PATCH v2 3/8] dt-bindings: pinctrl: aspeed: Convert AST2500 " Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28 15:46   ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28 15:46     ` Rob Herring
2019-06-28  2:38 ` [PATCH v2 4/8] MAINTAINERS: Add entry for ASPEED pinctrl drivers Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 5/8] pinctrl: aspeed: Correct comment that is no longer true Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 6/8] pinctrl: aspeed: Clarify comment about strapping W1C Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 7/8] pinctrl: aspeed: Split out pinmux from general pinctrl Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-06-28  2:38 ` [PATCH v2 8/8] pinctrl: aspeed: Add implementation-related documentation Andrew Jeffery
2019-06-28  2:38   ` Andrew Jeffery
2019-07-03  8:40 ` [PATCH v2 0/8] pinctrl: aspeed: Preparation for AST2600 Linus Walleij
2019-07-03  8:40   ` Linus Walleij
2019-07-03  8:40   ` Linus Walleij
2019-07-03  8:40   ` Linus Walleij
2019-07-04  0:28   ` Andrew Jeffery [this message]
2019-07-04  0:28     ` Andrew Jeffery
2019-07-04  0:28     ` Andrew Jeffery
2019-07-04  0:28     ` Andrew Jeffery

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=022b6528-7ab3-449f-807d-d711b6d2db51@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=ryan_chen@aspeedtech.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.