All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <lkp@intel.com>,
	Stefan Wahren <wahrenst@gmx.net>,
	kbuild-all@01.org,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [pinctrl:for-next 16/77] drivers/pinctrl/bcm/pinctrl-bcm2835.c:995:10: error: incompatible types when assigning to type 'volatile struct SHIFTER' from type 'unsigned int'
Date: Wed, 4 Sep 2019 15:20:47 +0200	[thread overview]
Message-ID: <CACRpkdYkcR8MAzoQBEOvKQvNwut=uteNaDEs0JZCs5VrOkd9AA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWLR-2Wd7M+KAmk7mKaCw=pUTY4DCehFwbrg_griPrGoA@mail.gmail.com>

On Wed, Sep 4, 2019 at 1:44 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> >    drivers/pinctrl/bcm/pinctrl-bcm2835.c: In function 'bcm2711_pull_config_set':
> > >> arch/m68k/include/asm/atarihw.h:190:22: error: expected identifier or '(' before 'volatile'
>
> https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/commit/?h=for-v5.4&id=053b514295694f3336e97f56d5f41c0d4972c109

What people sometimes do to shut up the automatic checks is to merge
the patch into both trees and let git sort it out. I'd rather not, though.

Yours,
Linus Walleij

      reply	other threads:[~2019-09-04 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 11:07 [pinctrl:for-next 16/77] drivers/pinctrl/bcm/pinctrl-bcm2835.c:995:10: error: incompatible types when assigning to type 'volatile struct SHIFTER' from type 'unsigned int' kbuild test robot
2019-09-04 11:44 ` Geert Uytterhoeven
2019-09-04 13:20   ` Linus Walleij [this message]

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='CACRpkdYkcR8MAzoQBEOvKQvNwut=uteNaDEs0JZCs5VrOkd9AA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=kbuild-all@01.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=wahrenst@gmx.net \
    /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.