All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marian Ulbricht <ulbricht@innoroute.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/1 v2] add support for mws4 board
Date: Sun, 8 May 2022 12:11:20 -0400	[thread overview]
Message-ID: <20220508161120.GJ3901321@bill-the-cat> (raw)
In-Reply-To: <cf75d4aa-f2b8-7689-bc55-2f9a29ba2743@innoroute.de>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

On Sun, May 08, 2022 at 05:47:58PM +0200, Marian Ulbricht wrote:
> Am 08.05.22 um 16:21 schrieb Tom Rini:
> > On Sun, May 08, 2022 at 03:46:55PM +0200, Marian Ulbricht wrote:
> > 
> > > mws4 is an arm based nuclear probe hardware used from german government to
> > > monitor nuclear activity
> > > 
> > > Signed-off-by: Marian Ulbricht <ulbricht@innoroute.de>
> > 
> > Thanks for the submission.  Have you submitted the board dts files to
> > upstream Linux?  Also, please remove all of the commented out code in
> > the board files, etc.
> > 
> Hi,
> not yet, i started from bottom up: u-boot -> buildroot -> kernel

OK.  We require the board dts itself to be submitted to the kernel
first, as we keep that as an unchanged copy of the file in upstream and
try and sync them down periodically.

> [PATCH 1/1 v2] add support for mws4 board
> 
> mws4 is an arm based nuclear probe hardware used from german government to
> monitor nuclear activity
> 
> Signed-off-by: Marian Ulbricht <ulbricht@innoroute.de>
> ---
> Changes v2:
> 
> * code cleanup

Note that there's a number of whitespace, etc, issues that checkpatch.pl
reports.  For the dts files, you can set that aside and follow what
upstream says there, but the rest need to be addressed.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2022-05-08 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 13:46 [PATCH 1/1] add support for mws4 board Marian Ulbricht
2022-05-08 14:21 ` Tom Rini
2022-05-08 15:47   ` [PATCH 1/1 v2] " Marian Ulbricht
2022-05-08 16:11     ` Tom Rini [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=20220508161120.GJ3901321@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ulbricht@innoroute.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.