In commit d166991234347215dc23fc9dc15a63a83a1a54e1
idle: Implement generic idle function
Thomas Gleixner cleaned up many things but perturbed some
fragile code that was keeping ia64 alive. So we started
seeing:
WARNING: at kernel/cpu/idle.c:94 cpu_idle_loop+0x360/0x380()
and other unpleasantn
Split kcore bits from linux/procfs.h into linux/kcore.h.
Signed-off-by: David Howells
cc: linux-m...@linux-mips.org
cc: sparcli...@vger.kernel.org
cc: x...@kernel.org
cc: linux...@kvack.org
---
arch/mips/mm/init.c |1 +
arch/score/mm/init.c|2 +-
arch/x86/mm/init_64.c |1 +
On 04/10/2013 06:22 AM, Viresh Kumar wrote:
On 9 April 2013 22:26, Stratos Karafotis wrote:
On 04/05/2013 10:50 PM, Stratos Karafotis wrote:
Hi Viresh,
On 04/04/2013 07:54 AM, Viresh Kumar wrote:
Hi Stratos,
Yes, your results show some improvements. BUT if performance is the only
thing
we
Don't need to save the PDE of a directory created under /proc/net/rtl8192/ as
we can use proc subtree deletion to get rid of it and all its children.
Signed-off-by: David Howells
cc: Jerry Chuang
cc: Mauro Carvalho Chehab
cc: linux-wirel...@vger.kernel.org
cc: de...@driverdev.osuosl.org
---
d
Supply accessor functions to set attributes in proc_dir_entry structs.
The following are supplied: proc_set_size() and proc_set_user().
Signed-off-by: David Howells
cc: linuxppc-...@lists.ozlabs.org
cc: linux-me...@vger.kernel.org
cc: net...@vger.kernel.org
cc: linux-wirel...@vger.kernel.org
cc:
Create a dir under /proc/net/r8180/ named for the device and create that
device's files under there. This means that there won't be a problem for
multiple devices in the system (if such is possible) and it means we don't
need to save the 'device directory' PDE any more as we can just do a proc
sub
Move proc_fd() to fs/proc/fd.h.
Signed-off-by: David Howells
---
fs/proc/fd.h |5 +
fs/proc/internal.h |5 -
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/proc/fd.h b/fs/proc/fd.h
index cbb1d47..7c047f2 100644
--- a/fs/proc/fd.h
+++ b/fs/proc/fd.h
@@ -1
Split the proc namespace stuff out into linux/proc_ns.h.
Signed-off-by: David Howells
cc: net...@vger.kernel.org
cc: Serge E. Hallyn
cc: Eric W. Biederman
---
fs/namespace.c |6 ++--
fs/proc/inode.c |8 ++---
fs/proc/namespaces.c | 17 +++
include/linu
Here is a series of patches to make the procfs internals private to the procfs
filesystem. This is built on top of the patches to eliminate
create_proc_read_entry() after the kill-read_proc_t tag.
These patches include fixes for the places that are attempting to abuse
proc_dir_entry->count and d
Fixed: warning: cast from pointer to integer of different size
Reported-by: kbuild test robot
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/netvsc.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/hyperv/netvsc.c b/dr
On Tue, Apr 16, 2013 at 12:01 PM, Rafael J. Wysocki wrote:
> On Monday, April 15, 2013 02:18:18 PM Bjorn Helgaas wrote:
>> On Fri, Apr 12, 2013 at 11:50 PM, Yinghai Lu wrote:
>> > On Fri, Apr 12, 2013 at 4:58 PM, Rafael J. Wysocki wrote:
>> >> From: Rafael J. Wysocki
>> >>
>> >> Commit b51306c
Supply an accessor function for getting the private data from the parent
proc_dir_entry struct of the proc_dir_entry struct associated with an inode.
ReiserFS, for instance, stores the super_block pointer in the proc directory
it makes for that super_block, and a pointer to the respective seq_file
Use remove_proc_subtree() to remove the airo device subdir and all its
children instead of doing it manually.
Signed-off-by: David Howells
cc: linux-wirel...@vger.kernel.org
---
drivers/net/wireless/airo.c | 49 +++
1 file changed, 13 insertions(+), 36
Use minor->index to label things, not the name field from the proc_dir_entry
of the /proc/dwm// directory.
Also, use "%u" not "%d" to render the value and use a 12-byte buffer in which
to render the integer, not a 16-byte buffer. The longest string an unsigned
int can give you is 10 chars (429496
On Tue, Apr 16, 2013 at 11:21 AM, Linus Torvalds
wrote:
>> What I meant is IF is included by userspace (it sure is
>> meant to be included and *is* included by libfuse and other stuff)
>> THEN using instead of is fine regardless of
>> whether __linux__ is defined or not.
>
> That's probably tru
Don't print proc_dir_entry data in debug as we're soon to have no direct
access to the contents of the PDE. Print what was put in there instead.
Signed-off-by: David Howells
cc: mjpeg-us...@lists.sourceforge.net
cc: linux-me...@vger.kernel.org
---
drivers/media/pci/zoran/zoran_procfs.c |2
Clean up the use of procfs by the dgrp driver:
(1) Use remove_proc_subtree() for the mass slaughter of a subdir full of proc
files rather than doing it manually.
(2) When creating files, only call ID_TO_CHAR() once to generate the name.
Signed-off-by : David Howells
cc: Bill Pemberton
c
Use remove_proc_subtree() rather than remove_proc_entry() to remove a
device-specific proc directory and all its children.
Signed-off-by: David Howells
cc: Jouni Malinen
cc: Johannes Berg
cc: linux-wirel...@vger.kernel.org
cc: de...@driverdev.osuosl.org
---
drivers/net/wireless/hostap/hostap_
Clean up some of the problems with the rtas_flash driver:
(1) It shouldn't fiddle with the internals of the procfs filesystem (altering
pde->count).
(2) If pid namespaces are in effect, then you can get multiple inodes
connected to a single pde, thereby rendering the pde->count > 2 te
Constify drm_proc_list[] and related pointers.
Signed-off-by: David Howells
cc: dri-de...@lists.freedesktop.org
---
drivers/gpu/drm/drm_proc.c |6 +++---
include/drm/drmP.h |2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_proc.c b/drivers
Supply a function (proc_remove()) to remove a proc entry (and any subtree
rooted there) by proc_dir_entry pointer rather than by name and (optionally)
root dir entry pointer. This allows us to eliminate all remaining pde->name
accesses outside of procfs.
Signed-off-by: David Howells
cc: linux-a.
Make the PROC_I() and PDE() macros internal to procfs. This means making
PDE_DATA() out of line. This could be made more optimal by storing
PDE()->data into inode->i_private.
Also provide a __PDE_DATA() that is inline and internal to procfs.
Signed-off-by: David Howells
---
fs/proc/generic.c
Move non-public declarations and definitions from linux/proc_fs.h to
fs/proc/internal.h.
Signed-off-by: David Howells
---
fs/proc/internal.h | 307 ++-
fs/proc/kcore.c |1
include/linux/proc_fs.h | 151 ++-
3 fi
Supply an accessor to get access to the name in a proc_dir_entry struct, just
returning a const pointer to it.
This is only needed by the xt_hashlimit netfilter module as that appears to
use the name in the pde to save a label in the xt_hashlimit_htable struct -
which will be a problem if CONFIG_P
Supply an accessor to get the process ID associated with some proc files and
directories (get_proc_pid()).
Signed-off-by: David Howells
cc: Tejun Heo
cc: Li Zefan
cc: contain...@lists.linux-foundation.org
cc: cgro...@vger.kernel.org
---
fs/proc/base.c |5 +
include/linux/proc
Move some bits from linux/proc_fs.h to linux/of.h, signal.h and tty.h.
Also move proc_tty_init() and proc_device_tree_init() to fs/proc/internal.h as
they're internal to procfs.
Signed-off-by: David Howells
cc: devicetree-disc...@lists.ozlabs.org
cc: linux-a...@vger.kernel.org
cc: Greg Kroah-Har
Clean up the pseries scanlog driver's use of procfs:
(1) Don't need to save the proc_dir_entry pointer as we have the filename to
remove with.
(2) Save the scan log buffer pointer in a static variable (there is only one
of it) and don't save it in the PDE (which doesn't have a destruc
Use remove_proc_subtree() rather than remove_proc_entry() to remove a
minor-specific drm proc directory and all its children.
Things could theoretically be improved by storing the drm_minor pointer in the
minor-specific dir proc_dir_entry struct data and then scrapping the list of
proc files - but
Don't access the proc_dir_entry in ReiserFS's r_open(), r_start() r_show()
procfs interface functions.
ReiserFS stores the ->show() method pointer in PDE->data and the super_block
pointer in PDE->parent->data. This isn't changing.
Currently, ReiserFS passes the PDE pointer into seq_file::private
Add proc_mkdir_data() to allow procfs directories to be created that are
annotated at the time of creation with private data rather than doing this
post-creation. This means no access is then required to the proc_dir_entry
struct to set this.
Signed-off-by: David Howells
cc: Neela Syam Kolli
cc
Move PDE_NET() to fs/proc/proc_net.c as that's where the only user is.
Signed-off-by: David Howells
---
fs/proc/proc_net.c |4
include/linux/proc_fs.h |5 -
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/fs/proc/proc_net.c b/fs/proc/proc_net.c
index b4ac657
Include missing linux/slab.h inclusions where the source file is currently
expecting to get kmalloc() and co. through linux/proc_fs.h.
Signed-off-by: David Howells
cc: linux-s...@vger.kernel.org
cc: sparcli...@vger.kernel.org
cc: linux-...@vger.kernel.org
cc: linux-...@lists.infradead.org
cc: de.
Uninline pid_delete_dentry() as it's only used by three function pointers.
Signed-off-by: David Howells
---
fs/proc/base.c |9 +
fs/proc/internal.h | 14 +-
2 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 593e7c
On Tue, Apr 16, 2013 at 6:28 AM, Thomas Gleixner wrote:
> Hmm, is safe_halt() returning with interrupts disabled? If yes, it
> lacks a local_irq_enable().
Quite probably. Adding arch_local_irq_enable() to arch_safe_halt()
makes all the problems go away. I'll send you the one-line patch
from a sy
Include missing linux/magic.h inclusions where the source file is currently
expecting to get magic numbers through linux/proc_fs.h.
Signed-off-by: David Howells
cc: linux-...@vger.kernel.org
---
drivers/firmware/efivars.c |1 +
fs/proc/inode.c|1 +
2 files changed, 2 inserti
Hi Miklos,
On 4/15/13 7:08 PM, Miklos Szeredi wrote:
On Thu, Dec 20, 2012 at 1:30 PM, Maxim Patlasov wrote:
Hi,
There is a long-standing demand for syncronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.
On Fri, Apr 12, 2013 at 10:56:27AM +0800, Lai Jiangshan wrote:
> On 04/12/2013 01:04 AM, Sebastian Andrzej Siewior wrote:
> > * Lai Jiangshan | 2013-04-09 09:09:56 [+0800]:
> >
> >> If the percpu array can be defined in __SRCU_STRUCT_INIT(),
> >> I'm happy to expose it. but it is not currently.
>
> What I meant is IF is included by userspace (it sure is
> meant to be included and *is* included by libfuse and other stuff)
> THEN using instead of is fine regardless of
> whether __linux__ is defined or not.
That's probably true. But the patch in question adds the __KERNEL__
test, and *that
On Tue, Apr 16, 2013 at 12:15:47PM -0500, Aravind wrote:
> >This one case in point, please redo it against tip/master.
>
> I had based off bp.git's master... and it misses an additional
> 'PCI_DEVICE' line (Hence the conflict)
> I shall redo it against Linus's tree..
No, against tip/maste
On 04/16/2013 11:08 AM, Kees Cook wrote:
> On Fri, Apr 12, 2013 at 1:13 PM, Kees Cook wrote:
>> This splits up the relocs tool changes into the separate logical pieces,
>> which should be easier to review. I could use some suggestions on a
>> better way to build it in the 4th patch. What I have no
Am Dienstag, 16. April 2013, 19:41:34 schrieb Sylwester Nawrocki:
> There is no users of this code and there is already a pinctrl
> driver written for s3c24xx which is going to be used on any
> s3c24xx DT platforms. Hence this has been effectively a dead
> code in mainline.
>
> This reverts commit
On Thu, Apr 11, 2013 at 2:05 AM, Mike Galbraith wrote:
> On Wed, 2013-04-10 at 08:49 -0400, Phil Wilshire wrote:
>> We are using kernel 3.2.21
>>
>> It looks like we are seeing stalls or lockups when allowing rt threads to
>> migrate.
>>
>> The problem has been much reduced by pinning threads to c
On Fri, Apr 12, 2013 at 1:13 PM, Kees Cook wrote:
> This splits up the relocs tool changes into the separate logical pieces,
> which should be easier to review. I could use some suggestions on a
> better way to build it in the 4th patch. What I have now seems ugly,
> but Kbuild would not give me i
On Tue, Apr 16, 2013 at 09:07:20PM +0800, Xiao Guangrong wrote:
> On 04/16/2013 07:43 PM, Robin Holt wrote:
> > Argh. Taking a step back helped clear my head.
> >
> > For the -stable releases, I agree we should just go with your
> > revert-plus-hlist_del_init_rcu patch. I will give it a test
> >
On Tuesday, April 16, 2013 03:14:47 PM Andy Shevchenko wrote:
> On Mon, 2013-04-15 at 22:06 +0530, Vinod Koul wrote:
> > On Tue, Apr 09, 2013 at 02:05:42PM +0300, Andy Shevchenko wrote:
> > > There is a patch series which introduces ACPI DMA helpers in similar way
> > > like
> > > we have for Dev
On 04/15/2013 08:37 PM, zhang.y...@zte.com.cn wrote:
> Hello,
>
Hi Zhang,
I've rewrapped your plain text here for legibility, please adjust your
mail client accordingly.
> The futex-keys of processes share futex determined by page-offset,
> mapping-host, and mapping-index of the user space addre
On Monday, April 15, 2013 02:18:18 PM Bjorn Helgaas wrote:
> On Fri, Apr 12, 2013 at 11:50 PM, Yinghai Lu wrote:
> > On Fri, Apr 12, 2013 at 4:58 PM, Rafael J. Wysocki wrote:
> >> From: Rafael J. Wysocki
> >>
> >> Commit b51306c (PCI: Set device power state to PCI_D0 for device
> >> without nati
Hi Stephen,
On Tue, Apr 16, 2013 at 3:07 AM, Stephen Rothwell wrote:
> On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen wrote:
>> Could you please add:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git#for-next
>>
>> to linux-next to include new stuff coming from Rob?
>
> Well,
On Tue 16-04-13 10:48:35, Rusty Russell wrote:
> Andrew Morton writes:
> > On Fri, 12 Apr 2013 15:28:56 -0700 Kent Overstreet
> > wrote:
> >> Those are the main changes (besides adding attributes, of course) that
> >> I've made so far.
> >>
> >> * Get rid of the parallel syscall interface
>
On Tuesday, April 16, 2013 12:46:11 PM Stephen Rothwell wrote:
> Hi Rafael,
>
> Today's linux-next merge of the pm tree got a conflict in
> drivers/acpi/scan.c between commit 5c0b04e3d913 ("PCI/ACPI: Handle PCI
> slot devices when creating/destroying PCI buses") from the pci tree and
> commit 0a34
Hi,
I am rewriting Marvell Kirkwood/Dove audio driver and I am having
a hard time to match the controllers features to ASoC API.
The controller has a dma controller for one playback buffer. It can
play the stream to both I2S and SPDIF interfaces with independent mute.
Now, for example, I have a
For reproducibility, it can be useful to be able to specify the
seed to use to seed the RNG.
Add a new KCONFIG_SEED environment variable which can be set to
the seed to use:
$ make KCONFIG_SEED=42 randconfig
$ sha1sum .config
70a128c8dcc61303069e1be352cce64114dfcbca .config
$ make
Michal, All,
Here is a short series with a few kconfig improvements and fixes:
- fix in ncurses headers location
- fix randconfig always selecting the first entry of a choice
- enhance randconfig with user-suplied seed and/or probability
I'm posting this series for review before I send Mich
Introduce a KCONFIG_PROBABILITY environment variable to tweak the
probability between 0 (all options off) and 100 (all options on).
[Patch originally written by Peter for Buildroot, see:]
[http://git.buildroot.org/buildroot/commit/?id=3435c1afb5 ]
Signed-off-by: Peter Korsgaard
[yann.morin.1
Currently, randconfig does randomise choice entries, unless KCONFIG_ALLCONFIG
is specified.
For example, given those two files (Thomas' test-case):
---8<--- Config.test.in
config OPTIONA
bool "Option A"
choice
prompt "This is a choice"
config CHOICE_OPTIONA
The current code does this:
if [ -f /usr/include/ncursesw/curses.h ]; then
echo '-I/usr/include/ncursesw -DCURSES_LOC=""'
elif [ -f /usr/include/ncurses/ncurses.h ]; then
echo '-I/usr/include/ncurses -DCURSES_LOC=""'
elif [ -f /usr/include/ncurses/curses.h ]; then
There is no users of this code and there is already a pinctrl
driver written for s3c24xx which is going to be used on any
s3c24xx DT platforms. Hence this has been effectively a dead
code in mainline.
This reverts commit 172c6a13653ac8cd6a231293b87c93821e90c1d6
gpio: samsung: add devicetree init f
rpmsg configuration selects VIRTIO, but VIRTIO is now
subordinate to VIRTUALIZATION. RPMSG is currently selected
by OMAP_REMOTEPROC, and the dependency warning is not seen
with the fix in remoteproc config, but the kconfig menu
hierarchy dependency has to be honored nevertheless.
warning: (VIRTIO_
remoteproc configuration selects VIRTIO, but VIRTIO is now
subordinate to VIRTUALIZATION. VIRTUALIZATION has to be
selected as well to honor the kconfig menu hierarchy and fix
the dependency warnings.
warning: (VIRTIO_PCI && VIRTIO_MMIO && REMOTEPROC && RPMSG) selects VIRTIO
which has unmet direc
Hi,
This fixes the Kconfig dependency warnings for VIRTIO when remoteproc
and/or rpmsg are enabled. I have intentionally split the change into
two patches, based on testing by enabling STE-MODEM-RPROC and
OMAP_REMOTEPROC separately. The former selects just REMOTEPROC, while
the latter selects both
On Tue, Apr 16, 2013 at 06:37:05PM +0200, Joerg Roedel wrote:
> On Tue, Apr 16, 2013 at 09:35:56AM -0400, Neil Horman wrote:
> > Actually, hold on that last note, the intel iommu init code doesn't seem to
> > create any direct relationship between the set of iommu's and the pci_dev's
> > that
> >
Hey,
On Mon, Apr 15, 2013 at 09:02:06AM -0400, Mikulas Patocka wrote:
> The patch is not bug-prone, because we already must make sure that the
> cloned bio has shorter lifetime than the master bio - so the patch doesn't
> introduce any new possibilities to make bugs.
The whole world isn't compo
On Tue, Apr 16, 2013 at 5:59 PM, Linus Torvalds
wrote:
> On Tue, Apr 16, 2013 at 7:21 AM, Miklos Szeredi wrote:
>>
>> And I still disagree. Why should userspace use the linux internal
>> header when there's a perfectly good standard header that it can use?
>
> If it's called UAPI, it damn well i
+/* r3 = n (where n = [0-1023])
+ * The maximum number of BHRB entries supported with PPC_MFBHRBE
instruction
+ * is 1024. We have limited number of table entries here as POWER8
implements
+ * 32 BHRB entries.
+ */
+
+/* .global read_bhrb */
+_GLOBAL(read_bhrb)
+ cmpldi r3,1023
This
Benjamin, All,
On Tue, Apr 16, 2013 at 10:07:23AM -0400, Benjamin Poirier wrote:
> Displays a trail of the menu entries used to get to the current menu.
>
> Signed-off-by: Benjamin Poirier
> Tested-by: "Yann E. MORIN"
> [yann.morin.1...@free.fr: small, trivial code re-ordering]
> Signed-off-by:
Hello,
On Tue, Apr 16, 2013 at 5:14 AM, Namhyung Kim wrote:
>> The problem is that I didn't have python-devel package installed and
>> get-executable-or-default decides to error out instead of letting the
>> Makefile disable Python support.
>
> Right. I think the get-executable-or-default should
On 04/16/2013 09:24 AM, Borislav Petkov wrote:
On Mon, Apr 15, 2013 at 01:56:00PM -0500, Aravind Gopalakrishnan wrote:
Add code to handle ECC decoding for fam16h. Support exists for
previous families already, so code has been reused werever applicable
and some code has been added to handle fam16
On Mon, 15 Apr 2013 21:26:40 -0700, David Ahern wrote:
> On 4/15/13 7:14 PM, Namhyung Kim wrote:
>>> Makefile:755: The path '/usr/bin/python-config' is not executable.
>>> Makefile:755: *** Please set 'PYTHON_CONFIG' appropriately. Stop.
>>>
>>> The problem is that I didn't have python-devel pack
Hello, Li.
On Tue, Apr 16, 2013 at 07:17:17PM +0800, Li Zefan wrote:
...
> > hot-unplug). It currently transfers all its tasks to the nearest
> > ancestor with executing resources, which is an irreversible process
> > which would affect all other co-mounted controllers. We probably want
> > it t
A clock's notifier count only reflects notifiers which are registered
directly for that clock. A reparent operation though affects the whole
subtree because of a potential rate change.
When issuing the pre rate change notifications only the notifier count
for the clock to be changed is considered a
On 04/15/2013 08:02 PM, zhang.y...@zte.com.cn wrote:
> From: Zhang Yi
>
> Hello,
Hi Zhang,
I think you've attempted to address this with your second futex patch,
but please use plain text email on LKML, especially for patches. Ensure
to linewrap your plain text email and avoid mid-line breaks as
From: H Hartley Sweeten
This driver now uses the module_pcmcia_driver() macro to supply the
init/exit code. The nsp_cs_{init,exit} prototypes should be removed.
Reported-by: kbuild test robot
Signed-off-by: H Hartley Sweeten
Cc: YOKOTA Hiroshi
Cc: "James E.J. Bottomley"
Signed-off-by: Greg K
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Bilovol, Ruslan
> Sent: Tuesday, April 16, 2013 9:12 PM
> To: Balbi, Felipe; gre...@linuxfoundation.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject:
Hi Bengt,
This serial also needs your review.
Thanks,
Axel
2013/4/9 Axel Lin :
> This patch ensures info->update_val is consistent with current register value.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/ab8500.c | 20 +++-
> 1 file changed, 11 insertions(+), 9 dele
From: H Hartley Sweeten
Use the new module_pcmcia_driver() macro to remove the boilerplate
module init/exit code in the pcmcia drivers.
Signed-off-by: H Hartley Sweeten
Signed-off-by: Greg Kroah-Hartman
---
Note, this needs the module_pcmcia_driver() macro, which is in my
char-misc-next branc
When setting voltage for AB8540_LDO_AUX3, current code only updates one of
info->voltage_reg and info->expand_register registers which is wrong.
To ensure we set to correct voltage, it always needs to clear or set
expand_register.voltage_mask bit of expand_register.
The function of the expand regi
From: "Paul E. McKenney"
Signed-off-by: Paul E. McKenney
Cc: Frederic Weisbecker
Cc: Steven Rostedt
Cc: Borislav Petkov
Cc: Arjan van de Ven
Cc: Kevin Hilman
Cc: Christoph Lameter
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Olivier Baetz
Reviewed-by: Randy Dunlap
Reviewed-by: Borislav P
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should generally only be used when standard I2C
I am having fun wit
From: "Paul E. McKenney"
The Linux kernel uses a number of per-CPU kthreads, any of which might
contribute to OS jitter at any time. The usual approach to normal
kthreads, namely to bind them to a "housekeeping" CPU, does not work
with these kthreads because they cannot operate correctly if move
Hello!
This is v3 of the OS-jitter-reduction documentation.
Changes from v2 (https://lkml.org/lkml/2013/4/11/337 and
https://lkml.org/lkml/2013/4/11/338):
o Updated both patches based on review feedback.
Changes from v1 (https://lkml.org/lkml/2013/3/18/462):
o Updated the nohz1 pat
On 16/04/13 15:31, Sergey Vlasov wrote:
> Fixes build with CONFIG_EFI_VARS=m which was broken after the commit
> "x86, efivars: firmware bug workarounds should be in platform code".
>
> Signed-off-by: Sergey Vlasov
> ---
> arch/x86/platform/efi/efi.c | 1 +
> 1 file changed, 1 insertion(+)
Appl
On 16/04/13 15:31, Sergey Vlasov wrote:
> The commit "efi: Distinguish between "remaining space" and actually used
> space" added usage of ucs2_*() functions to arch/x86/platform/efi/efi.c,
> but the only thing which selected UCS2_STRING was EFI_VARS, which is
> technically optional and can be buil
On Tue 09-04-13 16:06:39, majianpeng wrote:
> After allocating a inode,it don't chain in superblock.At this time,it
> won't be used by others.So it make no sense to protect there.
Something (likely your mailer) has mangled whitespace in your patch.
Please submit patches with a program that preser
On Thu 11-04-13 16:47:59, Dmitry Monakhov wrote:
> There are two convenient ways to report errors to userspace
> 1) retun error to original syscall for example write(2)
> 2) mark mapping with error flag and return it on later fsync(2)
>
> Second one is broken if (mapping->nrpages == 0)
> This is r
Michal, All,
On Tue, Apr 16, 2013 at 11:12:41AM +0200, Michal Marek wrote:
> > On 15.4.2013 23:54, Yann E. MORIN wrote:
> >> So, unless Michal really wants to pull this one and push it to Linus
> >> before he cuts v3.9 final, I'll merge this later in my -for-next branch.
> BTW, in you are going to
On Sat 13-04-13 12:36:50, Marco Stornelli wrote:
> Replace file_start_write with file_start_write_killable where
> possible.
Looks good. You can add:
Reviewed-by: Jan Kara
Honza
>
> Signed-off-by: Marco Stornelli
> ---
> driver
On Sat 13-04-13 12:38:18, Marco Stornelli wrote:
> Replace sb_start_write with sb_start_write_killable where
> possible.
Looks good. You can add:
Reviewed-by: Jan Kara
Honza
>
> Signed-off-by: Marco Stornelli
> ---
> fs/open.c
On Tue, Apr 16, 2013 at 09:35:56AM -0400, Neil Horman wrote:
> Actually, hold on that last note, the intel iommu init code doesn't seem to
> create any direct relationship between the set of iommu's and the pci_dev's
> that
> implement them. In the intel_irq_remapping_supported path I can loop ov
On Sun 14-04-13 23:34:27, Dmitry Monakhov wrote:
> Callers may use this counter to optimize flushes
>
> Signed-off-by: Dmitry Monakhov
> ---
> block/blk-core.c |1 +
> block/blk-flush.c |3 ++-
> include/linux/blkdev.h |1 +
> 3 files changed, 4 insertions(+), 1 deletions(
On Sat 13-04-13 12:35:54, Marco Stornelli wrote:
> Added a new enum to decide if we want to sleep in uninterruptible or
> killable state or we want simply to return immediately.
I like the patch. You can add:
Reviewed-by: Jan Kara
On Fri 12-04-13 04:20:18, Alexandru Gheorghiu wrote:
> Use kstrdup function instead of kmalloc and strcpy.
> Patch found using coccinelle.
Thanks for the patch but I already have a similar patch in my tree.
Honza
>
> Signed
On Tue, Apr 16, 2013 at 09:29:02AM -0700, Doug Anderson wrote:
> 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
Acked-by: Olof Johansson
-Olof
--
On Tue, Apr 16, 2013 at 09:29:01AM -0700, Doug Anderson wrote:
> We need to use the i2c-arbitrator to talk to any of the devices on i2c
> bus 4 on exynos5250-snow so that we don't confuse the embedded
> controller (EC). Add the i2c-arbitrator to the device tree. As we
> add future devices (keyboa
Overdue, should have added a few iterations ago: :)
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should generall
On Mon, Apr 15, 2013 at 05:13:45PM -0700, D M German wrote:
>
>
> Greg KH twisted the bytes to say:
>
> >> http://o.cs.uvic.ca:20810/perl/next.pl
>
> Greg> Yes, that's a great thing. Maybe the ability to see the subject: line
> Greg> of the commit somewhere easier than having to click thro
We need to use the i2c-arbitrator to talk to any of the devices on i2c
bus 4 on exynos5250-snow so that we don't confuse the embedded
controller (EC). Add the i2c-arbitrator to the device tree. As we
add future devices (keyboard, sbs, tps65090) we'll add them on top of
this.
The arbitrated bus i
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 v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally only be used when standard I2C
multimaster isn't appropriate for some reason (errata/bugs).
This driver is based on cod
Can you try this patch?
diff --git a/drivers/platform/x86/hp-wmi.c
b/drivers/platform/x86/hp-wmi.c
index 45cacf7..91cc5df 100644
--- a/drivers/platform/x86/hp-wmi.c
+++ b/drivers/platform/x86/hp-wmi.c
@@ -53,6 +53,7 @@
MODULE_ALIAS("wmi:5FB7F034-2C63-45e9-BE91-3D44E2C707E4");
#define HPWMI_ALS_QU
On Tue, Apr 16, 2013 at 6:51 AM, Samuel Ortiz wrote:
> Hi Mauro,
>
> On Wed, Apr 10, 2013 at 06:48:28AM -0300, Mauro Carvalho Chehab wrote:
>> Em Wed, 10 Apr 2013 08:42:53 +0200
>> Samuel Ortiz escreveu:
>>
>> > Hi Stephen,
>> >
>> > On Wed, Apr 10, 2013 at 01:48:13PM +1000, Stephen Rothwell wrot
201 - 300 of 555 matches
Mail list logo