All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Josh Cartwright <joshc@codeaurora.org>,
	Pramod Gurav <pramod.gurav@smartplayin.com>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: pinctrl-msm build error on Linus' tree
Date: Wed, 8 Oct 2014 16:18:47 -0700	[thread overview]
Message-ID: <20141008231847.GC25134@roeck-us.net> (raw)
In-Reply-To: <CA+5PVA4nJkPZnZ2GfRmj4YBgmBKJBM4cG_3=DC2LXXJtB5=HHw@mail.gmail.com>

On Wed, Oct 08, 2014 at 07:09:18PM -0400, Josh Boyer wrote:
> On Wed, Oct 8, 2014 at 6:49 PM, Josh Cartwright <joshc@codeaurora.org> wrote:
> > Hey Josh-
> >
> > On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
> >> We're hitting a build error on ARM with Linus' tree as of Linux
> >> v3.17-2860-gef0625b70dac :
> >>
> >> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_setup_pm_reset':
> >> drivers/pinctrl/qcom/pinctrl-msm.c:875:4: error: implicit declaration
> >> of function 'register_restart_handler'
> >> [-Werror=implicit-function-declaration]
> >>     if (register_restart_handler(&pctrl->restart_nb))
> >>     ^
> >> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_remove':
> >> drivers/pinctrl/qcom/pinctrl-msm.c:949:2: error: implicit declaration
> >> of function 'unregister_restart_handler'
> >> [-Werror=implicit-function-declaration]
> >>   unregister_restart_handler(&pctrl->restart_nb);
> >>   ^
> >> cc1: some warnings being treated as errors
> >>
> >> Looking at the git logs it seems this was added via:
> >>
> >> commit cf1fc187628913070c3e418ce0e205732435aa2f
> >> Author: Josh Cartwright <joshc@codeaurora.org>
> >> Date:   Tue Sep 23 15:59:53 2014 -0500
> >>
> >>     pinctrl: qcom: use restart_notifier mechanism for ps_hold
> >>
> >>
> >> However, there is literally nothing else in the tree that calls or
> >> provides those functions:
> >>
> >> [jwboyer@vader linux]$ git grep unregister_restart_handler
> >> drivers/pinctrl/qcom/pinctrl-msm.c:     unregister_restart_handler(&pctrl->resta
> >> [jwboyer@vader linux]$
> >>
> >>
> >> I'm rather confused.  How was this commit built and tested?
> >
> > This may be my fault for not clearly stating that this particular patch
> > was dependent on Guenter's restart notifier patchset.  This patch was
> > applied to linusw's tree without these patches.   Perhaps it should be
> > dropped for now until the restart_notifier stuff lands?
> 
> Thanks, that explains things.  I'm not sure if Linus would do a revert
> at this point.  I guess it depends on how fast he's going to merge
> Guenter's patches.
> 
> Is there a reason this wasn't all brought in via one tree?  Seems like
> it should have been.
> 
Too many dependencies all over the place, and thus risk to create merge-time
conflicts. Besides pinctrl, the restart handler infrastructure is already
used by clock, power/restart, and watchdog drivers.

The idea was for me to provide a pointer to an immutable branch
with the infrastructure (which I did), and for all trees using it
to merge with that branch. This way the infrastructure would have been merged
automatically with its first user, and no separate pull request would have
been necessary. Again, I thought we had this well covered. Apparently not,
and of course the one tree who didn't merge the infrastructure got into
mainline first :-(.

Guenter

  reply	other threads:[~2014-10-08 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 22:42 pinctrl-msm build error on Linus' tree Josh Boyer
2014-10-08 22:49 ` Josh Cartwright
2014-10-08 23:09   ` Josh Boyer
2014-10-08 23:18     ` Guenter Roeck [this message]
2014-10-08 23:12 ` Guenter Roeck
2014-10-09  7:34   ` Linus Walleij
2014-10-09 16:07     ` Guenter Roeck
2014-10-10  8:42       ` Linus Walleij
2014-10-10 16:02         ` Guenter Roeck
2014-10-10 16:05           ` Josh Boyer
2014-10-10 16:22             ` Guenter Roeck

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=20141008231847.GC25134@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=joshc@codeaurora.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pramod.gurav@smartplayin.com \
    /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.