Hi all,
while working with regulators, I noticed that there is no
devm_regulator_enable() API.
Seems to me it would be useful to have it, but then devm_clk_enable() doesn't
exist either,
so I wonder if there is a reason for not having it.
I'll be happy to submit a patch if people think it is
On 02/01/2014 03:59 PM, Andy Lutomirski wrote:
If it is, indeed, okay to use non-fixed maps on 32-bit, it might
also be okay on 64-bit. If so, it could be useful to implement that,
which would remove a bit of a wart and allow PR_SET_TSC to work
usefully for 64-bit userspace. (This would
On Sat, Feb 1, 2014 at 4:26 PM, H. Peter Anvin h...@zytor.com wrote:
On 02/01/2014 03:59 PM, Andy Lutomirski wrote:
If it is, indeed, okay to use non-fixed maps on 32-bit, it might
also be okay on 64-bit. If so, it could be useful to implement that,
which would remove a bit of a wart and
Yes, that we can move, of course.
On February 1, 2014 4:30:17 PM PST, Andy Lutomirski l...@amacapital.net wrote:
On Sat, Feb 1, 2014 at 4:26 PM, H. Peter Anvin h...@zytor.com wrote:
On 02/01/2014 03:59 PM, Andy Lutomirski wrote:
If it is, indeed, okay to use non-fixed maps on 32-bit, it
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
To avoid the need to install a hotplug notify handler for each ACPI
namespace node representing a device and having a matching scan
handler, move the check whether or not the ejection of the given
device is enabled through its scan handler from
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_hotplug_notify_cb() does not use its data argument any
more, the second argument of acpi_install_hotplug_notify_handler()
can be dropped, so do that and update its callers accordingly.
Signed-off-by: Rafael J. Wysocki
On Wednesday, January 29, 2014 12:57:06 AM Rafael J. Wysocki wrote:
On Tuesday, January 28, 2014 11:10:30 PM Rafael J. Wysocki wrote:
Hi All,
It looks like there's time for more adventurous stuff. :-)
The following series is on top of the one I sent on Sunday:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
There is a slight possibility for the ACPI device object pointed to
by adev in acpi_hotplug_notify_cb() to become invalid between the
acpi_bus_get_device() that it comes from and the subsequent get_device().
Namely, if acpi_scan_drop_device()
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_bus_notify() is executed on all notifications for all
devices anyway, rename acpi_hotplug_notify_cb() to acpi_system_notify()
and call it directly from acpi_bus_notify() instead of installing
notify handlers pointing to it for all
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The ACPI-based PCI hotplug (ACPIPHP) code currently attaches its
hotplug context objects directly to ACPI namespace nodes representing
hotplug devices. However, after recent changes causing struct
acpi_device to be created for every namespace
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Subsequent changes will require the ACPI core to acquire the lock
protecting the ACPIPHP hotplug contexts, so move the definition of
the lock to the core and change its name to be more generic.
Signed-off-by: Rafael J. Wysocki
From: Max Filippov jcmvb...@gmail.com
Date: Fri, 31 Jan 2014 09:41:03 +0400
Hello David, Ben, Florian and everybody,
this series implements ethtool callbacks for the ethoc driver as was
requested by Florian.
Changes v1-v2:
- fix {get,set}_settings return code in case there's no PHY;
-
On 02/01/2014 04:41 PM, H. Peter Anvin wrote:
Right. But there's some obscure ABI reason for CONFIG_COMPAT_VDSO,
and if this breaks it, then it's no good. From extremely vague
memory, there's some version of SuSE that breaks if the 32-bit vdso
moves. I have no idea what the bug is, but
From: K. Y. Srinivasan k...@microsoft.com
Date: Fri, 31 Jan 2014 08:24:38 -0800
Some minor cleanup of the receive path. Get rid of unnecessary
indirection as well as unnecessary re-establishment of state.
It is not appropriate to submit cleanups at this time.
Please wait until the net-next
On Sat, Feb 1, 2014 at 11:27 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
That said, regardless of the allocation issue, I do think that it's
stupid for kernel_fpu_{begin,end} to save the math state if
used_math was not set. So I do think__kernel_fpu_end() as-s is
buggy and stupid.
OK, let's circle back for a bit. We have an active bug, and we clearly
have a lot of restructuring that could/should be done. We need to fix
the bug first; if we're going to a bunch of restructuring then that
ought to be separate. The first bit is how we fix the immediate bug.
Well, that's
On 02/01/2014 05:19 PM, George Spelvin wrote:
OK, let's circle back for a bit. We have an active bug, and we clearly
have a lot of restructuring that could/should be done. We need to fix
the bug first; if we're going to a bunch of restructuring then that
ought to be separate. The first bit
On 02/01/2014 05:06 PM, Suresh Siddha wrote:
so I will Ack for option b, as option a breaks the features which
don't take into account cr0.TS.
Even b does that, no? a should be fine as long as we don't ever use
those features in the kernel, even under kernel_fpu_begin/end().
Meanwhile I
On Sun, Feb 2, 2014 at 12:15 AM, David Rientjes rient...@google.com wrote:
On Thu, 30 Jan 2014, Chris Mason wrote:
Hi Linus
Please pull my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
There are two conflicts right now, one with the ACL
On Sat, Feb 1, 2014 at 5:26 PM, H. Peter Anvin h...@zytor.com wrote:
Even b does that, no?
oh right. It needs an else. only for non-eager fpu case we should do stts()
void __kernel_fpu_end(void)
{
if (use_eager_fpu()) {
struct task_struct *me = current;
On Sat, Feb 1, 2014 at 5:35 PM, Suresh Siddha sbsid...@gmail.com wrote:
On Sat, Feb 1, 2014 at 5:26 PM, H. Peter Anvin h...@zytor.com wrote:
Even b does that, no?
oh right. It needs an else. only for non-eager fpu case we should do stts()
It definitely does not want an else, I think.
If
What does the inner if clause do? It looks like it returns either way...
On February 1, 2014 5:35:13 PM PST, Suresh Siddha sbsid...@gmail.com wrote:
On Sat, Feb 1, 2014 at 5:26 PM, H. Peter Anvin h...@zytor.com wrote:
Even b does that, no?
oh right. It needs an else. only for non-eager fpu case
On Sat, Feb 1, 2014 at 5:38 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
It definitely does not want an else, I think.
If tsk_used_math() is false, or if the FPU restore failed, we
*definitely* need that stts(). Otherwise we'd return to user mode with
random contents in the FP
On Sat, Feb 1, 2014 at 5:43 PM, H. Peter Anvin h...@zytor.com wrote:
What does the inner if clause do? It looks like it returns either way...
Suresh broke it with his suggested version.
The inner if-statement is supposed to avoid the stts *if* we had used
math *and* the FPU restore worked.
But
On Sat, Feb 1, 2014 at 5:47 PM, Suresh Siddha sbsid...@gmail.com wrote:
So if the restore failed, we should do something like drop_init_fpu(),
which will restore init-state to the registers.
for eager-fpu() paths we don't use clts() stts() etc.
Uhhuh. Ok.
Why do we do that, btw? I think it
On 02/01/2014 05:51 PM, Linus Torvalds wrote:
On Sat, Feb 1, 2014 at 5:47 PM, Suresh Siddha sbsid...@gmail.com wrote:
So if the restore failed, we should do something like drop_init_fpu(),
which will restore init-state to the registers.
for eager-fpu() paths we don't use clts() stts() etc.
On Sat, Feb 1, 2014 at 5:51 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sat, Feb 1, 2014 at 5:47 PM, Suresh Siddha sbsid...@gmail.com wrote:
So if the restore failed, we should do something like drop_init_fpu(),
which will restore init-state to the registers.
for eager-fpu()
On Sat, Feb 1, 2014 at 5:57 PM, H. Peter Anvin h...@zytor.com wrote:
Twiddling CR0.TS is pretty slow if we're not taking advantage of it.
Immaterial.
We *already* avoid twiddling TS if it's not needed.
It is true that we used to twiddle it at every context switch (and
then twiddle it *again*
The current channel code is using scatterlist abstraction to pass data to the
ringbuffer API on the send path. This causes unnecessary translations
between virtual and physical addresses. Fix this.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
---
drivers/hv/channel.c | 42
Yes, that is exactly the eageronly features - currently LWP and MPX.
On February 1, 2014 6:05:05 PM PST, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sat, Feb 1, 2014 at 5:57 PM, H. Peter Anvin h...@zytor.com wrote:
Twiddling CR0.TS is pretty slow if we're not taking advantage of it.
On a stock Fedora installation:
$ sudo auditctl -l
No rules
Nonetheless TIF_SYSCALL_AUDIT is set and the __audit_syscall_entry and
__audit_syscall_exit account for 20% of syscall overhead according to
perf.
This sucks. Unless I'm missing something, syscall auditing is *off*.
How hard would it
On Sun, 2 Feb 2014, Filipe David Manana wrote:
Btrfs: fix btrfs boot when compiled as built-in (+73/-9)
This one, 14a958e678cd (Btrfs: fix btrfs boot when compiled as
built-in), breaks the build if CONFIG_LIBCRC32C=m:
fs/built-in.o: In function `btrfs_check_super_csum':
(2014/02/01 21:17), Chen Gang wrote:
When CONFIG_KRETPROBES disabled, cleanup_rp_inst() is useless too. It
is only called by unregister_kretprobes() which is in CONFIG_KRETPROBES
enabled area.
The related warning (allmodconfig under avr32):
kernel/kprobes.c:1181: warning:
On Sat, Feb 1, 2014 at 6:32 PM, Andy Lutomirski l...@amacapital.net wrote:
On a stock Fedora installation:
$ sudo auditctl -l
No rules
Nonetheless TIF_SYSCALL_AUDIT is set and the __audit_syscall_entry and
__audit_syscall_exit account for 20% of syscall overhead according to
perf.
This
From: H. Peter Anvin h...@linux.intel.com
We have two APIs for compatiblity timespec/val, with confusingly
similar names. compat_(get|put)_time(val|spec) *do* handle the case
where COMPAT_USE_64BIT_TIME is set, whereas
(get|put)_compat_time(val|spec) do not. This is an accident waiting
to
From: Shaibal Dutta shaibal.du...@broadcom.com
Allow the scheduler to select the best CPU to handle hub initalization
and LED blinking work. This extends idle residency times on idle CPUs
and conserves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc: Greg
When using hid_output_report(), the buffer should be allocated by
hid_alloc_report_buf(),
not a custom malloc.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/hid-input.c | 2 +-
drivers/hid/i2c-hid/i2c-hid.c | 2 +-
2 files changed, 2 insertions(+), 2
On Fri, 2014-01-31 at 15:34 +0100, Sebastian Andrzej Siewior wrote:
irq_work is processed in softirq context on -RT because we want to avoid
long latencies which might arise from processing lots of perf events.
The noHZ-full mode requires its callback to be called from real hardirq
context
It was missing, so adding it.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/uhid.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/hid/uhid.c b/drivers/hid/uhid.c
index f5a2b19..438c9f1 100644
--- a/drivers/hid/uhid.c
+++
struct hid_ll_driver is responsible for the transport communication.
Move hid_output_raw_report from hid_device to the transport layer then.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/hid-input.c| 2 +-
drivers/hid/hid-logitech-dj.c | 2 +-
Add a helper to access hdev-hid_output_raw_report().
To convert the drivers, use the following snippets:
for i in drivers/hid/*.c
do
sed -i.bak s/[^ \t]*-hid_output_raw_report(/hid_output_raw_report(/g $i
done
Then manually fix for checkpatch.pl
Signed-off-by: Benjamin Tissoires
dev-hid_get_raw_report(X) and hid_hw_raw_request(X, HID_REQ_GET_REPORT)
are strictly equivalent. Switch the hid subsystem to the hid_hw notation
and remove the field .hid_get_raw_report in struct hid_device.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
All the different transport drivers use now the generic event handling
in hid-input. We can remove the handler definitively now.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/hid-input.c | 4 +---
include/linux/hid.h | 4
2 files changed, 1
Well, no use to keep twice the same code.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/usbhid/hid-core.c | 64 ---
1 file changed, 11 insertions(+), 53 deletions(-)
diff --git a/drivers/hid/usbhid/hid-core.c
hidp uses its own -hidinput_input_event() instead of the generic binding
in hid-input.
Moving the handling of LEDs towards hidp_hidinput_event() allows two things:
- remove hidinput_input_event definitively from struct hid_device
- hidraw user space programs can also set the LEDs
Signed-off-by:
- Move hidp_output_report() above
- Removed duplicated code in hidp_output_raw_report()
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
net/bluetooth/hidp/core.c | 68 ---
1 file changed, 11 insertions(+), 57 deletions(-)
diff
Hi guys,
This is an attempt to complete the branch for-3.15/ll-driver-new-callbacks:
- try to implement as much as possible ll_driver callbacks (some are still
missing, but I did not had the time to complete it)
- add inliners hid_hw_* for all the ll_driver callbacks
- remove transport
hid-logitech-dj uses its own -hidinput_input_event() instead of
the generic binding in hid-input.
Moving the handling of LEDs towards logi_dj_output_hidraw_report()
allows two things:
- remove hidinput_input_event in struct hid_device
- hidraw user space programs can also set the LEDs
Add output_report and raw_request to i2c-hid.
Hopefully, we will manage to have the same transport level between
all the transport drivers.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/i2c-hid/i2c-hid.c | 24
1 file changed, 24
Those callbacks are not mandatory, so it's better to add inliners
to use them safely.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
include/linux/hid.h | 45 +
1 file changed, 45 insertions(+)
diff --git a/include/linux/hid.h
From: Namjae Jeon namjae.j...@samsung.com
Add new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate.
updated detailed semantics in comments.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
fs/open.c | 24
From: Namjae Jeon namjae.j...@samsung.com
This patch series is in response of the following post:
http://lwn.net/Articles/556136/
ext4: introduce two new ioctls
Dave chinner suggested that truncate_block_range
(which was one of the ioctls name) should be an fallocate operation
and not any fs
From: Namjae Jeon namjae.j...@samsung.com
Add support FALLOC_FL_COLLAPSE_RANGE for fallocate.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
fs/xfs/xfs_bmap.c | 195
From: Namjae Jeon namjae.j...@samsung.com
Add support FALLOC_FL_COLLAPSE_RANGE for fallocate
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
fs/ext4/ext4.h |3 +
fs/ext4/extents.c | 297
From: Namjae Jeon namjae.j...@samsung.com
Add support FALLOC_FL_COLLAPSE_RANGE for fallocate.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
Reviewed-by: Dave Chinner dchin...@redhat.com
---
io/prealloc.c | 41
From: Namjae Jeon namjae.j...@samsung.com
This testcase(001) tries to test various corner cases
for fcollapse range functionality over different type of extents.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
common/punch |
From: Namjae Jeon namjae.j...@samsung.com
This testcase(002) tries to test various corner cases with delayed extents
for fcollapse range functionality over different type of extents.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
Page migration will fail for memory that is pinned in memory with, for
example, get_user_pages(). In this case, it is unnecessary to take
zone-lru_lock or isolating the page and passing it to page migration
which will ultimately fail.
This is a racy check, the page can still change from under
From: Namjae Jeon namjae.j...@samsung.com
This testcase(004) tries to test various corner cases with delayed extents and
pre-existing holes for fcollapse range functionality
over different type of extents.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan
From: Namjae Jeon namjae.j...@samsung.com
This testcase(003) tries to test various corner cases with pre-existing holes
for fcollapse range functionality over different type of extents.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
From: Namjae Jeon namjae.j...@samsung.com
We execute collapse range multiple times on same file.
Each collapse range call collapses a single alternate block.
After the test execution, file will be left with 80 blocks and
as much number of extents.
We also check for file system consistency after
From: Namjae Jeon namjae.j...@samsung.com
Update FALLOC_FL_COLLAPSE_RANGE flag in fallocate.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish Sangwan a.sang...@samsung.com
---
man2/fallocate.2 | 21 +
1 file changed, 21 insertions(+)
diff --git
Commit-ID: 170750c108bb9382f32a2a99d097aa07d551a89e
Gitweb: http://git.kernel.org/tip/170750c108bb9382f32a2a99d097aa07d551a89e
Author: Petr Tesarik ptesa...@suse.cz
AuthorDate: Sat, 1 Feb 2014 13:30:19 +0100
Committer: H. Peter Anvin h...@zytor.com
CommitDate: Sat, 1 Feb 2014 21:57:48
Commit-ID: 85fc73a2cdf10cf42bc36fb3bca3896b2095a1c2
Gitweb: http://git.kernel.org/tip/85fc73a2cdf10cf42bc36fb3bca3896b2095a1c2
Author: Petr Tesarik ptesa...@suse.cz
AuthorDate: Sat, 1 Feb 2014 13:30:19 +0100
Committer: H. Peter Anvin h...@zytor.com
CommitDate: Sat, 1 Feb 2014 22:15:51
Some very trivial comments below:
On Fri, Jan 31, 2014 at 10:16 PM, Alexandre Courbot acour...@nvidia.com wrote:
Add support for initializing the priv ring of GK20A. This is done by the
BIOS on desktop GPUs, but needs to be done by hand on Tegra.
Signed-off-by: Alexandre Courbot
On 01/31/14 16:24, Andrew Morton wrote:
On Wed, 29 Jan 2014 22:24:11 -0600 Rob Landley r...@landley.net wrote:
On 01/29/14 18:27, Henrik Austad wrote:
Some of the 00-INDEX files are somewhat outdated and some folders does not
contain 00-INDEX at all. Only outdated (with the notably exception
On Sat, Feb 01, 2014 at 10:43:11AM -0800, Linus Torvalds wrote:
On Fri, Jan 31, 2014 at 6:32 AM, Greg KH gre...@linuxfoundation.org wrote:
Here's a single staging driver for a wireless chipset that has shown up
in the SteamBox hardware. It is merged separately from the main
staging pull
On Sat, 2014-02-01 at 17:06 -0800, Suresh Siddha wrote:
Meanwhile I have the patch removing the delayed dynamic allocation for
non-eager fpu. will post it after some testing.
Appended the patch for this. Tested for last 4-5 hours on my laptop.
The real fix for Nate's problem will be coming
301 - 368 of 368 matches
Mail list logo
