From: Grant Likely <grant.likely@secretlab.ca>
To: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
Cc: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
linux-kernel@vger.kernel.org,
alexander.stein@systec-electronic.com, qi.wang@intel.com,
yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com
Subject: Re: [PATCH 3/3] gpio-ml-ioh: Fix suspend/resume issue
Date: Wed, 5 Oct 2011 11:52:35 -0600 [thread overview]
Message-ID: <20111005175235.GC4205@ponder.secretlab.ca> (raw)
In-Reply-To: <4E8BB327.50306@dsn.lapis-semi.com>
On Wed, Oct 05, 2011 at 10:30:15AM +0900, Tomoya MORINAGA wrote:
> Hi Grant,
>
> (2011/10/05 1:07), Grant Likely wrote:
> >On Fri, Aug 05, 2011 at 01:04:22PM +0900, Tomoya MORINAGA wrote:
> >Can this one be merged without 1/3 and 2/3? Patch 2 looks like a
> >feature instead of a bug fix.
> >
>
> Is the above true ?
> I think,
> 1/3 is a bug fix.
> 2/3 and 3/3 are feature.
Considering that the title of 3/3 is "Fix suspend/resume issue", you
can understand my confusion. I'm not talking about 1/3 because it
looks like a trivial cleanup (not a bug fix).
> Do you mean you will merge only patch for a bug fix ?
> What will you do feature patch ?
I'll merge them regardless, I just need to know which branch to merge
them in. If patch 3 is a bug fix independent of patches 1 & 2, then
I'll put it in spi/merge and ask Linus to pull right away. Otherwise
I'll put it in spi/next along with patches 1 & 2.
g.
next prev parent reply other threads:[~2011-10-05 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 4:04 [PATCH 1/3] gpio-ml-ioh: Delete unnecessary code Tomoya MORINAGA
2011-08-05 4:04 ` [PATCH 2/3] gpio-ml-ioh: Support interrupt function Tomoya MORINAGA
2011-08-05 4:04 ` [PATCH 3/3] gpio-ml-ioh: Fix suspend/resume issue Tomoya MORINAGA
2011-10-04 16:07 ` Grant Likely
2011-10-05 1:30 ` Tomoya MORINAGA
2011-10-05 17:52 ` Grant Likely [this message]
2011-10-06 0:40 ` Tomoya MORINAGA
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=20111005175235.GC4205@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=alexander.stein@systec-electronic.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=tomoya-linux@dsn.lapis-semi.com \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=yong.y.wang@intel.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
Powered by JetHome