linux-kernel - Re: [PATCH] max8997_charger: Remove duplicate module.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 26 Nov 2011 03:34:36 +0400
From:	Anton Vorontsov <cbouatmailru@...il.com>
To:	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	최종환 <jhbird.choi@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] max8997_charger: Remove duplicate module.h

On Wed, Nov 23, 2011 at 11:26:41AM +0000, MyungJoo Ham wrote:
> Sender : 최종환<jhbird.choi@...sung.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@...sung.com>
> > 
> > module.h was included twice.
> > 
> > Signed-off-by: Jonghwan Choi <jhbird.choi@...sung.com>
> 
> Acked-by: MyungJoo Ham <myungjoo.ham@...sung.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@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/