From: Joel Stanley <joel@jms.id.au>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Zev Weiss <zweiss@equinix.com>
Subject: Re: [PATCH 1/2] pinctrl: aspeed: Enable pass-through on GPIOE1 and GPIOE3 free
Date: Fri, 25 Feb 2022 04:49:43 +0000 [thread overview]
Message-ID: <CACPK8XdsoL9_aTJL2KV9KD-djtiLRsJnHqWzL6gTWOMKRkjKOw@mail.gmail.com> (raw)
In-Reply-To: <7d792cb4-9eaf-cbdc-d39c-72217d5ebcf8@linux.intel.com>
On Thu, 24 Feb 2022 at 21:03, Bills, Jason M
<jason.m.bills@linux.intel.com> wrote:
>
> >
> > Jason, you should send the patch to the upstream lists (use
> > get_maintainers.pl) for review.
> Sorry for the delay. I found the right lists with get_maintainers.pl.
> Should I send these patches to the upstream lists as they are, or do
> they need to be tweaked?
You've got some review comments from Andrew and Zev that you should
address. I suggest replying to them, and adding the pinctrl list on
cc. Then when you post v2 you can send them to the upstream lists.
If you'd prefer to just send a v2 to the upstream lists to restart the
discussion you could do that too. Your call.
Cheers,
Joel
next prev parent reply other threads:[~2022-02-25 4:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 19:59 [PATCH 1/2] pinctrl: aspeed: Enable pass-through on GPIOE1 and GPIOE3 free Bills, Jason M
2022-02-02 22:49 ` Andrew Jeffery
2022-02-02 23:14 ` Zev Weiss
2022-02-07 6:45 ` Joel Stanley
2022-02-24 21:03 ` Bills, Jason M
2022-02-25 4:49 ` Joel Stanley [this message]
2022-02-25 15:22 ` Bills, Jason M
2022-02-28 0:04 ` 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=CACPK8XdsoL9_aTJL2KV9KD-djtiLRsJnHqWzL6gTWOMKRkjKOw@mail.gmail.com \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=jason.m.bills@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=zweiss@equinix.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.