From: slapin@ossfans.org (Sergey Lapin)
Date: Fri, 20 Jan 2012 08:26:36 -0500
Subject: [PATCH] S3C24XX DMA resume regression fix
In-Reply-To: <20120120121402.GM1068@n2100.arm.linux.org.uk>
References: <1326462444-10567-1-git-send-email-dron0gus@gmail.com>
 <4F11F911.7030609@ru.mvista.com>
 <20120120114902.GB22732@build.ihdev.net>
 <20120120121402.GM1068@n2100.arm.linux.org.uk>
Message-ID: <20120120132636.GC22732@build.ihdev.net>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

> > > >In commit bb072c3cf21d1c9a5a2eeb5a00679ee7bf39675b suspend/resume
> > > 
> > >    Please also specify that commit's summary in parens.
> > 
> > Could you please point me in direction of patch submission
> > guide where that is explained.
> 
> It's something that's been asked for by Linus - and as Linus can refuse
> to pull anything he doesn't like, it's something that we'd better satisfy
> if we want patches to hit mainline.
> 
> Like everything in kernel development, what's written in documentation is
> never the full story; things change through discussions on mailing lists,
> new guidelines get created, and the documents become stale.  That's the
> nature of this.
...
> The point is that if you include a commit ID, then you should include
> the summary, so people reading the commit message don't have to faff
> around trying to find out what you're referring to.
> 
> See, for example, http://lkml.org/lkml/2010/6/1/498

Thanks a lot for good explanation,

S.