From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: "Pakaravoor, Jagadeesh" <j-pakaravoor-l0cyMroinI0@public.gmane.org>
Cc: Ben Dooks <ben-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] I2C: OMAP: Add missing wakeup events
Date: Fri, 20 Feb 2009 10:42:44 -0800 [thread overview]
Message-ID: <20090220184243.GU7414@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02A3D4524D-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
* Pakaravoor, Jagadeesh <j-pakaravoor-l0cyMroinI0@public.gmane.org> [090202 07:28]:
> Hi,
> > Is it a necesary bugfix, or should it wait for the next merge window?
>
> You can line it up for the next merge window.
Just for references, I'm assuming that Ben has picked up this for his
queue, so not adding it to any of my ustream queues.
Acked-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Regards,
Tony
next prev parent reply other threads:[~2009-02-20 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 8:49 [PATCH] I2C: OMAP: Add missing wakeup events Pakaravoor, Jagadeesh
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02A39CF17B-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-02-02 7:17 ` Pakaravoor, Jagadeesh
2009-02-02 14:06 ` Ben Dooks
[not found] ` <20090202140606.GN8032-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-02-02 15:26 ` Pakaravoor, Jagadeesh
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02A3D4524D-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-02-20 18:42 ` Tony Lindgren [this message]
[not found] ` <20090220184243.GU7414-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-05-04 15:13 ` Jagadeesh Bhaskar Pakaravoor
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=20090220184243.GU7414@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=ben-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org \
--cc=j-pakaravoor-l0cyMroinI0@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: 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