mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: linux-kernel@vger.kernel.org
Cc: stable-rt@vger.kernel.org
Subject: [PATCH RT 0/4] Warning fixes for PREEMPT_RT
Date: Tue, 06 Oct 2015 03:41:32 +0100	[thread overview]
Message-ID: <1444099292.2956.4.camel@decadent.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]

These patches fix various warnings I got when building 3.2.71-rt104;
some of them are applicable to other RT branches as well.

Ben.

Ben Hutchings (4):
  KVM: lapic: Fix name of timer handler before 3.7
  rtmutex: Fix rt_mutex_timed_fastlock() slowfn type mismatch up to 3.10
  genirq: Fix pointer cast warning for randomness on 32-bit
    architectures
  work-simple: Add missing #include <linux/export.h>

 arch/x86/kvm/lapic.c | 4 +---
 kernel/irq/manage.c  | 3 ++-
 kernel/rtmutex.c     | 2 +-
 kernel/work-simple.c | 1 +
 4 files changed, 5 insertions(+), 5 deletions(-)

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

             reply	other threads:[~2015-10-06  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  2:41 Ben Hutchings [this message]
2015-10-06  2:55 ` [PATCH RT 1/4] KVM: lapic: Fix name of timer handler before 3.7 Ben Hutchings
2015-10-06  2:55 ` [PATCH RT 2/4] rtmutex: Fix rt_mutex_timed_fastlock() slowfn type mismatch up to 3.10 Ben Hutchings
2015-10-06  2:55 ` [PATCH RT 3/4] genirq: Fix pointer cast warning for randomness on 32-bit architectures Ben Hutchings
2015-10-06  2:55 ` [PATCH RT 4/4] work-simple: Add missing #include <linux/export.h> Ben Hutchings
2015-11-21  0:20 ` [PATCH RT 0/4] Warning fixes for PREEMPT_RT Ben Hutchings
2015-11-23 14:36   ` Steven Rostedt

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=1444099292.2956.4.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-rt@vger.kernel.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

Powered by JetHome