public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <pranith@gatech.edu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] kernel/rcu/tree.c: remove duplicate extern definition
Date: Mon, 14 Apr 2014 10:31:00 -0700	[thread overview]
Message-ID: <20140414173100.GI4496@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJhHMCCX=DdCpDsakJVhRat7-iieqT2_65vfxBjy7C-bSPc8VQ@mail.gmail.com>

On Mon, Apr 14, 2014 at 12:27:47PM -0400, Pranith Kumar wrote:
> On Mon, Apr 14, 2014 at 12:19 PM, Pranith Kumar <pranith@gatech.edu> wrote:
> > Hi Paul,
> >
> > On Mon, Apr 14, 2014 at 12:07 PM, Paul E. McKenney
> > <paulmck@linux.vnet.ibm.com> wrote:
> >> On Sun, Apr 13, 2014 at 05:53:53PM -0400, Pranith Kumar wrote:
> >>> remove duplicate definition of extern resched_cpu
> >>>
> >>> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
> >>
> >> Hello, Pranith,
> >>
> >> When I apply this patch I get the following:
> >>
> >> /home/paulmck/public_git/linux-rcu/kernel/rcu/tree.c: In function ‘rcu_implicit_dynticks_qs’:
> >> /home/paulmck/public_git/linux-rcu/kernel/rcu/tree.c:895:3: error: implicit declaration of function ‘resched_cpu’ [-Werror=implicit-function-declaration]
> >> /home/paulmck/public_git/linux-rcu/kernel/rcu/tree.c: At top level:
> >> /home/paulmck/public_git/linux-rcu/kernel/rcu/tree.c:1009:13: warning: conflicting types for ‘resched_cpu’ [enabled by default]
> >> /home/paulmck/public_git/linux-rcu/kernel/rcu/tree.c:895:3: note: previous implicit declaration of ‘resched_cpu’ was here
> >>
> >> This failed in under number of different Kconfig setups, the .config file
> >> for one of them is attached.
> >>
> >> So this declaration really is needed.  Just out of curiosity, what led
> >> you to believe that it could be removed?
> >>
> 
> Your attached config has the following:
> 
> Linux/x86 3.14.0-rc3 Kernel Configuration
> 
> The patch is against 3.15.0-rc1 (the latest at this time). May be that
> is the reason?

Nope, it was just me messing up when hand-applying the patch.  The reason
the patch wouldn't apply is that I am working against the -rcu tree at
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git,
branch rcu/dev.  Once I applied it correctly, removing the second of
the two declarations rather than the first one, it worked fine.

So please accept my apologies for my confusion.  I have queued your
patch for 3.16, thank you!

							Thanx, Paul


  reply	other threads:[~2014-04-14 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJhHMCBVQTpDecjd5sVhCWJk++K_Rne0DfHRoF7aSd7SRYp1WA@mail.gmail.com>
2014-04-14 16:07 ` [PATCH 1/1] kernel/rcu/tree.c: remove duplicate extern definition Paul E. McKenney
2014-04-14 16:19   ` Pranith Kumar
2014-04-14 16:27     ` Pranith Kumar
2014-04-14 17:31       ` Paul E. McKenney [this message]
2014-04-14 16:32     ` Paul E. McKenney
2014-04-14 16:53       ` Joe Perches
2014-04-14 17:17         ` Paul E. McKenney
     [not found] <CAJhHMCCE0QHvzqrdY-w8bB8ZK=JRN02V29XwaFYRXmu=9RhG9Q@mail.gmail.com>
2014-04-14  1:39 ` Pranith Kumar
2014-04-14  2:50   ` Joe Perches
2014-04-14  3:03     ` Pranith Kumar
2014-04-14  3:18       ` Joe Perches
2014-04-14  3:31         ` Pranith Kumar

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=20140414173100.GI4496@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranith@gatech.edu \
    /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