linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] SPI patches for 2.6.15
Date: Sun, 15 Jan 2006 08:56:32 +0900	[thread overview]
Message-ID: <dqc33h$5bv$1@sea.gmane.org> (raw)
In-Reply-To: <20060114112013.GA11446@vrfy.org>

Kay Sievers wrote:
> On Sat, Jan 14, 2006 at 01:48:30PM +0900, Kalin KOZHUHAROV wrote:
>> Greg KH wrote:
>>> Here are a few patches for 2.6.15 that add a SPI driver subsystem to the
>>> kernel tree.
> 
>>> Please pull from:
>>> 	rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/spi-2.6.git/
> 
>> May be just a browser accessible URL for Documentation/spi/spi-summary or at
>> least a definition of SPI in the header of the mail.
>>
>> git is just too complex for me at htemoment (haven't found the time to learn it)
> 
> If the git web interface is "too complex" for you, then you may not
> need to know what SPI is too. :)
> 
>   http://www.kernel.org/git/?p=linux/kernel/git/gregkh/spi-2.6.git;a=commitdiff;h=8ae12a0d85987dc138f8c944cb78a92bf466cea0


Thank you for the link, it turns I wasn't right about the meaning...
What I had in mind is to include say the beginning two lines of
Documentation/spi/spi-summary in the first mail (the usual procedure for
patch-00 as I can see):

The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
link used to connect microcontrollers to sensors, memory, and peripherals.

I always give the -ck patches as an example: even if you don't know what are
they about, what does -ck mean and so on, just reading the first one or two
sentences is enough to decide: to read on or to go next thread.

By seeing this most people will be able to decide whether there are
interested or not and those who are interested should spend the time to find
the patch (learn to use git if needed), etc.

I know we are not talking Web design here, but "Don't let me think" is an
excellent book that I just finished and it teaches exactly what the title
says is a good design, not only web.

And I know Greg posts and comments and everything is very professional, I
know basically who he is and how important he is. /me is mostly reading here
and trying to be helpful, eventually asking for help/explanation of issues I
run into.

Thank you again for the time.

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  reply	other threads:[~2006-01-14 23:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14  0:44 [GIT PATCH] SPI patches for 2.6.15 Greg KH
2006-01-14  0:46 ` [PATCH] spi: mtd dataflash driver Greg KH
2006-01-14  0:46   ` [PATCH] spi: simple SPI framework Greg KH
2006-01-14  0:46     ` [PATCH] spi: add spi_driver to " Greg KH
2006-01-14  0:46       ` [PATCH] spi: ads7846 driver Greg KH
2006-01-14  0:46         ` [PATCH] SPI core tweaks, bugfix Greg KH
2006-01-14  0:46           ` [PATCH] spi: ads7836 uses spi_driver Greg KH
2006-01-14  0:46             ` [PATCH] spi: M25 series SPI flash Greg KH
2006-01-14  0:46               ` [PATCH] spi: add spi_bitbang driver Greg KH
2006-01-14  0:46                 ` [PATCH] SPI: add spi_butterfly driver Greg KH
2006-01-14  0:46                   ` [PATCH] spi: remove fastcall crap Greg KH
2006-01-14  0:46                     ` [PATCH] spi: misc fixes Greg KH
2006-01-14  0:46                       ` [PATCH] spi: use linked lists rather than an array Greg KH
2006-01-14  4:48 ` [GIT PATCH] SPI patches for 2.6.15 Kalin KOZHUHAROV
2006-01-14 11:20   ` Kay Sievers
2006-01-14 23:56     ` Kalin KOZHUHAROV [this message]
     [not found]     ` <fa.fl6o99l.132m0gn@ifi.uio.no>
2006-01-15 14:27       ` Kai Henningsen
2006-01-16  2:30         ` Kalin KOZHUHAROV

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='dqc33h$5bv$1@sea.gmane.org' \
    --to=kalin@thinrope.net \
    --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;
as well as URLs for NNTP newsgroup(s).