From: Krzysztof Kozlowski <krzk@kernel•org>
To: Linux Next Mailing List <linux-next@vger•kernel.org>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Include in next: krzk/linux-dt
Date: Mon, 20 Jun 2022 21:34:22 +0200 [thread overview]
Message-ID: <b2e86d7a-401d-f48f-2c02-e8253885ab51@kernel.org> (raw)
Hi Stephen,
Please kindly include in linux-next my new tree:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-dt.git
branch: for-next
branch for pending-fixes: fixes
I tend to create a lot of cleanup patches for Devicetree bindings and
DTS files. Since some time I started to pick them up to my Samsung SoC
tree and send to arm-soc (Arnd, Olof). This way I will split it from
Samsung SoC work to independent cleanup stuff.
The tree will be sent with pull requests to arm-soc (Arnd, Olof) or to
DT (Rob Herring).
Best regards,
Krzysztof
next reply other threads:[~2022-06-20 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 19:34 Krzysztof Kozlowski [this message]
2022-06-20 22:33 ` Include in next: krzk/linux-dt Stephen Rothwell
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=b2e86d7a-401d-f48f-2c02-e8253885ab51@kernel.org \
--to=krzk@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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