From: Sascha Hauer <s.hauer@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RESEND] [PATCH 0/2] small doc fixes
Date: Thu, 17 Jan 2019 08:39:41 +0100 [thread overview]
Message-ID: <20190117073941.hlfcdfpo4tvau2pd@pengutronix.de> (raw)
In-Reply-To: <20190116101601.3441-1-rhi@pengutronix.de>
On Wed, Jan 16, 2019 at 11:15:59AM +0100, Roland Hieber wrote:
> Hi Sascha,
>
> I'll resend these two, they are not applied yet, and now apply cleanly
> to master.
>
> Roland Hieber (2):
> Documentation: state: fix closing brace without opening brace
> Documentation: i.MX: Kindle 4/5: fix sphinx warnings
Applied now, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-01-17 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 15:55 [PATCH 1/3] Documentation: i.MX: improve wording, add markup and missing articles Roland Hieber
2018-12-10 15:55 ` [PATCH 2/3] Documentation: state: fix closing brace without opening brace Roland Hieber
2018-12-10 15:55 ` [PATCH 3/3] Documentation: i.MX: Kindle 4/5: fix sphinx warnings Roland Hieber
2018-12-13 6:57 ` [PATCH 1/3] Documentation: i.MX: improve wording, add markup and missing articles Sascha Hauer
2018-12-14 10:13 ` Roland Hieber
2018-12-17 9:45 ` Sascha Hauer
2019-01-11 11:35 ` Roland Hieber
2019-01-16 10:15 ` [RESEND] [PATCH 0/2] small doc fixes Roland Hieber
2019-01-16 10:16 ` [RESEND] [PATCH 1/2] Documentation: state: fix closing brace without opening brace Roland Hieber
2019-01-16 10:16 ` [RESEND] [PATCH 2/2] Documentation: i.MX: Kindle 4/5: fix sphinx warnings Roland Hieber
2019-01-17 7:39 ` Sascha Hauer [this message]
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=20190117073941.hlfcdfpo4tvau2pd@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.de \
/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