From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ep93xx: fix build of vision_ep93xx.c
Date: Mon, 13 Feb 2012 07:01:37 +0000 [thread overview]
Message-ID: <201202130701.38027.arnd@arndb.de> (raw)
In-Reply-To: <201202130658.12505.arnd@arndb.de>
On Monday 13 February 2012, Arnd Bergmann wrote:
> It should indeed go through the arm-soc tree, I'm sorry for having
> been so unresponsive recently. Olof was taking care of the other
> pull requests and bug fixes but unfortunately was not on Cc on this
> one, so we both ended up missing it until now.
>
> I've applied it on the "fixes" branch of the arm-soc tree now, it
> will get sent to Linus on the next opportunity.
>
> I had a little trouble applying the patch from base64 format, but
> since you've had to wait so long already and I'm not completely sure
> which side the problem was on I took the time to recreate the diff
> from the base64 encoding and fix up the whitespace damage I got.
>
One more comment: if you want to ensure a patch or pull request
for arm-soc reaches us, please send it to arm at kernel.org. This should
let us make sure that at least one of us reacts in a way that you
deserve instead of letting it fall under the table.
Arnd
next prev parent reply other threads:[~2012-02-13 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:53 [PATCH] ep93xx: fix build of vision_ep93xx.c H Hartley Sweeten
2012-02-10 6:46 ` Mika Westerberg
2012-02-10 16:40 ` H Hartley Sweeten
2012-02-13 6:58 ` Arnd Bergmann
2012-02-13 7:01 ` Arnd Bergmann [this message]
2012-02-13 16:48 ` H Hartley Sweeten
-- strict thread matches above, loose matches on Subject: below --
2012-01-16 20:05 H Hartley Sweeten
2012-01-18 21:42 ` Ryan Mallon
2012-01-18 23:20 ` H Hartley Sweeten
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=201202130701.38027.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.