All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	devel <devel@driverdev.osuosl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Fernando Guzman Lugo <fernando.lugo@ti.com>,
	Felipe Contreras <felipe.contreras@nokia.com>
Subject: Re: [PATCH 2/2] staging: tidspbridge: replace mbox callback with notifier_call
Date: Thu, 20 Jan 2011 11:52:54 -0800	[thread overview]
Message-ID: <20110120195254.GA1730@kroah.com> (raw)
In-Reply-To: <AANLkTinG5tQJ=aFHJDcLJnWX7RF3Jjru_pUqXXn4=wue@mail.gmail.com>

On Fri, Jan 14, 2011 at 04:53:25PM -0600, Ramirez Luna, Omar wrote:
> On Thu, Jan 13, 2011 at 11:34 PM, Omar Ramirez Luna <omar.ramirez@ti.com> wrote:
> > Lately, mailbox callbacks have been replaced by notifier block
> > call chains, this needs to be changed in the users of mailbox,
> > otherwise compilation will break due to missing parameters.
> 
> Please hold on applying this patch, it is not right as io_mbx_msg
> differs on what a notifier_call parameters and type should be.

Ok, I'll just queue up the 1st patch in this series.

greg k-h

  reply	other threads:[~2011-01-20 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  5:34 [PATCH 0/2] staging: tidspbridge for 2.6.38 Omar Ramirez Luna
2011-01-14  5:34 ` [PATCH 1/2] staging: tidspbridge: configure full L1 MMU range Omar Ramirez Luna
2011-01-14  5:34 ` [PATCH 2/2] staging: tidspbridge: replace mbox callback with notifier_call Omar Ramirez Luna
2011-01-14 22:53   ` Ramirez Luna, Omar
2011-01-20 19:52     ` Greg KH [this message]
2011-01-19 17:01 ` [PATCH 0/2] staging: tidspbridge for 2.6.38 Ramirez Luna, Omar

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=20110120195254.GA1730@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=felipe.contreras@nokia.com \
    --cc=fernando.lugo@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omar.ramirez@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.