From: jason@lakedaemon.net (Jason)
To: linux-arm-kernel@lists.infradead.org
Subject: revert merge commit de68f28 in for-next?
Date: Tue, 6 Mar 2012 09:44:15 -0500 [thread overview]
Message-ID: <20120306144415.GR5050@titan.lakedaemon.net> (raw)
Arnd,
As much as I'd love to see this go in right now, I don't think it's the
correct version (from Mar 2). This is the merge commit in question:
de68f2847fa759df54e9d8eb0013a0f8ea959c22
It's missing several fixes, #ifdef CONFIG_OF around struct of_device_id,
marvell -> mrvl in compatible properties, etc.
Would you like me to submit a new pull request, or base my fixes off of
this and submit new patches?
Thanks and sorry for the confusion,
Jason.
next reply other threads:[~2012-03-06 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 14:44 Jason [this message]
2012-03-06 16:04 ` revert merge commit de68f28 in for-next? Arnd Bergmann
2012-03-06 16:29 ` Jason
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=20120306144415.GR5050@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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