From: plaes@plaes.org (plaes at plaes.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-orion5x: Use hex2bin that is present in kernel lib
Date: Wed, 23 Nov 2011 16:26:57 +0200 [thread overview]
Message-ID: <1322058417.2472.9.camel@localhost.localdomain> (raw)
Hey!
I noticed there was some duplicate code under arm/mach-orion5x directory
so I ended up with a patch that uses existing library function present
in kernel code.
I regretfully have to admit that this patch is NOT even compile-tested,
but I hope that it still useful in case it happens to break something...
P?ikest,
Priit ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ARM-mach-orion5x-Use-hex2bin-that-is-present-in-kern.patch
Type: text/x-patch
Size: 3160 bytes
Desc:
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111123/fc6de17f/attachment.bin>
next reply other threads:[~2011-11-23 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 14:26 plaes at plaes.org [this message]
2011-11-24 6:40 ` [PATCH] ARM: mach-orion5x: Use hex2bin that is present in kernel lib Lennert Buytenhek
2011-11-24 9:49 ` plaes at plaes.org
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=1322058417.2472.9.camel@localhost.localdomain \
--to=plaes@plaes.org \
--cc=linux-arm-kernel@lists.infradead.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).