linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] irq: gic-v3: Tag all low level accessors __maybey_unused
Date: Tue, 9 Sep 2014 01:47:47 +1000	[thread overview]
Message-ID: <20140909014747.0931d51e@canb.auug.org.au> (raw)
In-Reply-To: <20140907140255.GB30828@titan.lakedaemon.net>

Hi Jason,

On Sun, 7 Sep 2014 10:02:55 -0400 Jason Cooper <jason@lakedaemon.net> wrote:
>
> On Sat, Sep 06, 2014 at 01:54:12PM +0100, Mark Brown wrote:
> > On Sun, Aug 17, 2014 at 01:04:53PM -0400, Jason Cooper wrote:
> > > On Wed, Jul 30, 2014 at 08:23:14PM +0100, Mark Brown wrote:
> > > > From: Mark Brown <broonie@linaro.org>
> > 
> > > > This is only really needed for gic_write_sgi1r in the !SMP case since it
> > > > is only referenced in the SMP initialisation code but it seems better to
> > > > have these functions all next to each other and declared consistently.
> > 
> > > > Signed-off-by: Mark Brown <broonie@linaro.org>
> > > > ---
> > > >  drivers/irqchip/irq-gic-v3.c | 10 +++++-----
> > > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > 
> > > Applied to irqchip/urgent
> > 
> > This appears to have disappeared from -next and the warning is back.
> 
> Hmm, interesting. Here's what I have in irqchip/for-next,irqchip/urgent:
> 
>   c44e9d77fd1c irqchip: gic-v3: Tag all low level accessors __maybe_unused
>   ddc86821ee2c irqchip: gic-v3: Only define gic_peek_irq() when building SMP
> 
> and:
> 
> $ git tag --contains c44e9d77fd1c | grep ^next | sort -V
> next-20140820
> next-20140822
> next-20140823
> next-20140825
> next-20140826
> next-20140827
> next-20140828
> next-20140829
> 
> To see whether I forgot to add /urgent to /for-next or if
> irqchip/for-next was dropped, I did the same search against the first
> commit I added to irqchip/core:
> 
> $ git tag --contains 1c36d42c4ffe | grep ^next | sort -V
> next-20140822
> next-20140823
> next-20140825
> next-20140826
> next-20140827
> next-20140828
> next-20140829
> 
> Also dropped on the 30th.  So, unless I really screwed up, -next is no
> longer pulling irqchip/for-next.
> 
> Stephen, could you please look and see if this is the case?

I am fetching it ok.  Unfortunately, in the hand over to Mark last week
he ended up with an old version of my control file and so that tree was
net being included.  Sorry about that, it should be fixed in
next-20140908.

-- 
Cheers,
Stephen Rothwell                    sfr at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140909/3c16b13b/attachment.sig>

  reply	other threads:[~2014-09-08 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 19:23 [PATCH] irq: gic-v3: Tag all low level accessors __maybey_unused Mark Brown
2014-08-17 17:04 ` Jason Cooper
2014-09-06 12:54   ` Mark Brown
2014-09-07 14:02     ` Jason Cooper
2014-09-08 15:47       ` Stephen Rothwell [this message]
2014-08-18  7:11 ` Uwe Kleine-König
2014-08-18 10:51   ` Jason Cooper

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=20140909014747.0931d51e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-arm-kernel@lists.infradead.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).