All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Fernando Guzman Lugo <x0095840@ti.com>
Cc: felipe.contreras@nokia.com, Hiroshi.DOYU@nokia.com,
	linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] staging: tidspbridge - misc fixes
Date: Mon, 25 Oct 2010 21:06:19 -0700	[thread overview]
Message-ID: <20101026040619.GA8549@suse.de> (raw)
In-Reply-To: <1288054306-4361-1-git-send-email-x0095840@ti.com>

On Mon, Oct 25, 2010 at 07:51:38PM -0500, Fernando Guzman Lugo wrote:
> This set of patches fix some issues found in lastest tree.
> 
> Fernando Guzman Lugo (8):
>   staging: tidspbridge - remove req_addr from proc_map
>   staging: tidspbridge - add kconfig parameter for DMM size
>   staging: tidspbridge - change mmufault tasklet to a workqueue
>   staging: tidspbridge - fix timeout in dsp_gpt_wait_overflow
>   staging: tidspbridge - use GTP7 for DSP stack dump
>   staging: tidspbridge - remove disabling twl when printing DSP stack
>   staging: tidspbridge - fix some issues after iommu patches
>   staging: tidspbridge - make sync_wait_on_event interruptible

Are any of these really applicable for .37 after .37-rc1?  Or can they
wait for .38?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] staging: tidspbridge - misc fixes
Date: Mon, 25 Oct 2010 21:06:19 -0700	[thread overview]
Message-ID: <20101026040619.GA8549@suse.de> (raw)
In-Reply-To: <1288054306-4361-1-git-send-email-x0095840@ti.com>

On Mon, Oct 25, 2010 at 07:51:38PM -0500, Fernando Guzman Lugo wrote:
> This set of patches fix some issues found in lastest tree.
> 
> Fernando Guzman Lugo (8):
>   staging: tidspbridge - remove req_addr from proc_map
>   staging: tidspbridge - add kconfig parameter for DMM size
>   staging: tidspbridge - change mmufault tasklet to a workqueue
>   staging: tidspbridge - fix timeout in dsp_gpt_wait_overflow
>   staging: tidspbridge - use GTP7 for DSP stack dump
>   staging: tidspbridge - remove disabling twl when printing DSP stack
>   staging: tidspbridge - fix some issues after iommu patches
>   staging: tidspbridge - make sync_wait_on_event interruptible

Are any of these really applicable for .37 after .37-rc1?  Or can they
wait for .38?

thanks,

greg k-h

  parent reply	other threads:[~2010-10-26  4:05 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  0:51 [PATCH 0/8] staging: tidspbridge - misc fixes Fernando Guzman Lugo
2010-10-26  0:51 ` Fernando Guzman Lugo
2010-10-26  0:51 ` Fernando Guzman Lugo
2010-10-26  0:51 ` [PATCH 1/8] staging: tidspbridge - remove req_addr from proc_map Fernando Guzman Lugo
2010-10-26  0:51   ` Fernando Guzman Lugo
2010-10-26  0:51   ` Fernando Guzman Lugo
2010-10-26  0:51   ` [PATCH 2/8] staging: tidspbridge - add kconfig parameter for DMM size Fernando Guzman Lugo
2010-10-26  0:51     ` Fernando Guzman Lugo
2010-10-26  0:51     ` Fernando Guzman Lugo
2010-10-26  0:51     ` [PATCH 3/8] staging: tidspbridge - change mmufault tasklet to a workqueue Fernando Guzman Lugo
2010-10-26  0:51       ` Fernando Guzman Lugo
2010-10-26  0:51       ` Fernando Guzman Lugo
2010-10-26  0:51       ` [PATCH 4/8] staging: tidspbridge - fix timeout in dsp_gpt_wait_overflow Fernando Guzman Lugo
2010-10-26  0:51         ` Fernando Guzman Lugo
2010-10-26  0:51         ` Fernando Guzman Lugo
2010-10-26  0:51         ` [PATCH 5/8] staging: tidspbridge - use GTP7 for DSP stack dump Fernando Guzman Lugo
2010-10-26  0:51           ` Fernando Guzman Lugo
2010-10-26  0:51           ` Fernando Guzman Lugo
2010-10-26  0:51           ` [PATCH 6/8] staging: tidspbridge - remove disabling twl when printing DSP stack Fernando Guzman Lugo
2010-10-26  0:51             ` Fernando Guzman Lugo
2010-10-26  0:51             ` Fernando Guzman Lugo
2010-10-26  0:51             ` [PATCH 7/8] staging: tidspbridge - fix some issues after iommu patches Fernando Guzman Lugo
2010-10-26  0:51               ` Fernando Guzman Lugo
2010-10-26  0:51               ` Fernando Guzman Lugo
2010-10-26  0:51               ` [PATCH 8/8] staging: tidspbridge - make sync_wait_on_event interruptible Fernando Guzman Lugo
2010-10-26  0:51                 ` Fernando Guzman Lugo
2010-10-26  0:51                 ` Fernando Guzman Lugo
2010-10-26  0:58                 ` Felipe Contreras
2010-10-26  0:58                   ` Felipe Contreras
2010-10-26 15:50                   ` Guzman Lugo, Fernando
2010-10-26 15:50                     ` Guzman Lugo, Fernando
2010-10-26 15:50                     ` Guzman Lugo, Fernando
2010-10-26 17:03                     ` Felipe Contreras
2010-10-26 17:03                       ` Felipe Contreras
2010-10-26 17:58                       ` Guzman Lugo, Fernando
2010-10-26 17:58                         ` Guzman Lugo, Fernando
2010-10-26 17:58                         ` Guzman Lugo, Fernando
2010-10-26 19:27                         ` Felipe Contreras
2010-10-26 19:27                           ` Felipe Contreras
2010-10-26 20:01                           ` Guzman Lugo, Fernando
2010-10-26 20:01                             ` Guzman Lugo, Fernando
2010-10-26 20:01                             ` Guzman Lugo, Fernando
2010-12-06  8:51                   ` Ramirez Luna, Omar
2010-12-06  8:51                     ` Ramirez Luna, Omar
2010-10-26 11:46   ` [PATCH 1/8] staging: tidspbridge - remove req_addr from proc_map Felipe Contreras
2010-10-26 11:46     ` Felipe Contreras
2010-10-26 15:52     ` Guzman Lugo, Fernando
2010-10-26 15:52       ` Guzman Lugo, Fernando
2010-10-26 15:52       ` Guzman Lugo, Fernando
2010-10-26 17:07       ` Felipe Contreras
2010-10-26 17:07         ` Felipe Contreras
2010-10-26 18:08         ` Guzman Lugo, Fernando
2010-10-26 18:08           ` Guzman Lugo, Fernando
2010-10-26 18:08           ` Guzman Lugo, Fernando
2010-10-26 19:37           ` Felipe Contreras
2010-10-26 19:37             ` Felipe Contreras
2010-10-26 20:39             ` Guzman Lugo, Fernando
2010-10-26 20:39               ` Guzman Lugo, Fernando
2010-10-26 20:39               ` Guzman Lugo, Fernando
2010-10-27  8:19               ` Felipe Contreras
2010-10-27  8:19                 ` Felipe Contreras
2010-10-27  8:19                 ` Felipe Contreras
2010-10-28 15:38                 ` Guzman Lugo, Fernando
2010-10-28 15:38                   ` Guzman Lugo, Fernando
2010-10-28 15:38                   ` Guzman Lugo, Fernando
2010-10-28 15:56                 ` Russell King - ARM Linux
2010-10-28 15:56                   ` Russell King - ARM Linux
2010-10-28 15:56                   ` Russell King - ARM Linux
2010-10-26  4:06 ` Greg KH [this message]
2010-10-26  4:06   ` [PATCH 0/8] staging: tidspbridge - misc fixes Greg KH
2010-10-26 14:43   ` Felipe Contreras
2010-10-26 14:43     ` Felipe Contreras
2010-10-26 14:55     ` Omar Ramirez Luna
2010-10-26 14:55       ` Omar Ramirez Luna
2010-10-26 14:55       ` Omar Ramirez Luna
2010-10-26 15:46     ` Guzman Lugo, Fernando
2010-10-26 15:46       ` Guzman Lugo, Fernando
2010-10-26 15:46       ` Guzman Lugo, Fernando

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=20101026040619.GA8549@suse.de \
    --to=gregkh@suse.de \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=felipe.contreras@nokia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=x0095840@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 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.