Commit-ID: f0905c5a32ce6e9b743b4d9c70e53d1ce447852d
Gitweb: http://git.kernel.org/tip/f0905c5a32ce6e9b743b4d9c70e53d1ce447852d
Author: Andy Lutomirski
AuthorDate: Fri, 12 Dec 2014 16:25:47 -0800
Committer: Ingo Molnar
CommitDate: Sun, 14 Dec 2014 08:47:22 +0100
MAINTAINERS: Add me as
On Dec 13, 2014 10:58 PM, "Stephen Rothwell" wrote:
>
> Hi Andy,
>
> The luto-misc tree seems to have a whole series of commits in it that
> have just bee removed from the rcu tree ... You really have to be very
> careful if you base your work on a tree that is regularly rebased.
Hmm. They
On Tue, Nov 4, 2014 at 7:31 AM, Tim Kryger wrote:
> On Tue, Nov 4, 2014 at 1:00 AM, Alexandre Courbot wrote:
>> Hi Tim, thanks for your reply!
>>
>> On 11/04/2014 02:28 PM, Tim Kryger wrote:
>>>
>>> On Mon, Nov 3, 2014 at 7:05 PM, Alexandre Courbot
[..]
After bisecting I tracked commit
Hi Andy,
The luto-misc tree seems to have a whole series of commits in it that
have just bee removed from the rcu tree ... You really have to be very
careful if you base your work on a tree that is regularly rebased.
I also wonder if the other commits in that tree are destined for
v3.19? If
To be future-proof and for better readability the time comparisons are
modified to use time_after() instead of plain, error-prone math.
Signed-off-by: Asaf Vertz
---
drivers/media/dvb-frontends/stb0899_drv.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git
This is to announce a resync and update of the Brain Fuck Scheduler,
version 0.460 for the latest stable linux kernel.
The patch against linux-3.18(.x) is available here:
http://ck.kolivas.org/patches/bfs/3.0/3.18/3.18-sched-bfs-460.patch
A -ck branded linux-3.18-ck1 patch is available here:
On Sat, Dec 13, 2014 at 9:20 PM, Steve French wrote:
> Probably harmless patch - but I didn't notice the warning on x86
> kernel build (building on Fedora 21, gcc 4.9.2)
Did you test x86 32-bit or 64-bit? In the generic do_div()
implementation, only the former case has an explicit type check.
Probably harmless patch - but I didn't notice the warning on x86
kernel build (building on Fedora 21, gcc 4.9.2)
On Fri, Dec 12, 2014 at 11:19 AM, Kevin Cernekee wrote:
> On Mon, Nov 10, 2014 at 1:09 PM, Kevin Cernekee wrote:
>> Commit 2ae83bf93882d1 ("[CIFS] Fix setting time before epoch
Hi,
My Linux virtual machine on (Windows) VMWare workstation 10 can't boot with
following commit.
commit bd809af16e3ab1f8d55b3e2928c47c67e2a865d2
Author: Juergen Gross
Date: Mon Nov 3 14:02:03 2014 +0100
x86: Enable PAT to use cache mode translation tables
Unfortunately I can't see
On Fri, Dec 12, 2014 at 05:08:56PM -0500, Lennart Sorensen wrote:
> Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
> crystal is not enabled at power up. Instead the CPU falls back to using
> an emulation for the 32KHz clock which is SYSCLK1/610. SYSCLK1 is usually
>
On Sat, Dec 13, 2014 at 03:41:52PM -0500, Dave Jones wrote:
> On Sat, Dec 13, 2014 at 10:04:08AM -0800, Paul E. McKenney wrote:
> > On Sat, Dec 13, 2014 at 11:59:15AM -0500, Dave Jones wrote:
> > > On Fri, Dec 12, 2014 at 11:14:06AM -0800, Linus Torvalds wrote:
> > > > On Fri, Dec 12, 2014 at
On Sat, 13 Dec 2014, Davidlohr Bueso wrote:
> On Fri, 2014-12-12 at 16:56 -0800, a...@linux-foundation.org wrote:
> > From: Hugh Dickins
> > Subject: mm: unmapped page migration avoid unmap+remap overhead
> >
> > Page migration's __unmap_and_move(), and rmap's try_to_unmap(), were
> > created
Jianjian,
> How about invalidating previous writes on same sector address? if
> first write is stored in one 512KB log in SSD, later when user write
> the same address, will writeboost invalid old write by updating meta
> data header in place in that 512KB log? and other meta data like
>
On Sat, Dec 13, 2014 at 05:35:17PM -0800, Linus Torvalds wrote:
> On Sat, Dec 13, 2014 at 4:33 PM, Al Viro wrote:
> >
> > So does SMP - this_cpu_dec() relies on preemption being disabled.
>
> No. really. It very much does not. Not on x86, not elsewhere. It's
> part of the whole point of
Hi Paul,
As per my understanding, for BULK OUT we do queue a request with 512
bytes length since we do not
know the length of the transfer Host is going to send. For Control OUT
we know the length in wLength of
Setup packet, hence I assumed there is no difference in programming
model of Control
On Fri, 2014-12-12 at 16:56 -0800, a...@linux-foundation.org wrote:
> From: Hugh Dickins
> Subject: mm: unmapped page migration avoid unmap+remap overhead
>
> Page migration's __unmap_and_move(), and rmap's try_to_unmap(), were
> created for use on pages almost certainly mapped into userspace.
Hi,
I've just measured how split affects.
I think seqread can make the discussion solid
so these are the cases of reading 6.4GB (64MB * 100) sequentially.
HDD:
64MB read
real 2m1.191s
user 0m0.000s
sys 0m0.470s
Writeboost (HDD+SSD):
64MB read
real 2m13.532s
user 0m0.000s
On Sat, Dec 13, 2014 at 6:07 AM, Akira Hayakawa wrote:
> Hi,
>
> Jianjian, You really get a point at the fundamental design.
>
>> If I understand it correctly, the whole idea indeed is very simple,
>> the consumer/provider and circular buffer model. use SSD as a circular
>> write buffer, write
Hello,this is Mr Paul N,i sent you an email on charity work but i am yet
to hear fom you,do reply with this code CHA-2015 to my email address
paulchar...@qq.com i Look forward to hearing from you this time,God
bless Brother Paul
--
To unsubscribe from this list: send the line "unsubscribe
On Saturday 13 December 2014 05:17 PM, Muthu Mani wrote:
Adds support for USB-I2C interface of Cypress Semiconductor
CYUSBS234 USB-Serial Bridge controller.
The read/write operation is setup using vendor command through control endpoint
and actual data transfer happens through bulk in/out
On Saturday 13 December 2014 05:17 PM, Muthu Mani wrote:
Adds support for USB-GPIO interface of Cypress Semiconductor
CYUSBS234 USB-Serial Bridge controller.
The GPIO get/set can be done through vendor command on control endpoint
for the configured gpios.
Details about the device can be found
Hi,
> The major reason is, it needs to read full 512KB segment to calculate
> checksum to
> know if the log isn't half written.
> (Read 500GB SSD that performs 500MB/sec seqread spends 1000secs)
I've just measured how long the cache resuming is.
I use 2GB SSD for the cache device.
512KB
hi Linus,
please pull these three patches.
I did have a largish set of locking changes queued, but late testing showed
they weren't quite as stable as I thought and while I fixed what I found, I
decided it safer to delay them a release ... particularly as I'll be AFK for
a few weeks. So
On Sat, Dec 13, 2014 at 4:33 PM, Al Viro wrote:
>
> So does SMP - this_cpu_dec() relies on preemption being disabled.
No. really. It very much does not. Not on x86, not elsewhere. It's
part of the whole point of "this_cpu_p()". They are preemption and
interrupt safe.
It's the "__this_cpu_op()"
Hi Daniel,
> On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter
> wrote:
>> Adding relevant mailing lists.
>>
>>
>> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty wrote:
>>> Hi,
>>>
>>> The following commit permanently turns my screen off when x server is
>>> started (i3 330M Ironlake):
>>>
>>>
On Sat, Dec 13, 2014 at 04:14:58PM -0800, Linus Torvalds wrote:
> On Sat, Dec 13, 2014 at 3:47 PM, Al Viro wrote:
> >
> > static inline void mnt_dec_writers(struct mount *mnt)
> > {
> > #ifdef CONFIG_SMP
> > this_cpu_dec(mnt->mnt_pcp->mnt_writers);
> > #else
> >
On Sat, Dec 13, 2014 at 3:47 PM, Al Viro wrote:
>
> static inline void mnt_dec_writers(struct mount *mnt)
> {
> #ifdef CONFIG_SMP
> this_cpu_dec(mnt->mnt_pcp->mnt_writers);
> #else
> mnt->mnt_writers--;
> #endif
> }
> It's load/modify/store, without any kind of atomicity; get
Hi Pavel,
>>> My notes say that Marcel wanted different filenames, but I'd need
>>> advice exactly what filenames. I guess platform data supprort should
>>> be removed altogether, rather than renamed.
>>
>> Yes, the platform support should go away. This should be purely based on DT.
>>
>> Can
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of sundeep subbaraya
> Sent: Friday, December 12, 2014 9:13 PM
>
> Hi Felipe,
>
> In DWC3 driver, for three stage Control OUT transfer there is a check:
>
>else if (!IS_ALIGNED(req->request.length,
Hi!
> > My notes say that Marcel wanted different filenames, but I'd need
> > advice exactly what filenames. I guess platform data supprort should
> > be removed altogether, rather than renamed.
>
> Yes, the platform support should go away. This should be purely based on DT.
>
> Can you also
On Sat, Dec 13, 2014 at 03:38:57PM -0800, Linus Torvalds wrote:
> On Sat, Dec 13, 2014 at 3:35 PM, Al Viro wrote:
> >
> > Er... There's much more direct reason - suppose we get a timer interrupt
> > right in the middle of mnt_drop_write(). And lost the timeslice.
>
> So?
>
> You didn't have
On Sat, Dec 13, 2014 at 3:35 PM, Al Viro wrote:
>
> Er... There's much more direct reason - suppose we get a timer interrupt
> right in the middle of mnt_drop_write(). And lost the timeslice.
So?
You didn't have preemption disabled in *between* the mnt_want_write()
and mnt_drop_write(),
On Sat, Dec 13, 2014 at 02:59:43PM -0800, Linus Torvalds wrote:
> Side note: I think I've found a real potential lockup bug in
> fs/namespace.c, but afaik it could only trigger with the RT patches.
> Except it won't with the RT patches, I guess. So it looks like you could
> have:\
>
> -
On Sat, Dec 13, 2014 at 03:09:59PM -0800, Linus Torvalds wrote:
> On Sat, Dec 13, 2014 at 2:59 PM, Linus Torvalds
> wrote:
> > The generic code does that mnt_want_write/mnt_drop_write
> > dance adound the call to setxattr, and that in turn does
> >
> > while
Hi Pavel,
> Add hci_h4p bluetooth driver to staging tree. This device is used
> for example on Nokia N900 cell phone.
>
> Signed-off-by: Pavel Machek
> Thanks-to: Sebastian Reichel
> Thanks-to: Joe Perches
>
> ---
>
>
> I'd prefer to resurect the driver in staging/ in order not to lose
>
Hi,
On Fri, Dec 12, 2014 at 11:24 PM, Kishon Vijay Abraham I wrote:
> hi,
>
> On Saturday 13 December 2014 05:49 AM, Doug Anderson wrote:
>> Yunzhi,
>>
>> On Fri, Dec 12, 2014 at 7:07 AM, Yunzhi Li wrote:
>>> This patch to add a generic PHY driver for ROCKCHIP usb PHYs,
>>> currently this
On Sat, Dec 13, 2014 at 2:59 PM, Linus Torvalds
wrote:
> The generic code does that mnt_want_write/mnt_drop_write
> dance adound the call to setxattr, and that in turn does
>
> while (ACCESS_ONCE(mnt->mnt.mnt_flags) & MNT_WRITE_HOLD)
> cpu_relax();
>
> with preemption
Currently there is a lock order problem between the console lock and the
kernfs s_active lock of the console driver's bind sysfs entry. When
writing to the sysfs entry the lock order is first s_active then console
lock, when unregistering the console driver via
do_unregister_con_driver() the order
Side note: I think I've found a real potential lockup bug in
fs/namespace.c, but afaik it could only trigger with the RT patches.
I'm looking at what lxsetattr() does, since you had that
lxsetattr-only lockup. I doubt it's really related to lxsetattr(), but
whatever. The generic code does that
For in-kernel use, uX types should be enough, no need to use __uX.
Signed-off-by: Pavel Machek
diff --git a/include/net/bluetooth/bluetooth.h
b/include/net/bluetooth/bluetooth.h
index 58695ff..a0f0154 100644
--- a/include/net/bluetooth/bluetooth.h
+++ b/include/net/bluetooth/bluetooth.h
@@
On Sat, Dec 13, 2014 at 2:36 PM, Dave Jones wrote:
>
> Ok, I think we can rule out preemption. I just checked on it, and
> found it wedged.
Ok, one more. Mind checking what happens without CONFIG_DEBUG_PAGEALLOC?
Linus
--
To unsubscribe from this list: send the line
Add hci_h4p bluetooth driver to staging tree. This device is used
for example on Nokia N900 cell phone.
Signed-off-by: Pavel Machek
Thanks-to: Sebastian Reichel
Thanks-to: Joe Perches
---
I'd prefer to resurect the driver in staging/ in order not to lose
history, but Marcel wanted to treat
On Sat, Dec 13, 2014 at 11:59:15AM -0500, Dave Jones wrote:
> On Fri, Dec 12, 2014 at 11:14:06AM -0800, Linus Torvalds wrote:
> > On Fri, Dec 12, 2014 at 10:54 AM, Dave Jones wrote:
> > >
> > > Something that's still making me wonder if it's some kind of hardware
> > > problem is the
sorry, I've only been back from the road the days... Two tries at compiling
have failed (infrastructure problems, not your set), hoping to fire of another
build tonight.On 12/10/14 16:48 Serge Hallyn wrote:
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> Will people please test these
On Thu, Dec 11, 2014 at 11:13 PM, Simon Horman wrote:
>
> If you give me a specific tag or commit id I can investigate further but
> I'm assuming it is renesas-dt-du-for-v3.19 (0ee56d403549fd97d) then it has
> been accepted by the by Arnd (CCed) and I believe he or one of the other
> Arm SoC
On Sat, Dec 13, 2014 at 5:46 PM, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Dec 12, 2014 at 11:59:20AM +, Grant Likely wrote:
>> [...]
>> > --- a/Documentation/devicetree/bindings/serial/of-serial.txt
>> > +++ b/Documentation/devicetree/bindings/serial/of-serial.txt
>> > @@ -39,6 +39,10 @@
On Tue, Dec 9, 2014 at 11:42 AM, Shuah Khan wrote:
>
> Please pull the following kselftest updates for 3.19-rc1. Details
> in the singed tag:
Gaah. Why do you do this to me?
> g...@gitolite.kernel.org:/pub/scm/linux/kernel/git/shuah/linux-kselftest
> fixes
That's the wrong format, but it's
On Sat, Dec 13, 2014 at 07:07:05PM +, One Thousand Gnomes wrote:
>
> Pointless churn. It makes it less readable if anything, and it removes
> the type safety as you are now checking against 0 not (void *)0
>
> NAK
>
> Alan
The type safety is an interesting point I was not aware of.
Just
Currently there is a lock order problem between the console lock and the
kernfs s_active lock of the console driver's bind sysfs entry. When
writing to the sysfs entry the lock order is first s_active then console
lock, when unregistering the console driver via
do_unregister_con_driver() the order
System console drivers (without the CON_DRIVER_FLAG_MODULE flag) and
busy drivers bound to a console (as reported by con_is_bound())
shouldn't be unregistered. The current code checks for the
CON_DRIVER_FLAG_INIT flag but this doesn't really correspond to either
of the above two conditions.
Hi,
On 12/04/2014 12:25 AM, Andrew Morton wrote:
On Wed, 03 Dec 2014 15:41:21 +0300 Andrey Ryabinin
wrote:
Use the 'unsigned long' type for 'zero' variable to fix this.
Changing type to 'unsigned long' shouldn't affect any other users
of this variable.
Reported-by: Dmitry Vyukov
Fixes:
On Sat, Dec 13, 2014 at 10:04:08AM -0800, Paul E. McKenney wrote:
> On Sat, Dec 13, 2014 at 11:59:15AM -0500, Dave Jones wrote:
> > On Fri, Dec 12, 2014 at 11:14:06AM -0800, Linus Torvalds wrote:
> > > On Fri, Dec 12, 2014 at 10:54 AM, Dave Jones wrote:
> > > >
> > > > Something that's
Hello,
On Thu, 11 Dec 2014, Smart Weblications GmbH - Florian Wiessner wrote:
> >> [ 512.485323] CPU: 4 PID: 28142 Comm: vsftpd Not tainted 3.12.33 #5
> >
> > Above "#5" is same as previous oops. It means kernel
> > is not updated. Or you updated only the IPVS modules after
> >
Hi Linus,
Below is the block driver pull request for 3.19, it sits on top of the
core pull request submitted yesterday. It contains:
- NVMe updates
- The blk-mq conversion from Matias (and others)
- A stack of NVMe bug fixes from the nvme tree, mostly from Keith.
-
On Fri, Dec 12, 2014 at 05:58:19PM +0100, Miroslav Benes wrote:
>
> Hi,
>
> I think we are really close (or I hope so). I found few suspicious things
> or nitpicks though. They might have applied also to v5, but I didn't
> manage to look at that. Sorry about that.
>
> On Wed, 10 Dec 2014,
Hello Hans,
Please find my comments inlined.
On 12/13/14, Hans de Goede wrote:
> Hi VishnuPatekar,
>
> The patch mangling for this set seems to have gone a bit wrong I'm afraid
No, this time I've corrected it. Infact, last version of patch did not
used the status bit error macros.
> a lot of
Hi Jaewon,
On Fri, Dec 12, 2014 at 07:32:28PM +0900, Jaewon Kim wrote:
> This patch adds support for haptic driver controlled by
> voltage of regulator. And this driver support for
> Force Feedback interface from input framework
>
> Signed-off-by: Jaewon Kim
> Signed-off-by: Hyunhee Kim
>
On Saturday 13 December 2014 11:05:52 Arend van Spriel wrote:
>
> Makes sense. I think that is what Hauke meant by "adding
> additional support for registering to bcma". So the discovery info is a
> piece of read-only memory in the chip. Its address is stored in the
> chipcommon core register
Loïc,
On Sat, Dec 13, 2014 at 07:22:38PM +0100, Loic Pefferkorn wrote:
> > Whose convention is this? I can't find any mention in
> > Documention/CodingStyle. checkpatch.pl doesn't complain about them.
> > And there are almost three thousand examples in staging which don't
> > use this
Hi Andy,
On Wed, Dec 10, 2014 at 08:32:56PM +0200, Andy Shevchenko wrote:
> On Sun, 2014-12-07 at 23:21 -0800, Dmitry Torokhov wrote:
> > We do not need to roll our own implementation of delayed work now that we
> > have proper implementation of mod_delayed_work.
> >
> > For interrupt-only
On Sat, 13 Dec 2014 17:29:26 +0100
Loic Pefferkorn wrote:
> Hello,
>
> The convention for checking for NULL pointers is !ptr and not ptr == NULL.
> This patch fixes such occurences in goldfish driver, it applies against
> next-20141212
>
>
> Signed-off-by: Loic Pefferkorn
Pointless churn.
On Tue, Dec 09, 2014 at 10:08:16AM +0200, Asaf Vertz wrote:
> Fixed a coding style error, macros with complex values should be
> enclosed in parentheses.
>
> Signed-off-by: Asaf Vertz
Applied, thank you.
> ---
> Changes in v2:
> - use do {...} while (0) instead of {...}
>
>
> Whose convention is this? I can't find any mention in
> Documention/CodingStyle. checkpatch.pl doesn't complain about them.
> And there are almost three thousand examples in staging which don't
> use this convention.
>
> linux-next$ grep -r "== NULL" drivers/staging/* | wc -l
> 2844
Hi
On 12/13/14 8:26 AM, Arnaldo Carvalho de Melo wrote:
The callchain code was done initially for 'report' and when I made 'top'
reuse the hist_entry code allowing 'top' to collect callchains was too
easy, but then we need to go thru the callchain/hists/hist_entry code to
make sure that they don't
On Sat, Dec 13, 2014 at 10:53:35AM -0500, Sasha Levin wrote:
> On 12/13/2014 03:30 AM, Ingo Molnar wrote:
> >> > This is my no_hz related config:
> >> >
> >> > $ grep NO_HZ .config
> >> > CONFIG_NO_HZ_COMMON=y
> >> > # CONFIG_NO_HZ_IDLE is not set
> >> > CONFIG_NO_HZ_FULL=y
> >> >
On Sat, Dec 13, 2014 at 11:59:15AM -0500, Dave Jones wrote:
> On Fri, Dec 12, 2014 at 11:14:06AM -0800, Linus Torvalds wrote:
> > On Fri, Dec 12, 2014 at 10:54 AM, Dave Jones wrote:
> > >
> > > Something that's still making me wonder if it's some kind of hardware
> > > problem is the
On Fri, Dec 12, 2014 at 1:45 AM, Pankaj Dubey wrote:
> Hi Rob,
>
> On Thursday 11 December 2014 11:00 PM, Rob Herring wrote:
>>
>> On Thu, Dec 11, 2014 at 2:07 AM, Pankaj Dubey
>> wrote:
>>>
>>> Exynos SoCs have Chipid, for identification of product IDs
>>> and SoC revisions. This patch intendes
Loic,
On Sat, Dec 13, 2014 at 05:29:26PM +0100, Loic Pefferkorn wrote:
> Hello,
>
> The convention for checking for NULL pointers is !ptr and not ptr == NULL.
> This patch fixes such occurences in goldfish driver, it applies against
> next-20141212
>
Whose convention is this? I can't find any
On Fri, 12 Dec 2014, Jarkko Sakkinen wrote:
> This patch set enables TPM2 protocol and provides drivers for FIFO and
> CRB interfaces. This patch set does not export any sysfs attributes for
> TPM 2.0 because existing sysfs attributes have three non-trivial issues:
>
> - They are associated
I've just released Linux 2.6.32.65.
This version addresses the following list of security issues :
CVE-2013-2147 (was incorrectly fixed in 2.6.32.61), CVE-2014-3184,
CVE-2014-3185, CVE-2014-3687, CVE-2014-3688, CVE-2014-4653,
CVE-2014-4654, CVE-2014-4655, CVE-2014-4943, CVE-2014-6410,
On Sat, Dec 13, 2014 at 01:52:31PM +, One Thousand Gnomes wrote:
...
> It could then be integrated into git (if only so we can have a "git lost"
> command to block annoying sources)
All sounds nice and good but I'd be fine with people adhering to the
one-week feedback gather rule and not
Hi,
On Fri, Dec 12, 2014 at 11:59:20AM +, Grant Likely wrote:
> [...]
> > --- a/Documentation/devicetree/bindings/serial/of-serial.txt
> > +++ b/Documentation/devicetree/bindings/serial/of-serial.txt
> > @@ -39,6 +39,10 @@ Optional properties:
> >driver is allowed to detect support for
Hi,
On Fri, Dec 12, 2014 at 01:14:53PM +0100, Pavel Machek wrote:
> > > I have created provisional device tree binding, and the driver still
> > > works.
> >
> > I don't have time to look at the code now, but I have some comments
> > regarding the binding.
>
> > >
> > > {
> > > +
On Sat, Dec 13, 2014 at 09:06:45AM -0500, Jeff Layton wrote:
> On Fri, 12 Dec 2014 16:59:52 +
> Al Viro wrote:
>
> > On Fri, Dec 12, 2014 at 06:54:08AM -0500, Jeff Layton wrote:
> >
> > > > Umm... I would be very surprised if it turned out to be a problem.
> > > > nfsd really doesn't give
On Fri, Dec 12, 2014 at 11:14:06AM -0800, Linus Torvalds wrote:
> On Fri, Dec 12, 2014 at 10:54 AM, Dave Jones wrote:
> >
> > Something that's still making me wonder if it's some kind of hardware
> > problem is the non-deterministic nature of this bug.
>
> I'd expect it to be a race
Instead of using bool to restore suspended devices initially, use flags
like GPD_DEV_SUSPEND_INIT, GPD_DEV_RESTORE_INIT and GPD_DEV_RESTORE_FORCE.
The first two flags will be similar to the existing true/false functionality.
The third flag may be used to force restore of suspended devices
whenever
This patch adds PM runtime support for clocks associated with Power
Domain. The PM runtime suspend/resume handlers will be called when the
power domain associated with it, is turned on/off.
The registration of clocks happen in early initailisation. The probe
is later called to register the clock
Although workqueue detects relationship between cpu<->node at boot,
it is finally determined in cpu_up().
This patch tries to update pool->node using online status of cpus.
1. When a node goes down, clear per-cpu pool's node attr.
2. When a cpu comes up, update per-cpu pool's node attr.
3. When a
remove node aware unbound pools if node goes offline.
scan unbound workqueue and remove numa affine pool when
a node goes offline.
Signed-off-by: KAMEZAWA Hiroyuki
---
kernel/workqueue.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/kernel/workqueue.c
Yasuaki Ishimatsu hit a allocation failure bug when the numa mapping
between CPU and node is changed. This was the last scene:
SLUB: Unable to allocate memory on node 2 (gfp=0x80d0)
cache: kmalloc-192, object size: 192, buffer size: 192, default order: 1, min
order: 0
node 0: slabs: 6172,
Add warning if pool->node is offline.
This patch was originaly made for debug.
I think add warning here can show what may happen.
Signed-off-by: KAMEZAWA Hiroyuki
---
kernel/workqueue.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/kernel/workqueue.c
Subject: [PATCH 1/4] add callbackof node hotplug for workqueue.
Because workqueue is numa aware, it pool has node information.
And it should be maintained against node-hotplug.
When a node which exists at boot is unpluged, following error
is detected.
==
SLUB: Unable to allocate memory on node 2
I started seeing this behavior somewhere around 3.16 with
CONFIG_PREEMPT set. Setting CONFIG_PREEMPT off seems to help. And,
yes, it happens on high load (compiling mozilla, xul) and using qemu
chroot to compile mesa.
I'm seeing a few persons bisecting already. If you want, I could start
Hello,
The convention for checking for NULL pointers is !ptr and not ptr == NULL.
This patch fixes such occurences in goldfish driver, it applies against
next-20141212
Signed-off-by: Loic Pefferkorn
---
drivers/staging/goldfish/goldfish_audio.c | 8
The shunt resistance can only be set via platform_data or device tree. This
isn't suitable for devices in which the shunt resistance can change/isn't
known at boot-time.
Add a sysfs attribute that allows to read and set the shunt resistance.
Signed-off-by: Bartosz Golaszewski
---
Shunt resistance values greater than the chip's calibration factor make no
sense since the actual value written to the register equals:
/
Bail-out from ina2xx_probe() if the configured value is greater than the
calibration factor.
Signed-off-by: Bartosz Golaszewski
---
This series implements a mechanism to detect if the chip is in its POR state
and reinitialize it if needed. It also extends the sysfs interface to make the
driver configurable at run-time.
The shunt_resistor attribute allows to change the shunt resistance value
at run-time in cases where ina2xx
Chips from the ina family don't like to be uninitialized. In case the power
is cut-off and restored again the calibration register will be reset
to 0 and both the power and current registers will remain at 0.
Check the calibration register in ina2xx_update_device() and reinitialize
the chip if
The averaging rate of ina226 is hardcoded to 16 in the driver. Make it
modifiable at run-time via a new sysfs attribute.
While we're at it - add an additional variable to ina2xx_data, which holds
the current configuration settings - this way we'll be able to restore the
configuration in case of
Signed-off-by: Bartosz Golaszewski
---
drivers/hwmon/ina2xx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c
index ffbd60f..39e017b 100644
--- a/drivers/hwmon/ina2xx.c
+++ b/drivers/hwmon/ina2xx.c
@@ -52,7 +52,6 @@
#define INA226_ALERT_LIMIT
On 12/13/2014 03:30 AM, Ingo Molnar wrote:
>> > This is my no_hz related config:
>> >
>> > $ grep NO_HZ .config
>> > CONFIG_NO_HZ_COMMON=y
>> > # CONFIG_NO_HZ_IDLE is not set
>> > CONFIG_NO_HZ_FULL=y
>> > CONFIG_NO_HZ_FULL_ALL=y
> Just curious, if you disable NO_HZ_FULL_ALL, does the bug change?
On 12/12/2014 05:45 PM, Andy Lutomirski wrote:
> I was thinking of this:
>
> + if (is_64bit_mm(mm)) {
> + vaddr_space_size = 1ULL << __VIRTUAL_MASK_SHIFT;
> + bd_entry_virt_space = vaddr_space_size / MPX_BD_NR_ENTRIES_64;
> + /*
> + * __VIRTUAL_MASK takes the 64-bit addressing hole
> + * in
On 12/12/2014 06:50 AM, Matthias Brugger wrote:
Signed-off-by: Matthias Brugger
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 13 +
1 file changed, 13 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
diff --git
On 12/12/2014 06:50 AM, Matthias Brugger wrote:
This patch adds a driver for the Mediatek SoC integrated
watchdog. This driver supports watchdog and software reset
for mt65xx and mt81xx SoCs.
Signed-off-by: Matthias Brugger
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile
Em Sat, Dec 13, 2014 at 10:03:31AM +0100, Markus Trippelsdorf escreveu:
> On 2014.12.13 at 09:48 +0100, Markus Trippelsdorf wrote:
> > Running "perf top -g" built from current Linus tree apparently leaks
> > ~300MB of memory every second an my machine.
>
> Hmm, this is a much older problem. I
Hi, all,
Regarding preferring using netlink sockets versus ethtool IOCTLs for setting
kernel network attributes from userspace, I fully agree with Marco. The netlink
API is much more structured and
much more geared towards this type of operation, than the IOCTL-based ethtool.
Regards,
Rami
Silvio, Marc,
On Sat, Dec 13, 2014 at 09:21:23AM +, Marc Zyngier wrote:
> On Sat, Dec 13 2014 at 1:46:45 am GMT, Silvio Fricke
> wrote:
>
> Hi Silvio,
>
> > I have found some dts entries which are not evaluated by the drivers. This
> > patch remove this entries from the dts files.
> >
On Fri, 12 Dec 2014 08:02:48 -0500
> Which brings up another point: why not do this in the runtime power
> management;
> ie, turn on the slave device when the master device is turned on? Sebastian
> recently made the 8250 driver power-managed per access, which would enable
> significant power
On 12/13/2014 03:27 AM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>>
>> * Linus Torvalds wrote:
>>
>>> On Fri, Dec 12, 2014 at 10:54 AM, Dave Jones wrote:
>>>
Something that's still making me wonder if it's some kind of
hardware problem is the non-deterministic nature of
> 2) why is this tied to the tty core and not the serial core
>if this is only for UART?
I'm a bit baffled why you would try and tie it to serial core given that
serial core only covers a random subset of the uart drivers we have. If
we have a USB connected device with USB gpio lines doing
1 - 100 of 276 matches
Mail list logo
