From: Tom Rini <trini@kernel.crashing.org>
To: Takeharu KATO <kato.takeharu@jp.fujitsu.com>
Cc: linuxppc-dev@ozlabs.org, tmm@tmm.dk
Subject: Re: [PATCH] boot time scheduling w hile atomic fix
Date: Wed, 16 Mar 2005 18:47:12 -0700 [thread overview]
Message-ID: <20050317014711.GE8345@smtp.west.cox.net> (raw)
In-Reply-To: <4238D681.1040003@jp.fujitsu.com>
On Thu, Mar 17, 2005 at 09:59:45AM +0900, Takeharu KATO wrote:
> Hi Tom:
>
> Thank you for your response.
>
> >This is a great first start. But please see
> >Documentation/SubmittingPatches and provide a Signed-off-by line and
> >resubmit. Thanks!
> >
> IIRC, I alreday added the Signed-off-by line.
> And moreI made the patch with "diff -Nupr".
> What's wrong with my mail?
My fault, sorry.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2005-03-17 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 10:24 [PATCH] boot time scheduling w hile atomic fix Takeharu KATO
2005-03-16 22:19 ` Tom Rini
2005-03-17 0:59 ` Takeharu KATO
2005-03-17 1:47 ` Tom Rini [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=20050317014711.GE8345@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=kato.takeharu@jp.fujitsu.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tmm@tmm.dk \
/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;
as well as URLs for NNTP newsgroup(s).