Hi Dan,
On Thu, Jul 20, 2017 at 1:37 PM, Dan Carpenter wrote:
> On Thu, Jul 20, 2017 at 01:23:05PM +0200, Marcus Wolf wrote:
>> below you can see the report with the error on m68k. It was sent to me from a
>> test robot of intel.
>>
>> According to my research, this problem occured, because there
On Thu, Jul 20, 2017 at 01:23:05PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> below you can see the report with the error on m68k. It was sent to me from a
> test robot of intel.
>
> According to my research, this problem occured, because there is no hardware
> support for floating point on the m
On Thu, Jul 20, 2017 at 01:23:05PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> below you can see the report with the error on m68k. It was sent to me from a
> test robot of intel.
>
> According to my research, this problem occured, because there is no hardware
> support for floating point on the m68
Hi Greg,
below you can see the report with the error on m68k. It was sent to me from a
test robot of intel.
According to my research, this problem occured, because there is no hardware
support for floating point on the m68k (or it was configured not to use it).
Therefore gcc uses an internal func
Hi Marcus,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.13-rc1 next-20170717]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Wolf-Entwicklungen/drivers-staging
Hi Marcus,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.13-rc1 next-20170714]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Wolf-Entwicklungen/drivers-sta
On Sun, Jul 16, 2017 at 03:53:57PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> like I wrote before - unfortunally I couldn't find a git command, squashing
> all my commits into one single patch. Therfore I copy and pasted the patch
> manually.
git diff FIRST_PATCH..HEAD > my.patch
will do it.
> N
Sun, Jul 16, 2017 at 11:52:32AM +0200, Wolf Entwicklungen wrote:
> > From: Marcus Wolf
> > Date: Tue,16 Jul 2017 11:52:06 +0100
> > Subject: [PATCH 1/1] drivers/staging/pi433: New driver
>
> Why is this all here in the patch body? Usually git will strip this
> out, but in
On Sun, Jul 16, 2017 at 11:52:32AM +0200, Wolf Entwicklungen wrote:
> From: Marcus Wolf
> Date: Tue,16 Jul 2017 11:52:06 +0100
> Subject: [PATCH 1/1] drivers/staging/pi433: New driver
Why is this all here in the patch body? Usually git will strip this
out, but in the future, please don
From: Marcus Wolf
Date: Tue,16 Jul 2017 11:52:06 +0100
Subject: [PATCH 1/1] drivers/staging/pi433: New driver
Added a driver for the pi433 radio module
(see https://www.pi433.de/en.html for details).
Signed-off-by: Marcus Wolf
---
diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
bot
> To: kbu...@01.org
> Cc: Julia Lawall
> Subject: Re: [PATCH 1/1] drivers/staging/pi433: New driver
>
> Hi Wolf,
>
> [auto build test WARNING on staging/staging-testing]
> [also build test WARNING on v4.12 next-20170714]
> [if your patch is applied to the wrong git tr
test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 1/1] drivers/staging/pi433: New driver
Hi Wolf,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.12 next-20170714]
[if your patch is applied to the wrong git tree, please drop us a note to
12 matches
Mail list logo
