On Fri, Feb 15, 2013 at 01:27:38PM -0800, Andrew Morton wrote:
> On Fri, 15 Feb 2013 01:34:50 -0500
> Johannes Weiner wrote:
>
> > + * The status is returned in a vector of bytes. The least significant
> > + * bit of each byte is 1 if the referenced page is in memory, otherwise
> > + * it is
On Fri, Feb 15, 2013 at 1:59 PM, Al Viro wrote:
> On Fri, Feb 15, 2013 at 12:02:50PM -0800, Linus Torvalds wrote:
>> On Wed, Feb 13, 2013 at 9:36 PM, Al Viro wrote:
>> >
>> > The only problem is that some suicides do SIGKILL, some SIGSEGV.
>> > AFAICS, it started as SIGSEGV and had been
Hi
Worked for a while on 3.8.0-rc7, generally it is fine, then suddenly
laptop stopped responding to keyboard and mouse.
Sure it can be memory corruption by some other module, but maybe not.
Worth to report i guess.
After reboot checked logs and found this:
Feb 16 00:40:17 localhost kernel:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 3399cfb5df9594495b876d1843a7165f77366b2b upstream.
Commit e7e034e18a0a ("drivers/rtc/rtc-pl031.c: fix the missing operation
on enable") accidentally broke the ST variants
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting
This is the start of the stable review cycle for the 3.4.32 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:47 UTC 2013.
Anything
3.7-stable review patch. If anyone has any objections, please let me know.
--
This reverts commit a56040731e5b00081c6d6c26b99e6e257a5d63d7 which was
commit eb178619f930fa2ba2348de332a1ff1c66a31424 upstream.
It has been reported to cause problems:
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request
On Fri, 15 Feb 2013 23:44:44 +0100
Richard Weinberger wrote:
> As stated in [0], I'd simply revert commit ec0c4274 ("futex: Mark
> get_robust_list as deprecated")
Too much talk, not enough patches. I typed it all in again.
--
To unsubscribe from this list: send the line "unsubscribe
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting
This is the start of the stable review cycle for the 3.7.9 release.
There are 10 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:54:03 UTC 2013.
Anything
Tell twl4030_madc_conversion that this driver needs raw values.
Driver twl4030_madc has some hardcoded values and conversation
functions which are incorrect for Nokia RX-51 board. This driver
rx51_battery expects raw values which convert itself.
This patch fixing values reported by power supply
Driver twl4030-madc has hardcoded channel types (10 - battery current,
1 - battery temperature) and also conversation data in variable
twl4030_divider_ratios. These hardcoded channels are incorrect for
Nokia RX-51 board (where is channel 0 - battery temperature).
For Nokia RX-51 there is
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 9977f0f164d46613288e0b5778eae500dfe06f31 upstream.
With commit 8e72033f2a48 ("thp: make MADV_HUGEPAGE check for
mm->def_flags") the VM_NOHUGEPAGE flag may be set on s390
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't
Hi
Booted on Toshiba laptop, x86_64, NVIDIA Corporation GT218 [GeForce
310M], latest rc, and got this.
Please let me know if you need additional information.
[ 16.595094] [TTM] Zone dma32: Available graphics memory: 2097152
kiB
[ 16.595096] [TTM] Initializing pool allocator
[
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in
This is the start of the stable review cycle for the 3.0.65 release.
There are 4 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:56 UTC 2013.
Anything
On Tue, 15 Jan 2013 12:51:54 +0100, Roland Stigge wrote:
> There is a race condition between creating a gpio or gpiochip device and
> adding
> default attributes. This patch fixes this by defining the default attributes
> as
> dev_attrs of the class. For this, it was necessary to create a
Thank You for your response.
Comments inline.
I will throughly inspect the other 52% that wasn't reviewed for the same
simple mistakes that were missed :)
Testing changes before submitting.
A patch will be coming soon.
On Thu, Feb 14, 2013 at 03:56:14PM -0800, Andrew Morton wrote:
> On Fri, 1
On 02/15/2013 05:21 PM, Seiji Aguchi wrote:
> Rik, Satoru,
>
> Do you have any comments?
>
> Seiji
Hmm, this seems what we wanted to know in the previous thread.
Because extra_free_kbytes is quite simple and it fixes the problem,
it should be merged into upstream.
Regards,
Satoru
>>
On Wed, Feb 13, 2013 at 7:58 AM, Christian Gmeiner
wrote:
> During the development of this driver an in-house register
> documentation was used. The last weeks some integration tests
> were done and this problem was found. It turned out that
> the released register documentation is wrong.
>
> The
On Fri, 15 Feb 2013 13:38:24 +0100
Michal Hocko wrote:
> Fenguang Wu has reported the following compile time issue
> arch/ia64/kernel/topology.c:278:16: error: conflicting types for 'cache_show'
> include/linux/slab.h:224:5: note: previous declaration of 'cache_show' was
> here
>
> which has
Am Fri, 15 Feb 2013 14:26:52 -0800
schrieb a...@linux-foundation.org:
> --
> From: Paul Gortmaker
> Subject: futex: avoid kernel taint caused by get_robust_list
>
> Commit ec0c4274e33c0373e4 ("futex: Mark get_robust_list as
> deprecated") added
On Fri, 15 Feb 2013 17:28:03 -0500
Johannes Weiner wrote:
> > Yes, and there will be immediate calmour to add more goodies to the
> > other seven bits. PageDirty, referenced state, etc. We should think
> > about this now, at the design stage rather than grafting things on
> > later.
>
> I'm
On Mon, Feb 11, 2013 at 7:48 AM, David Engraf wrote:
> I have encountered a problem when a linux system uses a clocksource with
> mult = 1 and shift = 0 (clocksource cycle = nanoseconds). It may happen that
> the function timekeeping_adjust reduces the value of mult to 0 when error is
> lower
On Fri, Feb 15, 2013 at 04:50:28PM +0100, Ingo Molnar wrote:
> Dave, one thing that might be worth trying is to disable
> CONFIG_BUG and see whether the system manages to limp through to
> get console output?
Didn't make any difference. Black screen, blinky power light.
Dave
--
Hi,
The following patch causes 'perf stat --repeat 0' to be interpreted as
'forever', displaying the stats for every run.
We act as if a single run was asked, and reset the stats in each
iteration. In this mode SIGINT is passed to perf to be able to stop the
loop with Ctrl+C.
Regards,
Frederik
On Fri, Feb 15, 2013 at 03:02:22PM -0700, Stephen Warren wrote:
> From: Stephen Warren
>
> Tegra only supports, and always enables, device tree. Remove all ifdefs
> for DT support from the driver.
>
> Signed-off-by: Stephen Warren
> ---
> drivers/pwm/pwm-tegra.c |4 +---
> 1 file changed,
On Fri, Feb 15, 2013 at 01:14:51PM -0800, Andrew Morton wrote:
> On Fri, 15 Feb 2013 01:34:50 -0500
> Johannes Weiner wrote:
>
> > On Mon, Feb 11, 2013 at 02:12:39PM -0800, Andrew Morton wrote:
> > > Also, having to mmap the file to be able to query pagecache state is a
> > > hack. Whatever
On Fri, 2013-02-15 at 21:27 +0100, Linus Walleij wrote:
> On Fri, Feb 15, 2013 at 3:48 AM, Tony Prisk wrote:
>
> Hm some of these remarks would apply to the BCM2835 driver as
> well, I missed to complain at the time it was added. Probably I was
> all too excited about the new Raspberry.
>
>
On 02/15/2013 05:21 PM, Seiji Aguchi wrote:
Rik, Satoru,
Do you have any comments?
IIRC at the time the patch was rejected as too inelegant.
However, nobody else seems to have come up with a better plan, and
there are users in need of a fix for this problem.
I would still like to see a fix
On Fri, 15 Feb 2013 17:57:10 +0100
Jan Kara wrote:
> A CPU can be caught in console_unlock() for a long time (tens of seconds are
> reported by our customers) when other CPUs are using printk heavily and serial
> console makes printing slow. Despite serial console drivers are calling
>
Rik, Satoru,
Do you have any comments?
Seiji
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of dormando
> Sent: Monday, February 11, 2013 9:01 PM
> To: Rik van Riel
> Cc: Randy Dunlap; Satoru Moriya;
On Fri, Feb 15, 2013 at 1:53 PM, Stephen Warren wrote:
> From: Stephen Warren
>
> Tegra only supports, and always enables, device tree. Remove all ifdefs
> and runtime checks for DT support from the driver.
>
> Signed-off-by: Stephen Warren
Acked-by: Dan Williams
..adding Vinod.
--
To
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer wrote:
> I am currently tracking a hotlock reported by a customer on a large system,
> 512 cores. I am currently running 3.8-rc7 but the issue looks like it has
> been
> this way for a very long time.
> The offending lock is
On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
>
> [ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
>
> * Yinghai Lu wrote:
>
> > On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar wrote:
> > > these three:
> > >
> > > 10d73e655cef mm: bootmem: fix
From: Stephen Warren
Tegra only supports, and always enables, device tree. Remove all ifdefs
for DT support from the driver.
Signed-off-by: Stephen Warren
---
drivers/pwm/pwm-tegra.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/pwm/pwm-tegra.c
On Fri, Feb 15, 2013 at 12:02:50PM -0800, Linus Torvalds wrote:
> On Wed, Feb 13, 2013 at 9:36 PM, Al Viro wrote:
> >
> > The only problem is that some suicides do SIGKILL, some SIGSEGV.
> > AFAICS, it started as SIGSEGV and had been switched to SIGKILL for a.out
> > (without any
On Fri, 2013-02-15 at 16:18 -0500, Jarod Wilson wrote:
> On Wed, Feb 13, 2013 at 09:36:04AM +0300, Dan Carpenter wrote:
> > On Tue, Feb 12, 2013 at 01:20:36PM -0800, Joe Perches wrote:
> > > His email bounces and he hasn't done work on
> > > these sections in a couple of years.
> > I've added him
From: Stephen Warren
Tegra only supports, and always enables, device tree. Remove all ifdefs
and runtime checks for DT support from the driver.
Signed-off-by: Stephen Warren
---
drivers/gpio/gpio-tegra.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git
From: Stephen Warren
Tegra only supports, and always enables, device tree. Remove all ifdefs
and runtime checks for DT support from the driver.
Signed-off-by: Stephen Warren
---
drivers/dma/tegra20-apb-dma.c | 22 +++---
1 file changed, 7 insertions(+), 15 deletions(-)
diff
On Tue, 15 Jan 2013 12:51:52 +0100, Roland Stigge wrote:
> This patch adds sysfs support to the block GPIO API.
>
> Signed-off-by: Roland Stigge
Hi Roland.
I'm going to ignore this patch for the time being because I think my
comments on the first patch basically obsolete what is being done
On Mon, Jan 28, 2013 at 04:54:08PM +0100, Sebastian Hesselbarth wrote:
> With DT support for orion-ehci also convert Dove to it and
> remove the legacy calls and clock aliases.
>
> This patch is based on "ARM: Dove: split legacy and DT setup"
> applied to mvebu/boards recently.
>
>
We give the user access to change the power state of the device but
certain transitions result in an uninitialized state which the user
cannot resolve. To fix this we need to mark the PowerState field of
the PMCSR register read-only and effect the requested change on behalf
of the user. This has
Hello,
On Thu, 14 Feb 2013, Andrew Morton wrote:
> On Thu, 7 Feb 2013 10:40:26 +0200 (EET)
> Julian Anastasov wrote:
>
> > > Another question about the sysctl_sync_qlen_max:
> > > This variable is assigned as:
> > >
> > > ipvs->sysctl_sync_qlen_max = nr_free_buffer_pages() / 32;
> >
On 02/15/2013 12:46 PM, Doug Anderson wrote:
> The i2c-arbitrator-cros-ec driver implements the arbitration scheme
> that the Embedded Controller (EC) on the ARM Chromebook expects to use
> for bus multimastering. This i2c-arbitrator-cros-ec driver could also
> be used in other places where
On Fri, 15 Feb 2013 01:34:50 -0500
Johannes Weiner wrote:
> + * The status is returned in a vector of bytes. The least significant
> + * bit of each byte is 1 if the referenced page is in memory, otherwise
> + * it is zero.
Also, this is going to be dreadfully inefficient for some obvious
On Wed, Feb 13, 2013 at 09:36:04AM +0300, Dan Carpenter wrote:
> On Tue, Feb 12, 2013 at 01:20:36PM -0800, Joe Perches wrote:
> > His email bounces and he hasn't done work on
> > these sections in a couple of years.
> >
>
> I've added him to the CC list.
>
> Can we just update MAINTAINERS with
On Fri, 15 Feb 2013 01:34:50 -0500
Johannes Weiner wrote:
> On Mon, Feb 11, 2013 at 02:12:39PM -0800, Andrew Morton wrote:
> > Also, having to mmap the file to be able to query pagecache state is a
> > hack. Whatever happened to the fincore() patch?
>
> I don't know, but how about this one:
On Fri, 15 February 2013 12:35:46 -0800, Patrick O'Grady wrote:
>
> Permit the user to specify the erase page size as a parameter.
> This solves two problems:
>
> - phram can access images made by mkfs.jffs2. mkfs.jffs2 won't
> create images with erase sizes less than 8KiB; many architectures
>
On Fri, Feb 15, 2013 at 3:56 PM, Andy Shevchenko
wrote:
> On Fri, Feb 15, 2013 at 4:52 PM, Linus Walleij
> wrote:
>> On Tue, Feb 12, 2013 at 11:58 AM, Andy Shevchenko
>> wrote:
>>
>>> I have not checked the code but there is a possibility that custom
>>> pool->lock
>>> is not needed at all
On Friday, February 15, 2013 11:02:49 AM H. Peter Anvin wrote:
> On 02/15/2013 09:21 AM, Paul Moore wrote:
> > Commit fca460f95e928bae373daa8295877b6905bc62b8 simplified the x32
> > implementation by creating a syscall bitmask, equal to 0x4000, that
> > could be applied to x32 syscalls such
On Mon, Feb 11, 2013 at 10:26:09AM -0600, Jacob Shin wrote:
> On Fri, Feb 08, 2013 at 12:16:28PM +0100, Stephane Eranian wrote:
> > On Wed, Feb 6, 2013 at 6:26 PM, Jacob Shin wrote:
> > > On AMD family 15h processors, there are 4 new performance counters
> > > (in addition to 6 core performance
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very long time.
The offending lock is proc_dir_entry->pde_unload_lock.
This patch converts the replaces the lock with the rcu.
On Fri, Feb 08, 2013 at 03:37:31PM +0100, Benjamin Tissoires wrote:
> Some drivers need to wait for an io from the underlying device, creating
> an unwanted dependency on the underlying transport layer. This patch adds
> wait() to the interface, thereby removing usbhid from the lion share of
> the
From: Johannes Weiner
Date: Fri, 15 Feb 2013 01:34:50 -0500
> + nr_pages = DIV_ROUND_UP(len, PAGE_CACHE_SIZE);
A small nit, maybe use PAGE_CACHE_ALIGN() here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
From: Patrick O'Grady
Permit the user to specify the erase page size as a parameter.
This solves two problems:
- phram can access images made by mkfs.jffs2. mkfs.jffs2 won't
create images with erase sizes less than 8KiB; many architectures
define PAGE_SIZE as 4KiB.
- Allows more effective use
On Fri, Feb 15, 2013 at 3:48 AM, Tony Prisk wrote:
Hm some of these remarks would apply to the BCM2835 driver as
well, I missed to complain at the time it was added. Probably I was
all too excited about the new Raspberry.
Mainly you want Stephens review on this since he wrote the
driver you
As ways to determine whether to allow certain functions to be
called.
This makes it easier to understand the code - the three functions
that can be called by the filesystem irregardless whether a backend is set or
not cleancache_init_fs, cleancache_init_shared_fs, and cleancache_invalidate_fs.
From: Dan Magenheimer
With the goal of allowing tmem backends (zcache, ramster, Xen tmem) to be
built/loaded as modules rather than built-in and enabled by a boot parameter,
this patch provides "lazy initialization", allowing backends to register to
cleancache even after filesystems were
From: Dan Magenheimer
Allow Xen tmem shim to be built/loaded as a module. Xen self-ballooning
and frontswap-selfshrinking are now also "lazily" initialized when the
Xen tmem shim is loaded as a module, unless explicitly disabled
by module parameters.
Note runtime dependency disallows loading
With the support for loading of backends as modules, the
cleancache_enabled is always set to true. The next subsequent patches
are going to convert the cleancache_enabled to be a bit more selective
and be on/off depending on whether the backend has registered - and not
whether the cleancache API
From: Dan Magenheimer
With the goal of allowing tmem backends (zcache, ramster, Xen tmem) to be
built/loaded as modules rather than built-in and enabled by a boot parameter,
this patch provides "lazy initialization", allowing backends to register to
frontswap even after swapon was run. Before a
As ways to determine whether to allow certain functions to be called.
This makes it easier to understand the code - the two functions
that can be called irregardless whether a backend is set or not is
the frontswap_init and frontswap_invalidate_area. The rest of the
frontswap functions end up
Greg, I am CC-ing you here since there is one patch that touches
the staging tree:
[PATCH 02/11] frontswap: Make frontswap_init use a pointer for the
I am hoping that for #2 you are OK ACK-ing - it is a simple fix that ought
to have been a long time ago.
I am hoping that these patches are
With the support for loading of backends as modules (see for example:
"staging: zcache: enable zcache to be built/loaded as a module"), the
frontswap_enabled is always set to true ("mm: frontswap: lazy
initialization to allow tmem backends to build/run as modules").
The next patch "frontswap: Use
In the past it either used to be NULL or the "older" backend. Now we
also return -Exx error codes.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c | 5 -
drivers/xen/tmem.c | 5 -
2 files changed, 8 insertions(+), 2 deletions(-)
diff
From: Minchan Kim
Frontswap initialization routine depends on swap_lock, which want
to be atomic about frontswap's first appearance.
IOW, frontswap is not present and will fail all calls OR frontswap is
fully functional but if new swap_info_struct isn't registered
by enable_swap_info, swap
sparse complains about the following functions
ozhcd.c:330:20: warning: symbol 'oz_uncancel_urb' was not declared. Should it
be static?
ozhcd.c:420:6: warning: symbol 'oz_complete_buffered_urb' was not declared.
Should it be static?
ozmain.c:25:6: warning: symbol 'g_net_dev' was not declared.
This patch marks function parameters that are used read only
as well as readonly structs (and corresponding pointers) as const.
Signed-off-by: Peter Huewe
---
drivers/staging/ozwpan/ozcdev.c|2 +-
drivers/staging/ozwpan/ozhcd.c |9 +
drivers/staging/ozwpan/ozpd.c |
oz_cdev_heartbeat is empty and unused -> safe to remove.
Signed-off-by: Peter Huewe
---
drivers/staging/ozwpan/ozcdev.c |6 --
drivers/staging/ozwpan/ozcdev.h |1 -
2 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/ozwpan/ozcdev.c
ozcdev.c and ozhcd.c should include their own header file, so sparse
knows which functions are declared and which not.
Signed-off-by: Peter Huewe
---
drivers/staging/ozwpan/ozcdev.c |1 +
drivers/staging/ozwpan/ozhcd.c |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git
On Fri, Feb 15, 2013 at 12:40:47PM -0700, Stephen Warren wrote:
> On 02/15/2013 12:18 PM, Wolfram Sang wrote:
> > On Thu, Feb 14, 2013 at 06:13:33PM +0530, Laxman Dewangan wrote:
> >> If timeout error occurs in the i2c transfer then it was dumping warning
> >> of call stack.
> >>
> >> Remove the
> > @@ -1247,11 +1247,11 @@ static void set_input_params(struct input_dev *dev,
> > struct synaptics_data *priv)
> > input_set_abs_params(dev, ABS_PRESSURE, 0, 255, 0, 0);
> >
> > if (SYN_CAP_IMAGE_SENSOR(priv->ext_cap_0c)) {
> > - input_mt_init_slots(dev, 2, 0);
> >
On Friday 15 February 2013, Greg KH wrote:
> On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
> >
> > After merging the char-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
>
On Fri, Feb 15, 2013 at 03:51:41PM +0200, Kirill A. Shutemov wrote:
> Johan Hedberg wrote:
> > Hi David,
> >
> > On Fri, Feb 15, 2013, David Herrmann wrote:
> > > On Fri, Feb 15, 2013 at 12:29 PM, Kirill A. Shutemov
> > > wrote:
> > > > Hi David and all,
> > > >
> > > > There's claim in uhid.h
On Jan 21, 2013, at 7:02 AM, Julia Lawall wrote:
> From: Julia Lawall
>
> Delete successive tests to the same location. The code tested the result
> of a previous call, that itself was already tested. It is changed to test
> the result of the most recent call.
>
> A simplified version of
Forgot to reply to this bit:
On 02/15/2013 07:43 PM, Oleg Nesterov wrote:
>> We'd miss the poke
>> > variant, but that looks like something that could be always be added
>> > later.
> Yes. _POKE_ or _QUEUE_ or _DEQUEUE_, we can add more features if user-
> space wants them.
In general, IMO, I
On Wed, Feb 13, 2013 at 9:36 PM, Al Viro wrote:
>
> The only problem is that some suicides do SIGKILL, some SIGSEGV.
> AFAICS, it started as SIGSEGV and had been switched to SIGKILL for a.out
> (without any comments) in 1.1.62.
Ok, I really don't think it matters which one we do - either
On Fri, Feb 15, 2013 at 11:36 AM, Henrik Rydberg wrote:
> To properly setup event parameters for emulated events, pass
> the appropriate flag to the slot initialization function. Also,
> all MT-related events should be setup before initialization.
>
> Incidentally, this solves the issue of doubly
> I'll re-send with I2C subsystem wide. I probably won't attempt the
> whole kernel wide at this point, but would be very happy if someone
> else wanted to! :)
Thanks. Please double check that setting NULL is really unneeded for the
non-platform-bus variants, too, or skip those if you are
On 02/15/2013 07:43 PM, Oleg Nesterov wrote:
> On 02/15, Pedro Alves wrote:
>>
>> Not sure I'm reading the patch right, but it looks like GDB would
>> be able to use this as alternative to PTRACE_GET_SIGINFO variant
>
> No, it is different. PTRACE_GETSIGINFO reports the siginfo for the signal
>
Now that we have i2c-arbitrator in place on bus 4 we can add the
sbs-battery driver. Future devices will be added onto bus 4 once
drivers are in good shape.
Signed-off-by: Doug Anderson
---
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/exynos5250-snow.dts | 6 ++
1 file
The i2c-arbitrator-cros-ec driver implements the arbitration scheme
that the Embedded Controller (EC) on the ARM Chromebook expects to use
for bus multimastering. This i2c-arbitrator-cros-ec driver could also
be used in other places where standard I2C bus arbitration can't be
used and two extra
On Fri, Feb 15, 2013 at 10:51:40AM -0800, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix printk format warning. dma_addr_t can be 32-bit or 64-bit,
> so cast it to long long for printing. This also matches the
> printk format specifier that is already used.
>
>
101 - 200 of 1276 matches
Mail list logo
