All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 2/2] mpc83xx:Fix MPC8349ITX SPD	RAMinitialization
Date: Tue, 24 Apr 2007 14:55:21 -0500	[thread overview]
Message-ID: <462E60A9.8040709@freescale.com> (raw)
In-Reply-To: <CF7E46FCFF66AD478BB72724345289EC279613@twx-exch01.twacs.local>

Benedict, Michael wrote:

> Sorry, for the mistake... I thought you _did_ write this patch in an
> email to the list about an hour ago.  *confused*. 

Well, that wasn't a patch, it was a suggestion.  There's a difference between telling 
someone how to write a patch, and actually writing it.  The latter is necessary for a 
signed-off-by line.

Also, I saw your other re-send of the original patch.  I think I may have not explained 
myself properly.  Here's how a patch is supposed to look:



Required description of patch goes here.  This text gets logged with the patch itself in 
the repo.

Signed-off-by lines here

---

Optional comment about the patch.  This text does *not* get logged with the patch.

git-generated data (list of files changed, diff lines, etc) goes here

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

      reply	other threads:[~2007-04-24 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 19:22 [U-Boot-Users] [PATCH 2/2] mpc83xx:Fix MPC8349ITX SPD RAM initialization Benedict, Michael
2007-04-24 19:25 ` Timur Tabi
2007-04-24 19:36   ` [U-Boot-Users] [PATCH 2/2] mpc83xx:Fix MPC8349ITX SPD RAMinitialization Benedict, Michael
2007-04-24 19:55     ` Timur Tabi [this message]

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=462E60A9.8040709@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.