All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walter Lozano <walter.lozano@collabora.com>
To: u-boot@lists.denx.de
Subject: [PATCH] doc: rockchip: Update documentation with Rock Pi 4
Date: Tue, 19 May 2020 17:29:31 -0300	[thread overview]
Message-ID: <cc085a95-44d0-1605-ce24-caa5fd003de9@collabora.com> (raw)
In-Reply-To: <CAMty3ZC96iTXfQnB7jc8Drf_TsQVG9_qz0CbJW9CuVvEi8YJQg@mail.gmail.com>

Hi Jagan

On 19/5/20 15:57, Jagan Teki wrote:
> On Wed, May 20, 2020 at 12:15 AM Walter Lozano
> <walter.lozano@collabora.com> wrote:
>> Update README.rockchip to reflect the support of Radxa Rock Pi 4
>>
>> Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
>> ---
>>   doc/README.rockchip | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
> We have doc/board/rockchip please update there.

Documentation in doc/board/rockchip already states the support for Radxa 
Rock Pi 4. Unfortunately having two different documentation which 
overlaps tends to be redundancy prone.


At this point I think that the best approach it to spawn two tasks

1- Update the doc/README.rockchip with any specific information which 
needs to be updated

2- Continue to move doc/README.rockchip to doc/board/rockchip as you 
started to do


I might find some time to work in task 2, but in the meantime I think 
this patch goes in the direction of task 1


Do you agree?


Regards,


Walter

  reply	other threads:[~2020-05-19 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:45 [PATCH] doc: rockchip: Update documentation with Rock Pi 4 Walter Lozano
2020-05-19 18:57 ` Jagan Teki
2020-05-19 20:29   ` Walter Lozano [this message]
2020-05-19 21:02     ` Tom Rini
2020-05-19 21:06       ` Walter Lozano

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=cc085a95-44d0-1605-ce24-caa5fd003de9@collabora.com \
    --to=walter.lozano@collabora.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.