linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] randconfig warning fixes for thermal
Date: Tue, 9 Feb 2016 14:18:16 -0800	[thread overview]
Message-ID: <20160209221815.GE28102@localhost.localdomain> (raw)
In-Reply-To: <1453740264-1972562-1-git-send-email-arnd@arndb.de>

On Mon, Jan 25, 2016 at 05:44:09PM +0100, Arnd Bergmann wrote:
> These are three simple fixes for ARM randconfig builds:
> 
>  [PATCH 1/3] thermal: spear: use __maybe_unused for PM functions
>  [PATCH 2/3] thermal: allow spear-thermal driver to be a module
>  [PATCH 3/3] thermal: allow u8500-thermal driver to be a module
> 
> All three bugs are on configurationsn that are not important and
> that rarely happen even with randconfig builds.
> 
> 	Arnd

Thanks a lot for your cleanups Arnd,
queueing all three.

Eduardo Valentin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160209/57f41a2f/attachment.sig>

      parent reply	other threads:[~2016-02-09 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 16:44 [PATCH 0/3] randconfig warning fixes for thermal Arnd Bergmann
2016-01-25 16:44 ` [PATCH 1/3] thermal: spear: use __maybe_unused for PM functions Arnd Bergmann
2016-01-25 16:44 ` [PATCH 2/3] thermal: allow spear-thermal driver to be a module Arnd Bergmann
2016-01-25 16:44 ` [PATCH 3/3] thermal: allow u8500-thermal " Arnd Bergmann
2016-01-27  7:33   ` Lee Jones
2016-02-09 22:10     ` Eduardo Valentin
2016-02-05 14:44   ` Linus Walleij
2016-02-09 22:18 ` Eduardo Valentin [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=20160209221815.GE28102@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).