From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Dominik Brodowski <linux@dominikbrodowski•net>,
Jason Wong <tsanghan@gmail•com>
Subject: linux-next: manual merge of the staging-next tree with the pcmcia tree
Date: Wed, 28 Apr 2010 16:07:41 +1000 [thread overview]
Message-ID: <20100428160741.2695a14f.sfr@canb.auug.org.au> (raw)
Hi Greg,
Today's linux-next merge of the staging-next tree got a conflict in
drivers/staging/comedi/drivers/cb_das16_cs.c between commitc
8bf6e66c254bba7d0ea3f5d02420776dceac657 ("") from the pcmcia tree and
commit 6ea17dd43c1153f99920e66f806d86f4e83583cc ("Staging: comedi:
cb_das16_cs: fixed multiple brace coding style issues") from the
staging-next tree.
Just context changes. I fixed it up (see below) and can carry the fix as
necessary.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
diff --cc drivers/staging/comedi/drivers/cb_das16_cs.c
index e0352c6,68bd5ca..0000000
--- a/drivers/staging/comedi/drivers/cb_das16_cs.c
+++ b/drivers/staging/comedi/drivers/cb_das16_cs.c
@@@ -175,17 -175,17 +175,17 @@@ static int das16cs_attach(struct comedi
printk("I/O base=0x%04lx ", dev->iobase);
printk("fingerprint:\n");
- for (i = 0; i < 48; i += 2) {
+ for (i = 0; i < 48; i += 2)
printk("%04x ", inw(dev->iobase + i));
- }
+
printk("\n");
- ret = request_irq(link->irq.AssignedIRQ, das16cs_interrupt,
+ ret = request_irq(link->irq, das16cs_interrupt,
IRQF_SHARED, "cb_das16_cs", dev);
- if (ret < 0) {
+ if (ret < 0)
return ret;
- }
+
- dev->irq = link->irq.AssignedIRQ;
+ dev->irq = link->irq;
printk("irq=%u ", dev->irq);
dev->board_ptr = das16cs_probe(dev, link);
next reply other threads:[~2010-04-28 6:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 6:07 Stephen Rothwell [this message]
2010-04-28 15:26 ` linux-next: manual merge of the staging-next tree with the pcmcia tree Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-04-28 6:11 Stephen Rothwell
2010-04-28 15:25 ` Greg KH
2010-05-12 6:03 Stephen Rothwell
2010-05-12 19:50 ` Greg KH
2010-05-17 5:49 Stephen Rothwell
2010-05-17 18:01 ` Greg KH
2010-08-02 3:57 Stephen Rothwell
2010-08-02 22:23 ` Greg KH
2010-08-02 3:57 Stephen Rothwell
2010-08-02 22:23 ` Greg KH
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=20100428160741.2695a14f.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@dominikbrodowski$(echo .)net \
--cc=tsanghan@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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