Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]

> If it is indeed the case that this architecture is used internally by a
> single organisation then perhaps it doesn't make sense for us to merge it.

Disagree, as does history. We merged the AP1000 ... 

> distribution: to get it into the hands of people who need it.  But in this
> situation there is no advantage to *anyone* from this merge apart from MEI.

Or anyone who wants to hack an MEI device. If just three people do then
it beats voyager ;)

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
  - From: Andrew Morton <[email protected]>
- [PATCH 0/6] MN10300: Add the MN10300 architecture to Linux kernel [try #5]
  - From: David Howells <[email protected]>
- Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
  - From: David Howells <[email protected]>
- Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: Fw: Buffer overflow in CIFS VFS.
Next by Date: Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
Previous by thread: Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
Next by thread: Re: [PATCH 5/6] MN10300: Add the MN10300/AM33 architecture to the kernel [try #5]
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]