Remove all the 'default N' lines in the comedi Kconfig. They should all
be 'default n' but that is the default anyway.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Mori Hess
Cc: Greg Kroah-Hartman
---
diff --git a/drivers/staging/comedi/Kconfig b/drivers/staging/comedi/Kconfig
index a
On Thursday, May 17, 2012 11:29 AM, Ian Abbott wrote:
> On 17/05/2012 17:38, H Hartley Sweeten wrote:
>> BTW, what actual hardware do you have available to test with?
>
> Not a lot. Just the Amplicon cards (amplc_* drivers).
Speaking of the amplc_* drivers... What's up with them?
The dio200, pc2
On Thu, May 17, 2012 at 1:37 AM, Anton Vorontsov
wrote:
> Hi all,
>
> In v2:
>
> - Updated documentation per Colin Cross' comments;
> - Corrected return value in ramoops_pstore_write() (noticed by Kees Cook);
> - Fixed large writes handling in pstore_console_write(), i.e. when
> log_buf write is
On 17/05/2012 17:38, H Hartley Sweeten wrote:
On Thursday, May 17, 2012 8:58 AM, Ian Abbott wrote:
On 2012/05/17 02:32 PM, Greg KH wrote:
I thought a few years ago, either you, or someone else, said it would be
good to just delete them entirely. Or am I making that up and just wish
it would be
On Thu, May 17, 2012 at 1:40 AM, Anton Vorontsov
wrote:
> This is all straightforward: we just use the last region for
> console logging. If there's just one region, we fall-back to
> the old behaviour: just a oops/dumps logging.
>
> Signed-off-by: Anton Vorontsov
I don't think using the last re
From: Paul Stewart
This patch uses SET_NETDEV_DEV to set up a 'device' parent link in sysfs
(e.g. /sys/class/net/wm0/device) for a gdm72xx device.
Signed-off-by: Paul Stewart
Signed-off-by: Ben Chan
Cc: Sage Ahn
---
drivers/staging/gdm72xx/gdm_sdio.c |2 +-
drivers/staging/gdm72xx/gdm_u
On Thu, May 17, 2012 at 1:41 AM, Anton Vorontsov
wrote:
> The code tried to maintain the global list of persistent ram zones,
> which isn't a great idea overall, plus since Android's ram_console
> is no longer there, we can remove some unused functions.
>
> Signed-off-by: Anton Vorontsov
Acked-b
On Thu, May 17, 2012 at 1:40 AM, Anton Vorontsov
wrote:
> Since we use multiple regions, the messages are somewhat annoying.
> We do print total mapped memory already, so no need to print the
> information for each region in the library routines.
>
> Signed-off-by: Anton Vorontsov
Acked-by: Kees
On Thursday, May 17, 2012 8:58 AM, Ian Abbott wrote:
> On 2012/05/17 02:32 PM, Greg KH wrote:
>> I thought a few years ago, either you, or someone else, said it would be
>> good to just delete them entirely. Or am I making that up and just wish
>> it would be so? :)
>
> I can't remember at my age
On Thu, May 17, 2012 at 1:40 AM, Anton Vorontsov
wrote:
> This is all straightforward: we just use the last region for
> console logging. If there's just one region, we fall-back to
> the old behaviour: just a oops/dumps logging.
>
> Signed-off-by: Anton Vorontsov
Acked-by: Kees Cook
-Kees
--
On Thu, May 17, 2012 at 12:15 AM, Anton Vorontsov
wrote:
> The patch switches pstore RAM backend to use persistent_ram routines,
> one step closer to the ECC support.
>
> Signed-off-by: Anton Vorontsov
> Acked-by: Marco Stornelli
> ---
> fs/pstore/ram.c | 106
> +++
On Thu, May 17, 2012 at 1:40 AM, Anton Vorontsov
wrote:
> Pstore doesn't support logging kernel messages in run-time, it only
> dumps dmesg when kernel oopses/panics. This makes pstore useless for
> debugging hangs caused by HW issues or improper use of HW (e.g.
> weird device inserted -> driver t
_schedule" [drivers/staging/gdm72xx/gdmwm.ko] undefined!
ERROR: "skb_put" [drivers/staging/gdm72xx/gdmwm.ko] undefined!
ERROR: "sock_wfree" [drivers/staging/gdm72xx/gdmwm.ko] undefined!
ERROR: "__nlmsg_put" [drivers/staging/gdm72xx/gdmwm.ko] undefined!
Signed-
On 2012/05/17 02:32 PM, Greg KH wrote:
> On Thu, May 17, 2012 at 07:45:08AM +0100, Ian Abbott wrote:
>> On 17/05/12 07:15, H Hartley Sweeten wrote:
>>> Wednesday, May 16, 2012 7:18 PM, Greg KH wrote:
On Wed, May 16, 2012 at 05:51:56PM -0700, H Hartley Sweeten wrote:
> Convert the struct ad
On Thu, May 17, 2012 at 12:11:48AM -0700, Anton Vorontsov wrote:
> Hi all,
>
> Here comes v3:
>
> - Rebased on current staging-next tree, so only 3 patches left;
> - Fixed ram_console dependency in Kconfig (issue noticed by Greg KH).
Nice, thanks for reworking this, now applied.
greg k-h
__
On Thu, May 17, 2012 at 07:45:08AM +0100, Ian Abbott wrote:
> On 17/05/12 07:15, H Hartley Sweeten wrote:
> >Wednesday, May 16, 2012 7:18 PM, Greg KH wrote:
> >>On Wed, May 16, 2012 at 05:51:56PM -0700, H Hartley Sweeten wrote:
> >>>Convert the struct addi_board initialization to C99 format and rem
The code tried to maintain the global list of persistent ram zones,
which isn't a great idea overall, plus since Android's ram_console
is no longer there, we can remove some unused functions.
Signed-off-by: Anton Vorontsov
---
fs/pstore/ram_core.c | 77 ---
All the functionality is now supported by pstore and pstore_ram drivers.
Signed-off-by: Anton Vorontsov
---
drivers/staging/android/Kconfig |5 -
drivers/staging/android/Makefile |1 -
drivers/staging/android/ram_console.c | 179 -
3 files chan
Suggested-by: Shuah Khan
Signed-off-by: Anton Vorontsov
---
Documentation/ramoops.txt | 14 ++
1 file changed, 14 insertions(+)
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 4ba7db2..59a74a8 100644
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramo
This is all straightforward: we just use the last region for
console logging. If there's just one region, we fall-back to
the old behaviour: just a oops/dumps logging.
Signed-off-by: Anton Vorontsov
---
fs/pstore/ram.c | 40 +++-
1 file changed, 31 insertion
Since we use multiple regions, the messages are somewhat annoying.
We do print total mapped memory already, so no need to print the
information for each region in the library routines.
Signed-off-by: Anton Vorontsov
---
fs/pstore/ram_core.c |4 ++--
1 file changed, 2 insertions(+), 2 deletio
Pstore doesn't support logging kernel messages in run-time, it only
dumps dmesg when kernel oopses/panics. This makes pstore useless for
debugging hangs caused by HW issues or improper use of HW (e.g.
weird device inserted -> driver tried to write a reserved bits ->
SoC hanged. In that case we don'
Hi all,
In v2:
- Updated documentation per Colin Cross' comments;
- Corrected return value in ramoops_pstore_write() (noticed by Kees Cook);
- Fixed large writes handling in pstore_console_write(), i.e. when
log_buf write is larger than pstore bufsize. Also Noticed by Kees Cook.
These patches
On Wed, 16 May 2012, K. Y. Srinivasan wrote:
> Set the hid drvdata prior to invoking hid_add_device() as hid_add_device()
> expects this state to be set. This bug was introduced in the recent hid
> changes that were made in:
>
> commit 07d9ab4f0e52cb2a383596e5ebbbd20232501393
> HID: hid-hyperv: D
The patch switches pstore RAM backend to use persistent_ram routines,
one step closer to the ECC support.
Signed-off-by: Anton Vorontsov
Acked-by: Marco Stornelli
---
fs/pstore/ram.c | 106 +++
1 file changed, 59 insertions(+), 47 deletions(-
This is now straightforward: just introduce a module parameter and pass
the needed value to persistent_ram_new().
Signed-off-by: Anton Vorontsov
Acked-by: Marco Stornelli
Acked-by: Kees Cook
---
Documentation/ramoops.txt |6 ++
fs/pstore/ram.c| 15 ---
includ
This is a first step for adding ECC support for pstore RAM backend: we
will use the persistent_ram routines, kindly provided by Google.
Basically, persistent_ram is a set of helper routines to deal with the
[optionally] ECC-protected persistent ram regions.
A bit of Makefile, Kconfig and header f
Hi all,
Here comes v3:
- Rebased on current staging-next tree, so only 3 patches left;
- Fixed ram_console dependency in Kconfig (issue noticed by Greg KH).
And the boilerplate, background for the series:
There are currently two competing debug facilities to store kernel
messages in a persiste
28 matches
Mail list logo
