Initial patch by Ben Hutchings
We will install this in /usr, so it must use /var/lib for its state.
Only programs installed under /opt should use /var/opt.
Signed-off-by: Tomas Hozza
---
tools/hv/hv_kvp_daemon.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/t
From: Ben Hutchings
It's silly to create directories without execute permission, or to
give permissions to 'other' but not the group-owner.
Write the permissions in octal and 'ls -l' format since these are much
easier to read than the named macros.
Signed-off-by: Ben Hutchings
Signed-off-by: T
kvp_get_if_name and kvp_mac_to_if_name copy strings into statically
sized buffers which could be too small to store really long names.
Buffer sizes have been changed to PATH_MAX, include "limits.h" where
PATH_MAX is defined was added and length checks ware added via snprintf.
Signed-off-by: Tomas
On Mon, 2012-11-26 at 15:20 -0800, Andrew Morton wrote:
> On Mon, 26 Nov 2012 12:56:07 -0800
> Randy Dunlap wrote:
>
> > On 11/26/2012 06:17 AM, Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Changes since 20121115:
> > >
> >
> >
> > on i386:
> >
> > drivers/staging/fwserial/dma_fifo
The commit c8f2f0db1 ("zram: Fix handling of incompressible pages")
introduced a bug which caused a kunmap()'ed buffer to be used in case
of partial writes where the data was found to be incompressible.
This fixes bug 50081:
https://bugzilla.kernel.org/show_bug.cgi?id=50081
Signed-off-by: Nitin G
For every allocated object, zram maintains the the handle, size,
flags and count fields. Of these, only the handle is required
since zsmalloc now provides the object size given the handle.
The flags field was needed only to mark a given page as zero-filled.
Instead of this field, we now use an inva
Adds zs_get_object_size(handle) which provides the size of
the given object. This is useful since the user (zram etc.)
now do not have to maintain object sizes separately, saving
on some metadata size (4b per page).
The object handle encodes pair which currently points
to the start of the object.
On Mon, 2012-11-26 at 12:56 -0800, Randy Dunlap wrote:
> On 11/26/2012 06:17 AM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20121115:
> >
>
>
> on i386:
>
> drivers/staging/fwserial/dma_fifo.c: In function 'dma_fifo_in':
> drivers/staging/fwserial/dma_fifo.c:174:2: error: imp
Use WARN() as intended.
Signed-off-by: Peter Hurley
---
drivers/staging/fwserial/dma_fifo.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/staging/fwserial/dma_fifo.c
b/drivers/staging/fwserial/dma_fifo.c
index 72aa053..5e84634 100644
--- a/drivers/staging/fwser
This patch fixes an unused variable warning in gdm_usb_send
(when CONFIG_WIMAX_GDM72XX_K_MODE=n), which was introduced in
commit 1a276b80466bbd195cf94ec7178f68f2ab351467 (staging:
gdm72xx: protect access of rx / tx structs).
Signed-off-by: Ben Chan
---
drivers/staging/gdm72xx/gdm_usb.c |5 ++
From: Shan Wei
commit cf4ca4874fc45 removed the definition of NIPQUAD and NIPQUAD_FMT,
and NIP6 also is out of date.
Because DEBUG_SDU is not defined in gdm_wimax.h, no error message when compiling
this code. And remove constant condition judge.
Signed-off-by: Shan Wei
---
V3:
As suggestio
This define is no longer required for multi-file modules.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/comedi_compat32.c| 1 -
drivers/staging/comedi/comedi_fops.c| 1 -
drivers/staging/comedi/drivers.c
There are a couple defines left over from older kernel (2.4 and 2.6)
support. Remove them.
H Hartley Sweeten (2):
staging: comedi: remove unnecessary '#define _GNU_SOURCE'
staging: comedi: remove unnecessary '#define __NO_VERSION__'
drivers/staging/comedi/comedi_compat32.c| 1 -
This define is not needed.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers.c | 2 --
drivers/staging/comedi/drivers/ni_65xx.c | 1 -
2 files changed, 3 deletions(-)
diff --git a/drivers/staging/comedi/drivers.c b/drivers/stagin
On Mon, 26 Nov 2012 12:56:07 -0800
Randy Dunlap wrote:
> On 11/26/2012 06:17 AM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20121115:
> >
>
>
> on i386:
>
> drivers/staging/fwserial/dma_fifo.c: In function 'dma_fifo_in':
> drivers/staging/fwserial/dma_fifo.c:174:2: error: i
I've been banging on my test setup for the past week. I haven't
tracked down the cause yet, but something in my prior build system
results in this problem being masked with some builds. Doing pure
vanilla builds from git I'm able to reproduce with 3.6 and the 3.7-rc
series reliably. Support for
> -Original Message-
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Monday, November 26, 2012 4:12 PM
> To: KY Srinivasan
> Cc: Tomas Hozza; linux-ker...@vger.kernel.org; devel@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; jasow...@redhat.co
On Mon, Nov 26, 2012 at 08:42:40PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Tomas Hozza [mailto:tho...@redhat.com]
> > Sent: Monday, November 12, 2012 3:55 AM
> > To: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> > devel@linuxdriverproject.org; o...@a
On 11/26/2012 06:17 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20121115:
>
on i386:
drivers/staging/fwserial/dma_fifo.c: In function 'dma_fifo_in':
drivers/staging/fwserial/dma_fifo.c:174:2: error: implicit declaration of
function '__WARN_printf'
--
~Randy
__
> -Original Message-
> From: Tomas Hozza [mailto:tho...@redhat.com]
> Sent: Friday, November 09, 2012 7:47 AM
> To: o...@aepfle.de; KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; a...@canonical.com; jasow...@redhat.com;
> Toma
> -Original Message-
> From: Tomas Hozza [mailto:tho...@redhat.com]
> Sent: Monday, November 12, 2012 3:55 AM
> To: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com; KY Srinivasan; b...@deca
> -Original Message-
> From: Tomas Hozza [mailto:tho...@redhat.com]
> Sent: Monday, November 12, 2012 3:55 AM
> To: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com; KY Srinivasan; b...@deca
On Mon, 26 Nov 2012 07:37:50 + (UTC)
Woody Wu wrote:
...
> My question is, in terms of Linux driver technology, how to enable a
> non-PCI and not on-chip device driver? I think the ax_probe function
> must be called somehow, is this thinking right? If yes, I think before
> the driver get initi
23 matches
Mail list logo
