From: stigge@antcom•de (Roland Stigge)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] usb: change the dependency chain for LPC32XX and ISP1301
Date: Thu, 23 Aug 2012 10:18:39 +0200 [thread overview]
Message-ID: <5035E75F.5080801@antcom.de> (raw)
In-Reply-To: <5035D9E0.1000905@linutronix.de>
On 08/23/2012 09:21 AM, Sebastian Andrzej Siewior wrote:
> On 08/23/2012 12:16 AM, Roland Stigge wrote:
>> This issue could be resolved in a different way: Have you followed the
>> discussion at linux-arm-kernel at lists.infradead.org on 2012-08-20,
>> Subject "i2c: pnx: Fix bit definitions"? If nothing unexpected turns
>> out, PNX4008 should probably be removed altogether. (Practically
>> abandoned arch for 6 years.) Easily possible for v3.7.
>
> Ach. I assumed that is being merged. The PNX arch does not define
> USB_ARCH_HAS_OHCI so I goes that you can't select it there?
Yes, this issue will be gone also.
>> Then, the resulting solution is much simpler and Sebastian's patch
>> obsolete.
>
> That would be what?
Well, your idea won't be obsolete completely. :-) But much simpler
without all the "PNX4008 || LPC32XX" stuff. Following Alan's proposal,
I'd prefer not introducing new symbols, and much of the "PNX4008 ||
LPC32XX" logic won't be necessary anymore.
For the PNX4008 removal - should I already post a patch to build the
respective changes on top of, without PNX4008 references?
Thanks,
Roland
next prev parent reply other threads:[~2012-08-23 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1208221537260.1328-100000@iolanthe.rowland.org>
2012-08-22 22:16 ` [PATCH 1/2] usb: change the dependency chain for LPC32XX and ISP1301 Roland Stigge
2012-08-23 7:21 ` Sebastian Andrzej Siewior
2012-08-23 8:18 ` Roland Stigge [this message]
2012-08-23 8:29 ` Sebastian Andrzej Siewior
2012-08-23 8:59 ` Roland Stigge
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=5035E75F.5080801@antcom.de \
--to=stigge@antcom$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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