From: Anton Vorontsov <cbouatmailru@gmail.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: 최종환 <jhbird.choi@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] max8997_charger: Remove duplicate module.h
Date: Sat, 26 Nov 2011 03:34:36 +0400 [thread overview]
Message-ID: <20111125233436.GA19161@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <16505126.116361322047601084.JavaMail.weblogic@epml27>
On Wed, Nov 23, 2011 at 11:26:41AM +0000, MyungJoo Ham wrote:
> Sender : 최종환<jhbird.choi@samsung.com> S4(선임)/선임/S/W Solution개발팀(S.LSI)/삼성전자
> Date : 2011-11-23 13:40 (GMT+09:00)
> Title : [PATCH] max8997_charger: Remove duplicate module.h
> >
> > From: Jonghwan Choi <jhbird.choi@samsung.com>
> >
> > module.h was included twice.
> >
> > Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
The issue introduced in post-3.1 kernels, and since I don't want
to send it to Linus now (as it is not a regression fix), nor I want
to pull -rc kernels into battery GIT tree, I'll just let the patch
sit for awhile till 3.2 released. And during merge window I'll apply
it, just before sending pull request.
That is, I noticed the patch, it looks OK, and I'll apply it. Just
not now.
Thanks!
p.s.
The other option you have is to send the patch via -trivial tree.
I'm fine either way.
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2011-11-25 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 11:26 [PATCH] max8997_charger: Remove duplicate module.h MyungJoo Ham
2011-11-25 23:34 ` Anton Vorontsov [this message]
2012-01-06 0:59 ` Anton Vorontsov
-- strict thread matches above, loose matches on Subject: below --
2011-11-23 4:40 jhbird.choi
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=20111125233436.GA19161@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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