All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arndale: fix unknown status
Date: Fri, 15 Mar 2019 14:52:12 +0100	[thread overview]
Message-ID: <CAJKOXPdL_BB-ish3h3N-L+1b7TiTLMWciGE=H1QMkY1UgF=_2A@mail.gmail.com> (raw)
In-Reply-To: <20190314192356.GT8732@bill-the-cat>

On Thu, 14 Mar 2019 at 20:24, Tom Rini <trini@konsulko.com> wrote:
> 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!

Sure, let me take a look.

Best regards,
Krzysztof

  reply	other threads:[~2019-03-15 13:52 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
2019-03-15 13:52             ` Krzysztof Kozlowski [this message]
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='CAJKOXPdL_BB-ish3h3N-L+1b7TiTLMWciGE=H1QMkY1UgF=_2A@mail.gmail.com' \
    --to=krzk@kernel.org \
    --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.