On 09/15/2014 09:55 PM, Arnd Bergmann wrote:
> On Sunday 14 September 2014, Chen Gang wrote:
>> Hello Maintainers:
>>
>> Is this patch worthy enough to be applied?
>>
>> Welcome any ideas, suggestions or completions.
>
> I find it hard to judge whether it's worth it or not. You gave one example
>
On Sunday 14 September 2014, Chen Gang wrote:
> Hello Maintainers:
>
> Is this patch worthy enough to be applied?
>
> Welcome any ideas, suggestions or completions.
I find it hard to judge whether it's worth it or not. You gave one example
for a driver that needs this, but what would be your
On Sunday 14 September 2014, Chen Gang wrote:
Hello Maintainers:
Is this patch worthy enough to be applied?
Welcome any ideas, suggestions or completions.
I find it hard to judge whether it's worth it or not. You gave one example
for a driver that needs this, but what would be your
On 09/15/2014 09:55 PM, Arnd Bergmann wrote:
On Sunday 14 September 2014, Chen Gang wrote:
Hello Maintainers:
Is this patch worthy enough to be applied?
Welcome any ideas, suggestions or completions.
I find it hard to judge whether it's worth it or not. You gave one example
for a driver
Hello Maintainers:
Is this patch worthy enough to be applied?
Welcome any ideas, suggestions or completions.
Thanks.
On 09/03/2014 07:47 PM, Chen Gang wrote:
> On 09/02/2014 02:13 PM, Chen Gang wrote:
>> On 9/2/14 13:17, Paul Gortmaker wrote:
>>>
>>> OK, but that was not at _all_ what I
Hello Maintainers:
Is this patch worthy enough to be applied?
Welcome any ideas, suggestions or completions.
Thanks.
On 09/03/2014 07:47 PM, Chen Gang wrote:
On 09/02/2014 02:13 PM, Chen Gang wrote:
On 9/2/14 13:17, Paul Gortmaker wrote:
OK, but that was not at _all_ what I thought when
On 09/02/2014 02:13 PM, Chen Gang wrote:
> On 9/2/14 13:17, Paul Gortmaker wrote:
>>
>> OK, but that was not at _all_ what I thought when looking at this...
>>
>> Instead I saw a well intentioned, but perhaps not fully thought out
>> attempt at fixing a largely irrelevant randconfig/allmodconfig
On 09/02/2014 02:13 PM, Chen Gang wrote:
On 9/2/14 13:17, Paul Gortmaker wrote:
OK, but that was not at _all_ what I thought when looking at this...
Instead I saw a well intentioned, but perhaps not fully thought out
attempt at fixing a largely irrelevant randconfig/allmodconfig of a
1990's
On 9/2/14 13:17, Paul Gortmaker wrote:
> [Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using]
> On 01/09/2014 (Mon 10:01) H. Peter Anvin wrote:
>
>> On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
>>>>>
>>>> diff --git a/init
On 9/2/14 13:17, Paul Gortmaker wrote:
[Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using]
On 01/09/2014 (Mon 10:01) H. Peter Anvin wrote:
On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
diff --git a/init/Kconfig b/init/Kconfig
index ac033c3..f301cc8 100644
[Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using]
On 01/09/2014 (Mon 10:01) H. Peter Anvin wrote:
> On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
> >>>
> >> diff --git a/init/Kconfig b/init/Kconfig
> >> index ac033c3..f301cc8 100644
&
On 09/02/2014 01:01 AM, H. Peter Anvin wrote:
> On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
>>> diff --git a/init/Kconfig b/init/Kconfig
>>> index ac033c3..f301cc8 100644
>>> --- a/init/Kconfig
>>> +++ b/init/Kconfig
>>> @@ -23,6 +23,12 @@ config CONSTRUCTORS
>>> config IRQ_WORK
>>>
On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
>>>
>> diff --git a/init/Kconfig b/init/Kconfig
>> index ac033c3..f301cc8 100644
>> --- a/init/Kconfig
>> +++ b/init/Kconfig
>> @@ -23,6 +23,12 @@ config CONSTRUCTORS
>> config IRQ_WORK
>> bool
>>
>> +config CPU_LITTLE_ENDIAN
>> +bool
>> +
[[PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using] On
01/09/2014 (Mon 23:46) Chen Gang wrote:
> Some individual modules want to know the architecture's endian attribute
> during config time, or may cause compiling break, one sample is below:
> (with allm dcon
Some individual modules want to know the architecture's endian attribute
during config time, or may cause compiling break, one sample is below:
(with allm dconfig under microblaze):
CC [M] drivers/isdn/hisax/nj_s.o
drivers/isdn/hisax/nj_s.c: In function 'setup_netjet_s':
Some individual modules want to know the architecture's endian attribute
during config time, or may cause compiling break, one sample is below:
(with allm dconfig under microblaze):
CC [M] drivers/isdn/hisax/nj_s.o
drivers/isdn/hisax/nj_s.c: In function 'setup_netjet_s':
[[PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using] On
01/09/2014 (Mon 23:46) Chen Gang wrote:
Some individual modules want to know the architecture's endian attribute
during config time, or may cause compiling break, one sample is below:
(with allm dconfig under
On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
diff --git a/init/Kconfig b/init/Kconfig
index ac033c3..f301cc8 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -23,6 +23,12 @@ config CONSTRUCTORS
config IRQ_WORK
bool
+config CPU_LITTLE_ENDIAN
+bool
+
+config CPU_BIG_ENDIAN
On 09/02/2014 01:01 AM, H. Peter Anvin wrote:
On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
diff --git a/init/Kconfig b/init/Kconfig
index ac033c3..f301cc8 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -23,6 +23,12 @@ config CONSTRUCTORS
config IRQ_WORK
bool
+config
[Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using]
On 01/09/2014 (Mon 10:01) H. Peter Anvin wrote:
On 09/01/2014 09:08 AM, Paul Gortmaker wrote:
diff --git a/init/Kconfig b/init/Kconfig
index ac033c3..f301cc8 100644
--- a/init/Kconfig
+++ b/init/Kconfig
20 matches
Mail list logo
