From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@busybox.net, Ivan Riabtsov <ivriabtsov@gmail.com>
Subject: Re: [Buildroot] buildroot u-boot.nand oob size
Date: Fri, 24 Sep 2021 10:06:11 +0200 [thread overview]
Message-ID: <20210924100611.3d040035@windsurf> (raw)
In-Reply-To: <87fstuquef.fsf@dell.be.48ers.dk>
On Fri, 24 Sep 2021 09:56:08 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> Ahh, that is presumably a mailman configuration issue after the latest
> changes. Will you report it to osuosl or should I?
I did it, you're in Cc.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-09-24 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 11:55 [Buildroot] buildroot u-boot.nand oob size Ivan Riabtsov
2021-09-23 19:31 ` Arnout Vandecappelle
2021-09-24 7:04 ` Thomas Petazzoni
2021-09-24 7:56 ` Peter Korsgaard
2021-09-24 8:06 ` Thomas Petazzoni [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=20210924100611.3d040035@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=ivriabtsov@gmail.com \
--cc=peter@korsgaard.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