From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ionut Nicu <ionut.nicu@mindbit.ro>
Cc: Greg KH <greg@kroah.com>, Ionut Nicu <ionut.nicu@gmail.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Fernando Guzman Lugo <x0095840@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] staging: tidspbridge: bugfixes
Date: Fri, 5 Nov 2010 19:54:58 +0200 [thread overview]
Message-ID: <AANLkTinLw7AvLszyOoThAtmUrnBcX9EGjbT3aQzMWsJe@mail.gmail.com> (raw)
In-Reply-To: <1288972825.9931.7.camel@atlantis.mindbit.ro>
On Fri, Nov 5, 2010 at 6:00 PM, Ionut Nicu <ionut.nicu@mindbit.ro> wrote:
> On Fri, 2010-11-05 at 08:43 -0700, Greg KH wrote:
>> On Fri, Nov 05, 2010 at 05:15:45PM +0200, Ionut Nicu wrote:
>> > Changes since v1:
>> >
>> > * Split the mgr_enum_node_info patch into two patches:
>> > one that fixes the issue and one that reorganizes the
>> > code.
>>
>> Are these for the .37 or .38 kernel?
>
> They're bug fixes, so I think they should get into .37. It's up to you
> to decide.
Other than patch #2, I agree it would be better on .37.
--
Felipe Contreras
prev parent reply other threads:[~2010-11-05 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 15:15 [PATCH v2 0/3] staging: tidspbridge: bugfixes Ionut Nicu
2010-11-05 15:15 ` [PATCH v2 1/3] staging: tidspbridge: fix mgr_enum_node_info Ionut Nicu
2010-11-05 16:01 ` Felipe Contreras
2010-11-05 16:09 ` Greg KH
2010-11-05 16:17 ` Ionut Nicu
2010-11-05 16:24 ` Greg KH
2010-11-05 15:15 ` [PATCH v2 2/3] staging: tidspbridge: mgr_enum_node_info cleanup Ionut Nicu
2010-11-05 15:15 ` [PATCH v2 3/3] staging: tidspbridge: fix kernel oops in bridge_io_get_proc_load Ionut Nicu
2010-11-05 15:43 ` [PATCH v2 0/3] staging: tidspbridge: bugfixes Greg KH
2010-11-05 16:00 ` Ionut Nicu
2010-11-05 17:54 ` Felipe Contreras [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=AANLkTinLw7AvLszyOoThAtmUrnBcX9EGjbT3aQzMWsJe@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=greg@kroah.com \
--cc=ionut.nicu@gmail.com \
--cc=ionut.nicu@mindbit.ro \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--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.