public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Pandita, Vikram" <vikram.pandita@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [APPLIED] [PATCH 2/2] OMAP: Zoom2: Fix file system loading issue
Date: Mon, 22 Jun 2009 15:43:39 +0300	[thread overview]
Message-ID: <20090622124338.GE7352@atomide.com> (raw)
In-Reply-To: <87ab45vdg8.fsf@deeprootsystems.com>

* Kevin Hilman <khilman@deeprootsystems.com> [090618 17:12]:
> Tony Lindgren <tony@atomide.com> writes:
> 
> > * Pandita, Vikram <vikram.pandita@ti.com> [090617 19:26]:
> >> 
> >> 
> >> >-----Original Message-----
> >> >From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
> >> >Sent: Wednesday, June 17, 2009 10:55 AM
> >> >To: Tony Lindgren; Pandita, Vikram
> >> >Cc: linux-omap@vger.kernel.org
> >> >Subject: Re: [APPLIED] [PATCH 2/2] OMAP: Zoom2: Fix file system loading issue
> >> >
> >> >Tony Lindgren <tony@atomide.com> writes:
> >> >
> >> >> This patch has been applied to the linux-omap
> >> >> by youw fwiendly patch wobot.
> >> >>
> >> >> Branch in linux-omap: omap-fixes
> >> >>
> >> >> Initial commit ID (Likely to change): f84eca35d44fd64cdde542f12d08eb04ca534954
> >> >>
> >> >> PatchWorks
> >> >> http://patchwork.kernel.org/patch/29668/
> >> >>
> >> >> Git (Likely to change, and takes a while to get mirrored)
> >> >> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-
> >> >2.6.git;a=commit;h=f84eca35d44fd64cdde542f12d08eb04ca534954
> >> >
> >> >Sorry, I didn't get to this beforethe merge, but $SUBJECT for this
> >> >patch is wrong and not terribly helpful.  It refers to the symptom, bu
> >> >tnot the root cause.
> >> >
> >> >It should be something like:
> >> >
> >> >OMAP3: Zoom2: pass IRQ triggering flags for serial driver
> >> 
> >> Yes that should have been the subject and 
> >> is put that way for the 8250 driver:
> >> http://lists.arm.linux.org.uk/lurker/attach/1@20090612.173251.776f9eda.attach
> >> 
> >> It's learning for next time.
> >
> > Will revert. I guess we now need two 8250 patches upstream? One for the
> > omap register define, and one for the interrupt flags?
> 
> Yes, both of these are pending on LKML, and still no word from Alan.
> 
> To get it upstream, I defined wake-up register locally in
> mach-omap2/serial.c until the patch gets merged, but for the interrupt
> flags there isn't an easy solution.

OK, so it's the irqflags that we still need. I took a look and commented that
we should rather have irqflags field in struct uart_port instead.. So let's
just wait and see until we have some ack from Alan.

Regards,

Tony

      reply	other threads:[~2009-06-22 12:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  0:49 [PATCH 2/2] OMAP: Zoom2: Fix file system loading issue Vikram Pandita
2009-06-17 13:57 ` [APPLIED] " Tony Lindgren
2009-06-17 15:19   ` Pandita, Vikram
2009-06-17 15:52     ` Kevin Hilman
2009-06-17 15:54   ` Kevin Hilman
2009-06-17 16:26     ` Pandita, Vikram
2009-06-18  5:27       ` Tony Lindgren
2009-06-18 13:32         ` Pandita, Vikram
2009-06-18 17:38           ` Kevin Hilman
2009-06-18 14:11         ` Kevin Hilman
2009-06-22 12:43           ` Tony Lindgren [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=20090622124338.GE7352@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vikram.pandita@ti.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