public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/4] cleanup code which handles the Android sparse image format
Date: Thu, 04 Sep 2014 07:28:04 +0200	[thread overview]
Message-ID: <20140904052804.9990C382341@gemini.denx.de> (raw)
In-Reply-To: <1409763954-5494-4-git-send-email-srae@broadcom.com>

Dear Steve Rae,

In message <1409763954-5494-4-git-send-email-srae@broadcom.com> you wrote:
> - port dprintf() to debug()
> - update formatting
> 
> Signed-off-by: Steve Rae <srae@broadcom.com>
> ---
> 
> Changes in v3:
> - use original license text
> 
> Changes in v2:
> - use BSD-3-Clause
> 
>  common/aboot.c | 97 +++++++++++++++++++++++++++++++++-------------------------
>  1 file changed, 56 insertions(+), 41 deletions(-)
> 
> diff --git a/common/aboot.c b/common/aboot.c
> index a302c92..3611feb 100644
> --- a/common/aboot.c
> +++ b/common/aboot.c
> @@ -28,6 +28,9 @@
>   * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
>   * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>   *
> + * NOTE:
> + *   Although it is very similar, this license text is not identical
> + *   to the "BSD-3-Clause", therefore, DO NOT MODIFY THIS LICENSE TEXT!
>   */

I understand your intention of starting with the pristine file, and
then adaptng it to U-Boot, but I don't like adding a broken file in
patch 1/4 only to fix it later in patch 3/4. I think it would be
better to squash these patches.

Second, as already mentioned, we need to assign a SPDX ID for this.

Did you check with SPDX if there a matching ID?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
EMACS belongs in <sys/errno.h>: Editor too big!

  reply	other threads:[~2014-09-04  5:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 17:05 [U-Boot] [PATCH v3 0/4] Implement "sparse format" for fastboot Steve Rae
2014-09-03 17:05 ` [U-Boot] [PATCH v3 1/4] add code to handle Android sparse image format Steve Rae
2014-09-04  5:26   ` Wolfgang Denk
2014-09-17  0:44   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-09-03 17:05 ` [U-Boot] [PATCH v3 2/4] update code which handles " Steve Rae
2014-09-17  0:45   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-09-03 17:05 ` [U-Boot] [PATCH v3 3/4] cleanup code which handles the " Steve Rae
2014-09-04  5:28   ` Wolfgang Denk [this message]
2014-09-04 15:00     ` Tom Rini
2014-09-08 10:49       ` Lukasz Majewski
2014-09-08 11:10         ` Tom Rini
2014-09-17  0:45   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-09-03 17:05 ` [U-Boot] [PATCH v3 4/4] implement " Steve Rae
2014-09-17  0:45   ` [U-Boot] [U-Boot, v3, " 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=20140904052804.9990C382341@gemini.denx.de \
    --to=wd@denx.de \
    --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