From: Greg KH <greg@kroah.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-serial@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
uclinux-dist-devel@blackfin.uclinux.org,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH] serial: bfin_5xx: move resources into board files
Date: Thu, 28 Oct 2010 11:11:33 -0700 [thread overview]
Message-ID: <20101028181133.GC2573@kroah.com> (raw)
In-Reply-To: <1288167527-31648-1-git-send-email-vapier@gentoo.org>
On Wed, Oct 27, 2010 at 04:18:47AM -0400, Mike Frysinger wrote:
> From: Sonic Zhang <sonic.zhang@analog.com>
>
> Rather than maintain Kconfig entries where people have to enter raw
> numbers and hardcode lists of addresses/pins in the driver itself,
> push it all to platform resources. This lets us simplify the driver,
> the Kconfig, and gives board porters greater flexibility.
>
> In the process, we need to also start supporting the early platform
> interface. Not a big deal, but it causes the patch to be bigger than
> a simple resource relocation.
>
> All the Blackfin boards already have their resources updated and in
> place for this change.
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> Note: this is for 2.6.38 ... it depends on a Blackfin clean up patch
> that i'll be merging at the start of the 2.6.38 cycle. looking
> for feedback here and/or just an Ack so i may merge it through my
> Blackfin tree with the related changes.
Fine with me, feel free to merge it through your tree for .38 with a:
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
for it.
thanks,
greg k-h
prev parent reply other threads:[~2010-10-28 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 8:18 [PATCH] serial: bfin_5xx: move resources into board files Mike Frysinger
2010-10-28 18:11 ` 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=20101028181133.GC2573@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-serial@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.