All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the devicetree tree
Date: Fri, 30 Jul 2010 00:10:08 -0600	[thread overview]
Message-ID: <AANLkTimuYkDkAPXTAKLW-Fdj9dyEci9PGutMRRm2k3mM@mail.gmail.com> (raw)
In-Reply-To: <20100730145415.8ed17b7e.sfr@canb.auug.org.au>

On Thu, Jul 29, 2010 at 10:54 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Grant,
>
> After merging the devicetree tree, today's linux-next build (powerpc64
> allnoconfig) produced this warning:
>
> drivers/of/irq.c: In function 'of_irq_map_raw':
> drivers/of/irq.c:102: warning: cast from pointer to integer of different size
>
> Introduced by commit 7d12c3ee9e1843b1d19d9c308988bb163fb9aa0b ("of/irq:
> Fix endian issues in parsing interrupt specifiers").

Thanks.  fixed now and pushed out.  Silly typo.

g.

  reply	other threads:[~2010-07-30  6:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30  4:54 linux-next: build warning after merge of the devicetree tree Stephen Rothwell
2010-07-30  6:10 ` Grant Likely [this message]
2010-10-21  2:37 Stephen Rothwell
2010-10-21  3:26 ` Grant Likely
2010-10-21  8:05   ` Ingo Molnar
2010-10-21 17:04     ` Grant Likely
2017-04-28  2:45 Stephen Rothwell
2017-05-03  5:44 ` Stephen Rothwell
2017-05-03 12:12   ` Rob Herring
2017-05-03 12:46     ` Stephen Rothwell
2018-03-06  1:03 Stephen Rothwell
2018-03-06  1:05 Stephen Rothwell
2018-03-06  2:34 ` Rob Herring
2018-03-06  3:11   ` Stephen Rothwell
2018-05-09  6:04 Stephen Rothwell
2018-05-09 12:17 ` Rob Herring
2018-05-29  6:04   ` Stephen Rothwell
2021-08-24  3:18 Stephen Rothwell
2021-08-24 12:35 ` Rob Herring
2021-09-02 22:34   ` Stephen Rothwell
2021-09-03  0:38     ` Rob Herring
2021-09-03  0:38       ` Rob Herring
2021-10-26  2:44 Stephen Rothwell
2023-02-20  5:36 Stephen Rothwell

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=AANLkTimuYkDkAPXTAKLW-Fdj9dyEci9PGutMRRm2k3mM@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.