All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arndale: fix unknown status
Date: Thu, 14 Mar 2019 15:23:56 -0400	[thread overview]
Message-ID: <20190314192356.GT8732@bill-the-cat> (raw)
In-Reply-To: <CAJKOXPc82VH4Kp4HcNfZ5kTeQ5tEwX-Y4f3Dqf=Q8Fu3GTSdjQ@mail.gmail.com>

On Thu, Mar 14, 2019 at 09:23:53AM +0100, Krzysztof Kozlowski wrote:
> On Thu, 14 Mar 2019 at 09:15, Minkyu Kang <mk7.kang@samsung.com> wrote:
> >
> > Hi,
> >
> > On 14/03/2019 16:38, Krzysztof Kozlowski wrote:
> > > On Thu, 14 Mar 2019 at 05:10, Minkyu Kang <mk7.kang@samsung.com> wrote:
> > >>
> > >> On 14/03/2019 09:44, Minkyu Kang wrote:
> > >>> set status to Maintained
> > >>>
> > >>> Signed-off-by: Minkyu Kang <mk7.kang@samsung.com>
> > >>> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> > >>> ---
> > >>>  board/samsung/arndale/MAINTAINERS | 2 +-
> > >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> > >>>
> > >>> diff --git a/board/samsung/arndale/MAINTAINERS b/board/samsung/arndale/MAINTAINERS
> > >>> index 98ccaa4..aa64c7a 100644
> > >>> --- a/board/samsung/arndale/MAINTAINERS
> > >>> +++ b/board/samsung/arndale/MAINTAINERS
> > >>> @@ -1,6 +1,6 @@
> > >>>  ARNDALE BOARD
> > >>>  M:   Krzysztof Kozlowski <krzk@kernel.org>
> > >>> -S:   Odd Fixes
> > >>> +S:   Maintained
> > >>>  F:   board/samsung/arndale/
> > >>>  F:   include/configs/arndale.h
> > >>>  F:   configs/arndale_defconfig
> > >>>
> > >>
> > >> applied to u-boot-samsung.
> > >
> > > Hi,
> > >
> > > In the commit changing the maintainer I changed on purpose to Odd
> > > Fixes. Because the board is not actively maintained. It is not
> > > "unknown status", it is perfectly valid status. Why changing it to
> > > Maintained?
> > >
> >
> > $ ./tools/genboardscfg.py -f
> > WARNING: Odd Fixes: unknown status for 'arndale'
> >
> > If you don't want to maintain then, it would be set to Orphan?
> 
> I think then the genboardscfg.py should be updated because "Odd fixer"
> is a valid entry from MAINTAINERS (although not popular).
> "Odd Fixes:   It has a maintainer but they don't have time to do much
> other than throw the odd patch in. See below.."
> The board is pretty close to being orphaned but not yet.

I'm taking your patch to the MAINTAINERS file now.  That said, generally
"odd fixes" are what's required of board maintainers, once the port is
in.  However, as we push forward on moving to various frameworks that
should make life easier overall, over the long term, changes are needed
that may be more than just an occasional fix.  Looking at arndale right
now for example:
       arm:  w+   arndale
+(arndale) ===================== WARNING ======================
+(arndale) This board uses CONFIG_DM_I2C_COMPAT. Please remove
+(arndale) (possibly in a subsequent patch in your series)
+(arndale) before sending patches to the mailing list.
+(arndale) ====================================================
 
So, do you have time to look into that build time warning?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190314/1292c6b5/attachment.sig>

  reply	other threads:[~2019-03-14 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190314004445epcas1p3ace241b1a00f3237790cb95e2d338794@epcas1p3.samsung.com>
2019-03-14  0:44 ` [U-Boot] [PATCH] arndale: fix unknown status Minkyu Kang
2019-03-14  4:10   ` Minkyu Kang
2019-03-14  7:38     ` Krzysztof Kozlowski
2019-03-14  8:15       ` Minkyu Kang
2019-03-14  8:23         ` Krzysztof Kozlowski
2019-03-14 19:23           ` Tom Rini [this message]
2019-03-15 13:52             ` Krzysztof Kozlowski
2019-03-15 13:53               ` Tom Rini

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=20190314192356.GT8732@bill-the-cat \
    --to=trini@konsulko.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.