Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-next@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: linux-next: manual merge of the timers tree
Date: Tue, 14 Oct 2008 17:12:01 +1100	[thread overview]
Message-ID: <20081014171201.b943052a.sfr@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next merge of the timers tree got a conflict in
kernel/irq/chip.c between commit 0c5d1eb77a8be917b638344a22afe1398236482b
("genirq: record trigger type") from Linus' tree and commit
f2f61d198649e25e4ddce33f716729eae1aab02b ("generic: sparse irqs: use
irq_desc() together with dyn_array, instead of irq_desc[]") from the
timers tree.

I fixed it up (see below).
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc kernel/irq/chip.c
index 5203a59,5a3f73e..0000000
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@@ -126,13 -128,11 +128,12 @@@ int set_irq_type(unsigned int irq, unsi
  		return -ENODEV;
  	}
  
- 	desc = irq_desc + irq;
 -	if (desc->chip->set_type) {
 -		spin_lock_irqsave(&desc->lock, flags);
 -		ret = desc->chip->set_type(irq, type);
 -		spin_unlock_irqrestore(&desc->lock, flags);
 -	}
 +	if (type == IRQ_TYPE_NONE)
 +		return 0;
 +
 +	spin_lock_irqsave(&desc->lock, flags);
 +	ret = __irq_set_trigger(desc, irq, flags);
 +	spin_unlock_irqrestore(&desc->lock, flags);
  	return ret;
  }
  EXPORT_SYMBOL(set_irq_type);

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-10-14  7:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  6:12 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-29  2:02 linux-next: manual merge of the timers tree Stephen Rothwell
2008-10-21  1:43 Stephen Rothwell
2008-10-21 12:15 ` Ingo Molnar
2008-10-21 12:18   ` Stephen Rothwell
2008-10-14  6:03 Stephen Rothwell
2008-10-14  5:59 Stephen Rothwell
2008-10-14  5:51 Stephen Rothwell
2008-09-12  7:10 Stephen Rothwell
2008-09-12  6:57 Stephen Rothwell

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=20081014171201.b943052a.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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