From: Albert ARIBAUD <albert.aribaud@3adev.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm: Remove unofficial mach-type number uses
Date: Wed, 25 Jan 2017 08:23:53 +0100 [thread overview]
Message-ID: <20170125082353.10e9d087.albert.aribaud@3adev.fr> (raw)
In-Reply-To: <b3c4ae7e-0dd9-3bf4-3f5d-40832e4574b6@mleia.com>
Hi Vladimir,
Le Wed, 25 Jan 2017 03:34:13 +0200, Vladimir Zapolskiy <vz@mleia.com> a
?crit :
> Hypothetically it could be possible that a machine maintainer finds that
> after rebasing private changes on top of the latest Linux release, a board
> mach type is not recognized by the Linux kernel due to an expired and
> removed entry in mach-types, then s/he updates a record in Russell's DB
> to get the old machine type ID again. However a counterpart change in
> U-boot board config won't be synced automatically, and IMHO it should be
> stated that this problem is neglected, obviously because it causes
> maintenance burden for no gain.
I suspect there's also a case where a custom (non-mainline) kernel is
used on a given board and expects a machine ID from U-Boot, but this
machine ID is not required to be in RMK's list. Ugly, but such things
happen.
> That said, your change is good, it may produce a discontent in particular
> cases, but it won't be problematic to remove it by partial commit
> reverting and adding an explanatory comment into the code.
Agreed.
> --
> With best wishes,
> Vladimir
Cordialement,
Albert ARIBAUD
3ADEV
next prev parent reply other threads:[~2017-01-25 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 21:31 [U-Boot] [PATCH 1/2] arm: Remove unofficial mach-type number uses Tom Rini
2017-01-24 21:31 ` [U-Boot] [PATCH 2/2] arm: Clean up MACH_TYPE defines in config headers Tom Rini
2017-01-24 22:28 ` [U-Boot] [PATCH 1/2] arm: Remove unofficial mach-type number uses Vladimir Zapolskiy
2017-01-24 23:13 ` Tom Rini
2017-01-25 1:34 ` Vladimir Zapolskiy
2017-01-25 7:15 ` Igor Grinberg
2017-01-25 7:23 ` Albert ARIBAUD [this message]
2017-01-25 12:58 ` Tom Rini
2017-01-25 7:25 ` Igor Grinberg
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=20170125082353.10e9d087.albert.aribaud@3adev.fr \
--to=albert.aribaud@3adev.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox