On Thu, 16 Mar 2017 10:26:48 +0900, Greg KH said:
> On Tue, Mar 14, 2017 at 07:52:36PM -0600, Perry Hooker wrote:
> > $ git checkout next-20170310
> > What am I doing wrong / where should I go for more info?
>
> linux-next is usually a day or so behind my tree, so maybe there were
> other patches
Hello,
A bit confused with "free Linux/Ubuntu VMs".
Do you mean you looking for VM image ( to directly run your tests )
or an emulator to create VMs locally and play around.
For the first, I have not tried with. Probably vmware images can be found at :
http://www.osboxes.org/vmware-images/
But,
On Tue, Mar 14, 2017 at 07:52:36PM -0600, Perry Hooker wrote:
> I recently submitted a patch (attached below) that corrects a couple
> of 'sparse' warnings in drivers/staging/rtl8192u/r8192U_dm.c.
>
> I got this reply back from greg k-h:
>
> > This patch does not apply to my tree at all :(
> > Pl
I recently submitted a patch (attached below) that corrects a couple
of 'sparse' warnings in drivers/staging/rtl8192u/r8192U_dm.c.
I got this reply back from greg k-h:
> This patch does not apply to my tree at all :(
> Please rebase it against linux-next and try again.
However, I thought I *was
On Wed, Mar 15, 2017 at 12:12:48PM +0100, Bjørn Mork wrote:
> Alexander Kapshuk writes:
>
> >>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding wrote:
> >>> > why does calling pr_debug() with more than one argument cause a sparse
> >>> > warning?
> >>> >
> >>> > drivers/mmc/core/sdio_io.c:70:
Hi, all
I encounter a problem when I read the source code of kernel 4.9.9.
In arch/x86/mm/init_32.c, at line 125 [1], there is a function named
page_table_range_init_count(...). I have analyzed some codes and find its
two parameters are PKMAP_BASE and FIXADDR_START.
Between Line 141 and Line 150
Alexander Kapshuk writes:
>>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding wrote:
>>> > why does calling pr_debug() with more than one argument cause a sparse
>>> > warning?
>>> >
>>> > drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
>>> >
>>> > sdio_io.c:70:
>>>
On Wed, Mar 15, 2017 at 12:40 PM, Tobin C. Harding wrote:
> On Wed, Mar 15, 2017 at 12:01:39PM +0200, Alexander Kapshuk wrote:
>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding wrote:
>> > why does calling pr_debug() with more than one argument cause a sparse
>> > warning?
>> >
>> > drivers/m
On Wed, Mar 15, 2017 at 12:01:39PM +0200, Alexander Kapshuk wrote:
> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding wrote:
> > why does calling pr_debug() with more than one argument cause a sparse
> > warning?
> >
> > drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
>
On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding wrote:
> why does calling pr_debug() with more than one argument cause a sparse
> warning?
>
> drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
>
> sdio_io.c:70:
> pr_debug("SDIO: Enabling device %s...\n", sdio_func_id(fun
why does calling pr_debug() with more than one argument cause a sparse
warning?
drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
sdio_io.c:70:
pr_debug("SDIO: Enabling device %s...\n", sdio_func_id(func));
What can we do about this?
thanks,
Tobin.
_
11 matches
Mail list logo