devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Kim Phillips <kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH 4/4] dtc/libfdt: sparse fixes
Date: Thu, 15 Nov 2012 14:53:05 +1100	[thread overview]
Message-ID: <20121115035305.GH32290@truffula.fritz.box> (raw)
In-Reply-To: <20121114184630.64242a970b40c2b3b55f54a2-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On Wed, Nov 14, 2012 at 06:46:30PM -0600, Kim Phillips wrote:
> On Wed, 14 Nov 2012 21:23:03 +1100
> David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> 
> > Hrm.  The patch comment shows a lot of sparse warnings, but the patch
> > looks like the basic conversion of the code from uint32_t to
> > annontated fdt32_t types.
> 
> not sure what you're getting at: isn't this to be expected?  Anyway,
> I'm going to guess you mean to re-word the commit message.

Ah, I see what you're getting at, and yes.  The current message
suggests this is fixing real endian problems found by sparse, rather
than being almost a mechanical replacement of uint32_t with fdt32_t.
If there are real bug fixes, I'd prefer to see that broken out into a
different patch.

> >  I also never saw a 3/4.  Has something gone
> > wrong with the patch sending?
> 
> I sent 3/4 in reply-to your comments on v1 of the patch, and the
> rest without the reply-to reference, so 3/4 might show up out of
> order in your inbox, depending on how it's configured.  I'll send
> the entire series with the same reference - jdl's comments to v2 -
> instead next time.

Ok.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  parent reply	other threads:[~2012-11-15  3:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  0:34 [PATCH 4/4] dtc/libfdt: sparse fixes Kim Phillips
     [not found] ` <20121113183430.472a0d989815fbd73ee9b437-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-14 10:23   ` David Gibson
     [not found]     ` <20121114102303.GF32290-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-11-15  0:46       ` Kim Phillips
     [not found]         ` <20121114184630.64242a970b40c2b3b55f54a2-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-15  3:53           ` David Gibson [this message]
2013-01-06 21:58   ` Jon Loeliger

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=20121115035305.GH32290@truffula.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).