Thread (13 messages) flat view 13 messages, 9 authors, 2022-02-06

Re: [PATCH] HPE BMC GXP SUPPORT

From: "Verdun, Jean-Marie" <verdun@hpe.com>
Date: 2022-02-02 18:16:49
Also in: dri-devel, linux-devicetree, linux-gpio, linux-i2c, linux-pm, linux-pwm, linux-serial, linux-spi, linux-usb, linux-watchdog, lkml

Possibly related (same subject, not in this thread)

This is far too big for a single patch.  It needs to be broken into
functional chunks that can be reviewed individually.  Each driver and
each device tree change along with it's accompanying code need to be
done in individual patches.  The way it is it can't be reviewed in any
sane manner.
-corey
Thanks for your feedback. We are getting a little bit lost here, as our plan was to submit initial

- bindings
- dts for SoC and 1 board
- initial platform init code

Then drivers code avoiding to send many dts updates which might complexify the review. We wanted to send all drivers code to relevant reviewers by tomorrow.

So, what you are asking ( do not worry I am not trying to negotiate, I just want to avoid English misunderstandings as I am French) is to send per driver

- binding
- dts update
- driver code

For each driver through different submission (with each of them containing the 3 associated parts) ?

What shall be the initial one in our case as we are introducing a platform ? An empty dts infrastructure and then we make it grow one step at a time ?

vejmarie


 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help