mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Hu Mingkai-B21284 <B21284@freescale.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Kumar Gala <galak@kernel.crashing.org>
Subject: Re: spi_fsl_spi broken when compiled as module by b36ece832512c1a0afa54ff0a56d63492a1caf08
Date: Mon, 16 May 2011 12:52:17 -0400	[thread overview]
Message-ID: <20110516165217.GJ21345@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <9389EE59E16E9447AFB481039183BCF411AA99@039-SN1MPN1-005.039d.mgd.msft.net>

On Mon, May 16, 2011 at 02:10:25AM +0000, Hu Mingkai-B21284 wrote:
> You can prepare the patch using git tool and send it to the maillist.
> Also add spi-devel-general@lists.sourceforge.net maillist.

Well I did prepare it with git the same way I have done all the other
patches I have sent of the last number of years.  No one has ever had
a problem with that.

If you mean have git send the email, then no that isn't going to happen
ever.  I don't run git on a machine that sends mail, and I don't run
git on the machine I do my email on.

The email is a valid patch, my email client doesn't screw up white space,
so there is no problem.

-- 
Len Sorensen

  parent reply	other threads:[~2011-05-16 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 15:52 Lennart Sorensen
2011-05-11 17:03 ` Lennart Sorensen
2011-05-12  1:33 ` Hu Mingkai-B21284
2011-05-12 15:11   ` Lennart Sorensen
2011-05-16  2:10     ` Hu Mingkai-B21284
2011-05-16  2:17       ` Randy Dunlap
2011-05-16 16:52       ` Lennart Sorensen [this message]
2011-05-16 18:17     ` Grant Likely
2011-05-16 19:52       ` Lennart Sorensen
2011-05-16 20:01         ` Grant Likely

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=20110516165217.GJ21345@caffeine.csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=B21284@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®