mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/3] sandbox: work around missing of_add_memory_bank()
Date: Tue, 22 Jul 2014 11:09:19 +0200	[thread overview]
Message-ID: <CAOpc7mF2QKiSmi2LYpumpBOPyfwg5mkKkHTi2PK2Z4Ehv46GzA@mail.gmail.com> (raw)
In-Reply-To: <CAOpc7mEBJB=xNTbawAx3PyvquErCsQKHg39-mQzHHjU+YczcSA@mail.gmail.com>

Okay, another post, with less heat.

I asked you specifically if a proposed solution would be ok. You
didn't answer at all. That proposed solution would still not "work"
(it won't add a memory bank, because AFAIK in sandbox there are no
memory banks at all, it just uses the hosts memory). It might compile,
however and it might be a bit of unneeded code in the "make
ARCH=sandbox sandbox_defconfig && make all" case.

The tone of your mail made me think that I actually cannot convince
you, that you don't want this. Your reference to signal-to-noise made
me think this. I got the impression that you're dismissing the concept
of static checking and of code-massaging to make that easier.

I don't need to contribute to barebox. My barebox is running for my
board, I can stop now. I don't need to barebox to promote myself, e.g.
as a freelancer. Yet I also don't want to contribute crap to barebox.
So if my attempts are not going any further, and specific question if
XYZ would be ok and instead I get junk about signal-to-noise back,
then I simply aren't inclined to promote things further. Feel yourself
now utterly unconvinced :-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-07-22  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  7:57 Holger Schurig
2014-07-22  8:32 ` Lucas Stach
2014-07-22  8:39   ` Holger Schurig
2014-07-22  8:50     ` Lucas Stach
2014-07-22  8:59       ` Holger Schurig
2014-07-22  9:09         ` Holger Schurig [this message]
2014-07-22  9:43           ` Lucas Stach
2014-07-22 10:25             ` Holger Schurig
2014-07-22 10:52               ` Lucas Stach

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=CAOpc7mF2QKiSmi2LYpumpBOPyfwg5mkKkHTi2PK2Z4Ehv46GzA@mail.gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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