linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 17 (pinctrl-mcp23s08)
Date: Fri, 17 Apr 2020 12:22:51 +0200	[thread overview]
Message-ID: <CACRpkdZ9rKHiszLYAbbhaTCzgMdH1gzRmbsB9G2g4+B=KpdfgA@mail.gmail.com> (raw)
In-Reply-To: <0f828695-71cc-ab94-e0f0-ae63a192b283@infradead.org>

On Fri, Apr 17, 2020 at 8:16 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 4/16/20 9:50 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200416:
> >
>
> on i386:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/pinctrl/pinctrl-mcp23s08.o

Thanks, got a patch to fix it too, folded in your reported-by.

Yours,
Linus Walleij

  reply	other threads:[~2020-04-17 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  4:50 linux-next: Tree for Apr 17 Stephen Rothwell
2020-04-17  6:16 ` linux-next: Tree for Apr 17 (pinctrl-mcp23s08) Randy Dunlap
2020-04-17 10:22   ` Linus Walleij [this message]
2020-04-17  7:19 ` linux-next: Tree for Apr 17 Christian Borntraeger
2020-04-17  7:27   ` Mauro Carvalho Chehab
2020-04-17 14:48 ` linux-next: Tree for Apr 17 (mmc/host/sdhci-of-at91.c) Randy Dunlap
2020-04-20  9:12   ` Ulf Hansson
2020-04-20 10:28     ` Adrian Hunter
2020-04-20 12:27       ` Masahiro Yamada
2020-04-20 13:45         ` Adrian Hunter
2020-04-22 10:15         ` Ulf Hansson
2020-04-22 10:54           ` Masahiro Yamada
2020-04-17 15:23 ` linux-next: Tree for Apr 17 (drivers/char/hw_random/cctrng.c) Randy Dunlap
2020-04-17 20:14   ` Hadar Gat

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='CACRpkdZ9rKHiszLYAbbhaTCzgMdH1gzRmbsB9G2g4+B=KpdfgA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 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).