From: Greg KH <gregkh@linuxfoundation.org>
To: Tony Prisk <linux@prisktech.co.nz>
Cc: vt8500-wm8505-linux-kernel@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk
Subject: Re: [GIT PULL v3] Fixes/cleanup for vt8500 serial
Date: Thu, 17 Jan 2013 17:27:15 -0800 [thread overview]
Message-ID: <20130118012715.GA29023@kroah.com> (raw)
In-Reply-To: <1358363143-7154-1-git-send-email-linux@prisktech.co.nz>
On Thu, Jan 17, 2013 at 08:05:39AM +1300, Tony Prisk wrote:
> Hi Greg,
>
> This should be the final pull request for this series, unless there are
> other review comments. Changelog included.
>
> v2:
> Restore the setting of vt8500_port->uart.uartclk which was dropped in v1.
> Corrected the return-on-fail of devm_request_and_ioremap to -EADDRNOTAVAIL.
>
> v3:
> Corrected the commit message for patch 3
>
>
> The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:
>
> Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)
>
> are available in the git repository at:
>
> git://server.prisktech.co.nz/git/linuxwmt.git tags/vt8500/serial-fixes
I don't take git pull requests for tiny stuff like this, sorry, only
patches through email.
But 2 of these patches had checkpatch issues, so I didn't take patches 3
and 4, please redo them.
thanks,
greg k-h
prev parent reply other threads:[~2013-01-18 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 19:05 Tony Prisk
2013-01-16 19:05 ` [PATCH 1/4 v3] serial: vt8500: Fix range-checking on vt8500_uart_ports Tony Prisk
2013-01-16 19:05 ` [PATCH 2/4 v3] serial: vt8500: ioremap'd resource is never freed Tony Prisk
2013-01-16 19:05 ` [PATCH 3/4 v3] serial: vt8500: UART uses gated clock rather than 24Mhz reference Tony Prisk
2013-01-18 1:25 ` Greg KH
2013-01-16 19:05 ` [PATCH 4/4 v3] serial: tty: Cleanup code using devm_ function Tony Prisk
2013-01-18 1:26 ` [PATCH 4/4 v3] serial: vt8500: " Greg KH
2013-01-18 1:27 ` Greg KH [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=20130118012715.GA29023@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@prisktech.co.nz \
--cc=vt8500-wm8505-linux-kernel@googlegroups.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®