From: Greg KH <greg@kroah.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org,
Stephen Street <stephen@streetfiresound.com>,
Andrew Morton <akpm@osdl.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 09/10] spi: Update to PXA2xx SPI Driver
Date: Tue, 16 May 2006 18:40:10 -0700 [thread overview]
Message-ID: <20060517014010.GA1800@kroah.com> (raw)
In-Reply-To: <adamzvu9fhf.fsf@cisco.com>
On Fri, Dec 31, 2004 at 04:10:04PM -0800, Roland Dreier wrote:
> This is kind of a weird way to do things: the PXA2xx SPI driver was
> just added in patch 2/10. Why merge a known-buggy driver and then fix
> it as part of the same merge?
Because it was built up as a series of patches, and I didn't merge any
of them together like I should have :)
Anyway, David will be taking care of these now, so hopefully stuff like
this will not happen again.
thanks,
greg k-h
next prev parent reply other threads:[~2006-05-17 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 21:37 [GIT PATCH] SPI patches for 2.6.17-rc4 Greg KH
2006-05-16 21:38 ` [PATCH 01/10] SPI: per-transfer overrides for wordsize and clocking Greg KH
2006-05-16 21:38 ` [PATCH 02/10] SPI: add PXA2xx SSP SPI Driver Greg KH
2006-05-16 21:38 ` [PATCH 03/10] SPI: spi whitespace fixes Greg KH
2006-05-16 21:38 ` [PATCH 04/10] SPI: spi bounce buffer has a minimum length Greg KH
2006-05-16 21:38 ` [PATCH 05/10] SPI: Add David as the SPI subsystem maintainer Greg KH
2006-05-16 21:38 ` [PATCH 06/10] SPI: Renamed bitbang_transfer_setup to spi_bitbang_setup_transfer and export it Greg KH
2006-05-16 21:38 ` [PATCH 07/10] SPI: devices can require LSB-first encodings Greg KH
2006-05-16 21:38 ` [PATCH 08/10] SPI: busnum == 0 needs to work Greg KH
2006-05-16 21:38 ` [PATCH 09/10] spi: Update to PXA2xx SPI Driver Greg KH
2005-01-01 0:10 ` Roland Dreier
2006-05-17 1:40 ` Greg KH [this message]
2006-05-16 21:38 ` [PATCH 10/10] SPI: spi_bitbang: clocking fixes Greg KH
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=20060517014010.GA1800@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=stephen@streetfiresound.com \
/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