From: Zang Roy-R61911 <r61911@freescale.com> To: Wood Scott-B07421 <B07421@freescale.com>, Anton Vorontsov <cbouatmailru@gmail.com> Cc: dedekind1@gmail.com, Lan Chunhe-B25806 <B25806@freescale.com>, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, akpm@linux-foundation.org, dwmw2@infradead.org, Gala Kumar-B11780 <B11780@freescale.com> Subject: RE: [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common to elbc devices Date: Fri, 15 Oct 2010 13:03:14 +0800 [thread overview] Message-ID: <3850A844E6A3854C827AC5C0BEC7B60A2B049B@zch01exm23.fsl.freescale.net> (raw) In-Reply-To: <20101014110239.466072be@udp111988uds.am.freescale.net> > -----Original Message----- > From: Wood Scott-B07421 > Sent: Friday, October 15, 2010 0:03 AM > To: Zang Roy-R61911 > Cc: Anton Vorontsov; linux-mtd@lists.infradead.org; dwmw2@infradead.org; > dedekind1@gmail.com; akpm@linux-foundation.org; Lan Chunhe-B25806; Wood Scott- > B07421; Gala Kumar-B11780; linuxppc-dev@ozlabs.org > Subject: Re: [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common > to elbc devices >=20 > On Wed, 13 Oct 2010 23:43:38 -0700 > "Zang Roy-R61911" <r61911@freescale.com> wrote: >=20 > > > Plus, I think the patch is not runtime bisectable (i.e. you > > > now do request_irq() here, but not removing it from the nand > > > driver, so nand will fail to probe). > > Nand driver does not need to request irq. It will use the irq requested by > lbc. > > remember, other lbc device may also need to use this registered irq. > > It should not be removed in nand driver. >=20 > The point is that you need to make both changes in the same patch. But according to previous discussion, if lbc driver is registered successful, it will not be removed. (.remove function is dropped in the patch). that is not bisectable? nand driver will not touch the irq. all irq status process is in the lbc driver. Thanks. Roy
WARNING: multiple messages have this Message-ID (diff)
From: Zang Roy-R61911 <r61911@freescale.com> To: Wood Scott-B07421 <B07421@freescale.com>, Anton Vorontsov <cbouatmailru@gmail.com> Cc: dedekind1@gmail.com, Lan Chunhe-B25806 <B25806@freescale.com>, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, akpm@linux-foundation.org, dwmw2@infradead.org, Gala Kumar-B11780 <B11780@freescale.com> Subject: RE: [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common to elbc devices Date: Fri, 15 Oct 2010 13:03:14 +0800 [thread overview] Message-ID: <3850A844E6A3854C827AC5C0BEC7B60A2B049B@zch01exm23.fsl.freescale.net> (raw) In-Reply-To: <20101014110239.466072be@udp111988uds.am.freescale.net> > -----Original Message----- > From: Wood Scott-B07421 > Sent: Friday, October 15, 2010 0:03 AM > To: Zang Roy-R61911 > Cc: Anton Vorontsov; linux-mtd@lists.infradead.org; dwmw2@infradead.org; > dedekind1@gmail.com; akpm@linux-foundation.org; Lan Chunhe-B25806; Wood Scott- > B07421; Gala Kumar-B11780; linuxppc-dev@ozlabs.org > Subject: Re: [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common > to elbc devices > > On Wed, 13 Oct 2010 23:43:38 -0700 > "Zang Roy-R61911" <r61911@freescale.com> wrote: > > > > Plus, I think the patch is not runtime bisectable (i.e. you > > > now do request_irq() here, but not removing it from the nand > > > driver, so nand will fail to probe). > > Nand driver does not need to request irq. It will use the irq requested by > lbc. > > remember, other lbc device may also need to use this registered irq. > > It should not be removed in nand driver. > > The point is that you need to make both changes in the same patch. But according to previous discussion, if lbc driver is registered successful, it will not be removed. (.remove function is dropped in the patch). that is not bisectable? nand driver will not touch the irq. all irq status process is in the lbc driver. Thanks. Roy
next prev parent reply other threads:[~2010-10-15 5:03 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-17 7:01 [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common to elbc devices Roy Zang 2010-09-17 7:01 ` Roy Zang 2010-09-17 7:01 ` [PATCH 2/3 v4] P4080/mtd: Only make elbc nand driver detect nand flash partitions Roy Zang 2010-09-17 7:01 ` Roy Zang 2010-09-17 7:01 ` [PATCH 3/3 v4] P4080/mtd: Fix the freescale lbc issue with 36bit mode Roy Zang 2010-09-17 7:01 ` Roy Zang 2010-09-20 13:19 ` [PATCH 2/3 v4] P4080/mtd: Only make elbc nand driver detect nand flash partitions Anton Vorontsov 2010-10-02 12:36 ` Zang Roy-R61911 2010-10-02 12:36 ` Zang Roy-R61911 2010-10-04 15:38 ` Scott Wood 2010-10-04 15:38 ` Scott Wood 2010-10-14 3:09 ` Zang Roy-R61911 2010-10-14 3:09 ` Zang Roy-R61911 2010-10-14 16:01 ` Scott Wood 2010-10-14 16:01 ` Scott Wood 2010-10-15 2:15 ` Zang Roy-R61911 2010-10-15 2:15 ` Zang Roy-R61911 2010-10-14 4:14 ` Zang Roy-R61911 2010-10-14 4:14 ` Zang Roy-R61911 2010-09-20 15:37 ` [PATCH 1/3 v4] P4080/eLBC: Make Freescale elbc interrupt common to elbc devices Anton Vorontsov 2010-10-14 6:43 ` Zang Roy-R61911 2010-10-14 6:43 ` Zang Roy-R61911 2010-10-14 16:02 ` Scott Wood 2010-10-14 16:02 ` Scott Wood 2010-10-15 5:03 ` Zang Roy-R61911 [this message] 2010-10-15 5:03 ` Zang Roy-R61911
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=3850A844E6A3854C827AC5C0BEC7B60A2B049B@zch01exm23.fsl.freescale.net \ --to=r61911@freescale.com \ --cc=B07421@freescale.com \ --cc=B11780@freescale.com \ --cc=B25806@freescale.com \ --cc=akpm@linux-foundation.org \ --cc=cbouatmailru@gmail.com \ --cc=dedekind1@gmail.com \ --cc=dwmw2@infradead.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linuxppc-dev@ozlabs.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.