All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Lapin <slapin@ossfans.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Gusakov Andrey <dron0gus@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-samsung-soc@vger.kernel.org,
	Ben Dooks <ben-linux@fluff.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] S3C24XX DMA resume regression fix
Date: Fri, 20 Jan 2012 08:26:36 -0500	[thread overview]
Message-ID: <20120120132636.GC22732@build.ihdev.net> (raw)
In-Reply-To: <20120120121402.GM1068@n2100.arm.linux.org.uk>

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

WARNING: multiple messages have this Message-ID (diff)
From: slapin@ossfans.org (Sergey Lapin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] S3C24XX DMA resume regression fix
Date: Fri, 20 Jan 2012 08:26:36 -0500	[thread overview]
Message-ID: <20120120132636.GC22732@build.ihdev.net> (raw)
In-Reply-To: <20120120121402.GM1068@n2100.arm.linux.org.uk>

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

  reply	other threads:[~2012-01-20 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 13:47 [PATCH] S3C24XX DMA resume regression fix Gusakov Andrey
2012-01-13 13:47 ` Gusakov Andrey
2012-01-14 21:52 ` Sergei Shtylyov
2012-01-14 21:52   ` Sergei Shtylyov
2012-01-20 11:49   ` Sergey Lapin
2012-01-20 11:49     ` Sergey Lapin
2012-01-20 12:14     ` Russell King - ARM Linux
2012-01-20 12:14       ` Russell King - ARM Linux
2012-01-20 13:26       ` Sergey Lapin [this message]
2012-01-20 13:26         ` Sergey Lapin

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=20120120132636.GC22732@build.ihdev.net \
    --to=slapin@ossfans.org \
    --cc=ben-linux@fluff.org \
    --cc=dron0gus@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rjw@sisk.pl \
    --cc=sshtylyov@ru.mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.