From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
"James Hogan" <jhogan@kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>,
"Paul Burton" <paulburton@kernel.org>
Subject: Re: linux-next: manual merge of the gpio tree with the mips tree
Date: Mon, 13 Jan 2020 22:45:03 +1100 [thread overview]
Message-ID: <20200113224503.1e1e3235@canb.auug.org.au> (raw)
In-Reply-To: <20200113091237.GA1748@aptenodytes>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hi Paul,
On Mon, 13 Jan 2020 10:12:37 +0100 Paul Kocialkowski <paul.kocialkowski@bootlin.com> wrote:
>
> Thanks for the fix. We might want to keep the list ordered though, with
> "xylon" listed after "xunlong" and before "yna".
>
> > description: Xilinx
> > "^xunlong,.*":
> > description: Shenzhen Xunlong Software CO.,Limited
> > + "^yna,.*":
> > + description: YSH & ATIL
> > + "^xylon,.*":
> > + description: Xylon
>
> So reversing the two blocks above.
>
> What do you think?
Absolutely. I have changed my resolution for tomorrow. What really
matters, though is what we end up with in Linus' tree.
Thanks for checking.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-13 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 4:51 linux-next: manual merge of the gpio tree with the mips tree Stephen Rothwell
2020-01-13 9:12 ` Paul Kocialkowski
2020-01-13 11:45 ` Stephen Rothwell [this message]
2020-01-29 22:37 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2016-05-12 4:17 Stephen Rothwell
2016-05-12 13:35 ` Linus Walleij
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=20200113224503.1e1e3235@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jhogan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=zhouyanjie@wanyeetech.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