From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SH/Dreamcast - improve detection of attached
Date: Tue, 12 Feb 2008 09:36:12 +0000 [thread overview]
Message-ID: <20080212103612.be92e70a.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <1202689502.6237.23.camel@localhost.localdomain>
On Tue, 12 Feb 2008 17:24:25 +0900
Paul Mundt <lethal@linux-sh.org> wrote:
> On Mon, Feb 11, 2008 at 12:25:02AM +0000, Adrian McMenamin wrote:
> > Improve device detection for maple through longer delay
> >
> > Experience suggests that a much longer delay in setting up the Maple bus
> > on the Dreamcast leads to better hardware detection.
> >
> > Signed-off-by: Adrian McMenamin <adrian@mcmen.demon.co.uk>
> >
> > -----
> >
> 3 -'s only. Not 5, 3.
>
> Patch subjects should follow the format of 'subsystem: description'. In
> this case, 'maple: improve detection of attached peripherals'.
>
> On Mon, Feb 11, 2008 at 06:41:49PM +0100, Kristoffer Ericson wrote:
> > Greetings,
> >
> > shortlog:
> > This patch removes defunct. led support functions from hp6xx.h since they are now
> > added in a proper driver (see commit below). Also adds tabs instead of spaces before comments.
> >
> > *commit d39a7a63eb3971b1b3cc5c181ed526bf437b1c72
> >
> This goes directly in to the commit log. You do not need a greeting, and
> you do not need a shortlog:. Provide a meaningful subject, and then a
> short and concise description in the body, nothing more, and nothing
> less. Also, please ensure that you do not go beyond 80 cols in the text
> of your body. This not only applies to patch descriptions, but also to
> any mail you send to the list.
>
Ah, that I didn't know. Thought everything after the shortlog was
automaticly cut&pasted. Thx.
> Also, no attachments or MIME damage of any sort. If you aren't sure
> whether your mailer will mangle the inline patch or not, send it to
> yourself until you have it working.
I wasn't aware my attachments was being mangled in anyway, I'll test on
myself until I got it sorted.
>
> > signed-off-by: Kristoffer Ericson <kristoffer.ericson@gmail.com>
> >
> Signed-off-by. With an upper-case S.
Roger.
>
> I suggest you both re-read Documentation/SubmittingPatches and look out
> for deviations. This stuff is documented incredibly clearly, and yet
> there is constant trouble with this for whatever reason. Beyond that,
> please try applying your patches to a test tree with git-am _before_
> sending it to the list. You will very quickly see what needs to be
> corrected.
>
> I don't mind fixing these things up and merging the patches by hand from
> time to time, but when every single patch submission requires manual
> mangling, it simply gets to be a headache.
>
> Please try to follow the established conventions in the future. It will
> save everyone a lot of time.
Thx for info paul. I'll do that.
next prev parent reply other threads:[~2008-02-12 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 0:25 [PATCH] SH/Dreamcast - improve detection of attached peripherals Adrian McMenamin
2008-02-12 8:24 ` Paul Mundt
2008-02-12 9:36 ` Kristoffer Ericson [this message]
2008-02-12 9:48 ` Paul Mundt
2008-02-12 15:23 ` Mike Frysinger
2008-02-13 13:24 ` [PATCH] SH/Dreamcast - improve detection of attached Adrian McMenamin
2008-02-13 13:30 ` Adrian McMenamin
2008-02-14 9:34 ` Kristoffer Ericson
2008-02-14 10:14 ` [PATCH] SH/Dreamcast - improve detection of attached peripherals Paul Mundt
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=20080212103612.be92e70a.Kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=linux-sh@vger.kernel.org \
/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