From: Russ Gorby <russ.gorby@intel.com>
To: Russ Gorby <russ.gorby@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Cc: suhail.ahmed@intel.com
Subject: [PATCH 0/6] IFX6X60 patchset : 02/07/2011
Date: Mon, 7 Feb 2011 12:02:26 -0800 [thread overview]
Message-ID: <1297108952-27371-1-git-send-email-russ.gorby@intel.com> (raw)
In-Reply-To: <[PATCH 0/6] IFX6X60 patchset : 02/07/2011>
Hello SPI/Serial Maintainers,
I am sending a patchset for the ifx6x60 driver to be considered for
inclusion in the Linux kernel.
Patches were made against the following GIT repo
http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
pull date: ~2/4/2011
A breif description of the patches follows:
[PATCH 1/6] serial: ifx6x60: fixed call to tty_port_init
- fixed order of setting port ops
[PATCH 2/6] serial: ifx6x60: dma_alloc_coherent must use parent dev
- fixed device for which the allocation is made
[PATCH 3/6] serial: ifx6x60: changed internal bpw from boolean to int
[PATCH 4/6] serial: ifx6x60: set SPI max_speed_hz based on platform type
- set max speed based on platform data
[PATCH 5/6] serial: ifx6x60: probe routine needs to call spi_setup
- configured spi for the h/w device
[PATCH 6/6] serial: ifx6x60: cleanup
next parent reply other threads:[~2011-02-07 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 0/6] IFX6X60 patchset : 02/07/2011>
2011-02-07 20:02 ` Russ Gorby [this message]
2011-02-07 20:02 ` [PATCH 1/6] serial: ifx6x60: fixed call to tty_port_init Russ Gorby
2011-02-07 20:02 ` [PATCH 2/6] serial: ifx6x60: dma_alloc_coherent must use parent dev Russ Gorby
2011-02-07 20:02 ` [PATCH 3/6] serial: ifx6x60: changed internal bpw from boolean to int Russ Gorby
2011-02-07 20:02 ` [PATCH 4/6] serial: ifx6x60: set SPI max_speed_hz based on platform type Russ Gorby
2011-02-07 20:02 ` [PATCH 5/6] serial: ifx6x60: probe routine needs to call spi_setup Russ Gorby
2011-02-07 20:02 ` [PATCH 6/6] serial: ifx6x60: minor cleanup Russ Gorby
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=1297108952-27371-1-git-send-email-russ.gorby@intel.com \
--to=russ.gorby@intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=suhail.ahmed@intel.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
all inboxes | Powered by JetHome®