From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/5] of: introduce the overlay manager
Date: Thu, 27 Oct 2016 16:54:25 +0200 [thread overview]
Message-ID: <20161027145425.x6idpcrq6nbhmihv@kwain> (raw)
In-Reply-To: <CANLsYkxF4_fZwaBe+_0twMhND3TfpnmkXA_1q=AN_j9=cQ5ukw@mail.gmail.com>
On Thu, Oct 27, 2016 at 08:49:29AM -0600, Mathieu Poirier wrote:
>
> I agree - something like this should have attracted more reviews. I
> suggest providing a better explanation, i.e what you are doing and why
> in more details. I reviewed your set and I'm still not sure of
> exactly what it does, hence not being able to comment on the validity
> of the approach.
>
> I'm pretty sure there is value in what you are suggesting, it's a
> matter of getting people to understand the approach and motivation.
That's what I tried to do in the cover-letter. What do you think is
missing that I should add in it?
Thanks,
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161027/6ba52130/attachment-0001.sig>
next prev parent reply other threads:[~2016-10-27 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 14:57 [RFC PATCH 0/5] Add an overlay manager to handle board capes Antoine Tenart
2016-10-26 14:57 ` [RFC PATCH 1/5] of: introduce the overlay manager Antoine Tenart
2016-10-26 16:29 ` Mathieu Poirier
2016-10-26 19:02 ` Thomas Petazzoni
2016-10-27 14:03 ` Antoine Tenart
2016-10-27 14:49 ` Mathieu Poirier
2016-10-27 14:54 ` Antoine Tenart [this message]
2016-10-27 9:10 ` Matthias Brugger
2016-10-27 14:56 ` Pantelis Antoniou
2016-10-27 15:07 ` Pantelis Antoniou
2016-10-26 14:57 ` [RFC PATCH 2/5] of: overlay-mgr: add the CHIP format Antoine Tenart
2016-10-26 14:57 ` [RFC PATCH 3/5] w1: report errors returned by w1_family_notify Antoine Tenart
2016-10-26 16:39 ` Mathieu Poirier
2016-10-26 14:57 ` [RFC PATCH 4/5] w1: add a callback to call slave when a new device is connected Antoine Tenart
2016-10-26 16:42 ` Mathieu Poirier
2016-10-26 17:30 ` Antoine Tenart
2016-10-26 14:57 ` [RFC PATCH 5/5] of: overlay-mgr: add a detector for headers stored on a ds2431 eeprom over w1 Antoine Tenart
2016-10-27 9:18 ` Matthias Brugger
2016-10-27 9:19 ` Matthias Brugger
2016-10-27 13:55 ` Antoine Tenart
2016-10-27 13:41 ` [RFC PATCH 0/5] Add an overlay manager to handle board capes Rob Herring
2016-10-27 14:25 ` Antoine Tenart
2016-10-27 15:13 ` Hans de Goede
2016-10-27 17:30 ` Rob Herring
2016-10-27 20:51 ` Hans de Goede
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=20161027145425.x6idpcrq6nbhmihv@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=linux-arm-kernel@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