linux-kernel - RE: [PATCH 1/3] regulator: fix wrong header name in description

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] [day] [month] [year] [list]

Message-ID: <B567DBAB974C0544994013492B949F8E381301287B@EXMAIL03.scwf.nsc.com>
Date:	Thu, 16 Feb 2012 23:17:22 -0800
From:	"Kim, Milo" <Milo.Kim@...com>
To:	"Mark Brown" <broonie@...nsource.wolfsonmicro.com>
cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] regulator: fix wrong header name in description

OK, thanks for your advice.
Then should I resend other two patches based on linux-next tree ?

Milo -

> -----Original Message-----
> From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
> Sent: Friday, February 17, 2012 4:10 PM
> To: Kim, Milo
> Cc: linux-kernel@...r.kernel.org
> Subject: Re: [PATCH 1/3] regulator: fix wrong header name in
> description
> 
> On Thu, Feb 16, 2012 at 10:41:32PM -0800, Kim, Milo wrote:
> > The 'mode' is defined in consumer.h.
> >
> > * patch base version : linux-3.2.4
> 
> Applied, thanks, but you should only include administrative stuff like
> the above after the ---.  You should also always submit patches against
> either Linus' tree (for fixes) or -next (for everything else) rather
> than an old kernel.

--
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/