linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rahul Tanwar <rahul.tanwar@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: [GIT PULL] Oneliner fix for the pinctrl pull request
Date: Thu, 28 Nov 2019 14:18:51 +0100	[thread overview]
Message-ID: <CACRpkdb_5xjLBSPaGrDadHUj=4Npz13YELJw+Ov+JyigGPBZjg@mail.gmail.com> (raw)

Hi Linus,

as requested yesterday, a oneliner fix adding the license to
the new Intel pin controller.

This time just based on the top of your tree from yesterday.

Please pull it in.

Sorry for the mess.

Yours,
Linus Walleij

The following changes since commit a6ed68d6468bd5a3da78a103344ded1435fed57a:

  Merge tag 'drm-next-2019-11-27' of
git://anongit.freedesktop.org/drm/drm (2019-11-27 17:45:48 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.5-2

for you to fetch changes up to 6d29032c2cef31633db5dfd946fbcf9190dddef0:

  pinctrl: Fix warning by adding missing MODULE_LICENSE (2019-11-28
09:12:43 +0100)

----------------------------------------------------------------
Fixes a MODULE_LICENSE() problem in the Equilibrium pin
controller.

----------------------------------------------------------------
Rahul Tanwar (1):
      pinctrl: Fix warning by adding missing MODULE_LICENSE

 drivers/pinctrl/pinctrl-equilibrium.c | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2019-11-28 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 13:18 Linus Walleij [this message]
2019-12-02  2:05 ` [GIT PULL] Oneliner fix for the pinctrl pull request pr-tracker-bot

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='CACRpkdb_5xjLBSPaGrDadHUj=4Npz13YELJw+Ov+JyigGPBZjg@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rahul.tanwar@linux.intel.com \
    --cc=torvalds@linux-foundation.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).