On Tue, Aug 6, 2013 at 7:19 AM, Steven Rostedt wrote:
>
> After playing with the patches again, I now understand why I did that.
> It wasn't just for optimization.
[explanation snipped]
> Anyway, if you feel that update_jump_label is too complex, I can go the
> "update at early boot" route and s
[+cc Myron, Adam]
On Fri, Aug 2, 2013 at 10:24 AM, Chris Metcalf wrote:
> The LSI MEGARAID SAS HBA suffers from the problem where it can do
> 64-bit DMA to streaming buffers but not to consistent buffers.
> In other words, 64-bit DMA is used for disk data transfers and 32-bit
> DMA must be used f
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but I think it
would be more clean to avoid the s
On 08/06/2013 12:28 AM, Greg Kroah-Hartman wrote:
> On Mon, Aug 05, 2013 at 08:36:39PM +0200, Yacine Belkadi wrote:
>> On 08/04/2013 11:29 PM, Greg Kroah-Hartman wrote:
>>> On Sun, Aug 04, 2013 at 10:05:36PM +0200, Yacine Belkadi wrote:
On 08/03/2013 05:29 AM, Greg Kroah-Hartman wrote:
> O
On Tue, Jul 23, 2013 at 12:16:02PM +0200, Philipp Zabel wrote:
> I see no reason why a virtual range shouldn't be allowed to cover its
> own data window if the page selection register is in the same place
> on every page.
So, this feature is clearly sensible and in fact the thing that was
concerni
On Tue, 2013-08-06 at 09:46 +0800, Chen Gang wrote:
> "include/uapi/" is the whole Linux kernel API, it is important enough
> to get more global explanations by comments.
It'd probably be useful to have more descriptions
of uapi in the Documentation directory too.
--
To unsubscribe from this lis
On 06/16/2013 04:31 AM, Ralf Baechle wrote:
Patch looks ok but why not combine this patch with the previous one?
Because even though they both touch asm-offsets.c, they are offsets for
unrelated structures. I could try distributing these changes across
several other patches, but getting the
From: Lukasz Majewski
Policies available in a cpufreq framework are now linked together. They are
accessible via cpufreq_policy_list defined at cpufreq core.
Signed-off-by: Lukasz Majewski
Signed-off-by: Myungjoo Ham
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 11 +++
We don't need to set .owner = THIS_MODULE anymore in our code as this field
isn't used anymore by cpufreq core.
This patch removes it and fixes all dependent drivers.
Signed-off-by: Viresh Kumar
---
Documentation/cpu-freq/cpu-drivers.txt | 2 --
drivers/cpufreq/acpi-cpufreq.c | 1 -
dri
Caller of cpufreq_add_policy_cpu() already has pointer to policy structure and
so there is no need to find it again in cpufreq_add_policy_cpu(). Lets pass it
directly.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 18 ++
1 file changed, 6 insertions(+), 12 deletions
Governor's owner refcount usage was broken. We should increment refcount only
when CPUFREQ_GOV_POLICY_INIT event has come and should decrement only if
CPUFREQ_GOV_POLICY_EXIT has come.
Currently there can be situations where governor is in use but we have allowed
it to be unloaded which may result
Chapter 14 of Documentation/CodingStyle says:
The preferred form for passing a size of a struct is the following:
p = kmalloc(sizeof(*p), ...);
The alternative form where struct name is spelled out hurts readability and
introduces an opportunity for a bug when the pointer variable type i
We are protecting critical sections of cpufreq core with the help of owner's
refcount, which isn't the correct approach. As rmmod returns error when some
routine has updated the module's refcount.
Lets use rwsem for this.. Only cpufreq_unregister_driver() will use write sem
and everybody else will
For iterating over all policies currently we are iterating over all CPUs and
then finding their policies. Lets use the newly created infrastructure
cpufreq_policy_list.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
dif
__cpufreq_governor() function can fail in rare cases specially if there are bugs
in cpufreq driver. And so we must stop processing as soon as this routine fails,
otherwise it may result in undefined behavior.
And so this patch adds error checking code whenever this routine is called from
any place
They are pretty much mixed up. Although generic headers are present but
definitions/declarations are present outside them too..
This patch just moves stuff up and down to make it look better and consistent.
Signed-off-by: Viresh Kumar
---
include/linux/cpufreq.h | 373 +++---
They are named as policy, cur_policy, new_policy, data, etc.. Just name them
poicy wherever possible.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 200 ++---
drivers/cpufreq/cpufreq_governor.h | 2 +-
drivers/cpufreq/cpufreq_ondemand.c |
This patch intends to cleanup following issues in the header files included in
cpufreq core layers:
- Include headers in ascending order, so that we don't add same multiple times
by mistake.
- must be included after , so that they override whatever they
need.
- Remove unnecessary header files
Hi Rafael,
This is V2 of the patch series which was posted here earlier:
http://www.gossamer-threads.com/lists/linux/kernel/1759514
This patchset tries to fix & cleanup many existing cpufreq core issues. First
four patches tries to cleanup basic problems in cpufreq core. Its first patch
was earl
Reduces overhead a bit and frees up a couple of registers.
Signed-off-by: Christoph Lameter
Index: linux/arch/x86/include/asm/debugreg.h
===
--- linux.orig/arch/x86/include/asm/debugreg.h 2013-07-30 14:00:30.0
-0500
+++ li
On Tue, Jul 30, 2013 at 12:32:03PM +0200, Richard Genoud wrote:
> From: Nicolas Ferre
>
> Description of the Asoc machine driver for an at91sam9x5 based board
> with a wm8731 audio DAC. Wm8731 is clocked by a crystal and used as a
> master on the SSC/I2S interface. Its connections are a headphone
sl811h_suspend() seems to be the odd routine in the way it handles the
PM_EVENT_PRETHAW state. It treats it same as PM_EVENT_SUSPEND and
PM_EVENT_HIBERNATE. All other uses I could find treat it same as
PM_EVENT_FREEZE and PM_EVENT_QUIESCE. Makes sense since PM_EVENT_PRETHAW
is PM_EVENT_QUIESCE.
On Tue, Jul 30, 2013 at 12:32:04PM +0200, Richard Genoud wrote:
> As atmel-ssc can be used with DMA, the documentation should be updated.
> Also, a configuration DMA example is given.
Applied, thanks.
signature.asc
Description: Digital signature
From: Stephen Warren
pinctrl bindings can benefit from generic property names that define
which pins a "pin configuration node" affects, and which mux function
to select onto those pins. Document new properties for this purpose so
that other bindings may refer to them.
Signed-off-by: Stephen War
From: Stephen Warren
Reword the section of pinctrl-bindings.txt that describes generic
properties that pinctrl bindings may use. The aim is to make the text
clearer, and more explicitly call out the responsibility of individual
bindings that use the generic properties to define which of the
prope
From: "Yann E. MORIN"
When a symbol changes type from tristate to bool, and was previously set to
'm', a subsequent silentoldconfig would warn about inconsistency, such as:
include/config/auto.conf:3014:warning: symbol value 'm' invalid for
HOTPLUG_PCI_PCIE
Seen by Linus with the merge
On Mon, Jul 29, 2013 at 02:31:49PM +0200, Sebastian Hesselbarth wrote:
> This patch set converts DT based Dove boards to DT probed MBus to be
> introduced with v3.12.
>
> The first two patches prepare Dove DT nodes for MBus ID remapping by using
> preprocessor includes and adding the MBUS_ID macro
The LSI MEGARAID SAS HBA suffers from the problem where it can do
64-bit DMA to streaming buffers but not to consistent buffers.
In other words, 64-bit DMA is used for disk data transfers and 32-bit
DMA must be used for control message transfers. According to LSI,
the firmware is not fully function
On 08/06/2013 02:41 AM, Mark Rutland wrote:
> On Mon, Aug 05, 2013 at 10:56:00PM +0100, Stephen Warren wrote:
>> From: Stephen Warren
>>
>> pinctrl bindings can benefit from generic property names that define
>> which pins a "pin configuration node" affects, and which mux function
>> to select ont
On 8/5/2013 4:52 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Aug 05, 2013 at 04:06:20PM -0400, Chris Metcalf wrote:
>> The LSI MEGARAID SAS HBA suffers from the problem where it can do
>> 64-bit DMA to streaming buffers but not to consistent buffers.
>> In other words, 64-bit DMA is used for disk da
On 08/05/2013 11:42 PM, Krzysztof Kozlowski wrote:
> +#ifdef CONFIG_ZBUD
> + /* Allocated by zbud. Flag is necessary to find zbud pages to unuse
> + * during migration/compaction.
> + */
> + PG_zbud,
> +#endif
Do you _really_ need an absolutely new, unshared page flag?
The zbud c
On Tue, 2013-08-06 at 19:11 +0900, Yasuaki Ishimatsu wrote:
> try_offline_node() checks that all cpus related with removed node have been
> removed by using cpu_present_bits. If all cpus related with removed node have
> been removed, try_offline_node() clears the node information.
>
> But try_offl
On Tue, Aug 06, 2013 at 03:30:48PM +0100, Steve Twiss wrote:
> From: Steve Twiss
>
> I2C driver for the Dialog DA9210 Multi-phase 12A DC-DC Buck.
Applied, thanks. I made some trivial edits to sort Kconfig and to
remove a blank line at the start of the source file.
signature.asc
Description: D
Aha, yes...my misunderstanding.
This node is not only for OTG or HSIC, could miss USB HOST transceiver
if certain board file does not set "okay".
Thanks,
Dongjin.
On Tue, Aug 6, 2013 at 3:09 PM, Sachin Kamat wrote:
> Hi Dongjin,
>
> On 5 August 2013 23:48, Dongjin Kim wrote:
>> This patch adds
On Tue, Aug 06, 2013 at 03:30:51PM +, Steve Twiss wrote:
> I thought that my previous submission attempts were drawing comments
> because of the body content of the e-mail was wrong and the details should
> have
> been placed after the --- marker, not because of the subject line.
Actually it
On Tue, Aug 06, 2013 at 11:17:17AM +0200, Tom Gundersen wrote:
> On Tue, Aug 6, 2013 at 11:11 AM, Tom Gundersen wrote:
> > On Tue, Aug 6, 2013 at 10:20 AM, Maarten Lankhorst
> > wrote:
> >> Op 05-08-13 18:29, Andy Lutomirski schreef:
> >>> The systemd commit below can delay firmware loading by mu
On Mon, Aug 05, 2013 at 01:17:39PM +0200, Jan Kara wrote:
> On Sun 04-08-13 05:17:03, Kirill A. Shutemov wrote:
> > From: "Kirill A. Shutemov"
> > The radix tree is variable-height, so an insert operation not only has
> > to build the branch to its corresponding item, it also has to build the
> >
regmap.h requires linux/err.h if CONFIG_REGMAP is not defined. Without it I get
error.
CC drivers/media/platform/exynos4-is/fimc-reg.o
In file included from drivers/media/platform/exynos4-is/fimc-reg.c:14:0:
include/linux/regmap.h: In function ‘regmap_write’:
include/linux/regmap.h:525:10: err
On 08/06/2013 09:26 AM, Steven Rostedt wrote:
>>
>> No, but if we ever end up doing MPX in the kernel, for example, we would
>> have to put an MPX prefix on the jmp.
>
> Well then we just have to update the rest of the jump label code :-)
>
For MPX in the kernel, this would be a small part of th
On Tue, 2013-08-06 at 09:19 -0700, H. Peter Anvin wrote:
> On 08/06/2013 09:15 AM, Steven Rostedt wrote:
> > On Mon, 2013-08-05 at 14:43 -0700, H. Peter Anvin wrote:
> >
> >> For unconditional jmp that should be pretty safe barring any fundamental
> >> changes to the instruction set, in which case
On Tue, Aug 6, 2013 at 3:19 AM, HATAYAMA Daisuke
wrote:
> So, could anyone help testing the idea 2) above if you have which of
> the following machines? (or other ones that can lead to the same bug)
>
> - HP Compaq 6910p
> - HP Compaq 6710b
> - HP Compaq 6710s
> - HP Compaq 6510b
> - HP Compaq 251
From: Sebastian Hesselbarth [mailto:sebastian.hesselba...@gmail.com]
> Subject: [PATCH 0/8] Several NXP TDA998x patches
>
> This patch set picks up several patches sent during the past months related
> with NXP TDA998x HDMI transmitter driver. The patches have been tested
> on Marvell Dove (Armada
On Fri, Aug 2, 2013 at 5:40 PM, Maxim Patlasov wrote:
> 07/19/2013 08:50 PM, Miklos Szeredi пишет:
>
>> On Sat, Jun 29, 2013 at 09:45:29PM +0400, Maxim Patlasov wrote:
>>>
>>> From: Pavel Emelyanov
>>>
>>> The .writepages one is required to make each writeback request carry more
>>> than
>>> one
On Tue, Aug 06, 2013 at 06:09:09PM +0200, Daniel Lezcano wrote:
> On 08/06/2013 03:18 PM, Michal Simek wrote:
>
> [ ... ]
>
> > Soren: Are you able to replicate this issue on QEMU?
> > If yes, it should be the best if you can provide Qemu, kernel .config/
> > rootfs and simple manual
On Wed, Jul 24, 2013 at 09:25:19AM -0600, Alex Williamson wrote:
>
> This is a pretty massive memory leak, anyone @Intel care? Thanks,
>
> Alex
>
> On Sat, 2013-06-15 at 10:27 -0600, Alex Williamson wrote:
> > At best the current code only seems to free the leaf pagetables and
> > the root. If
On 08/06/2013 09:15 AM, Steven Rostedt wrote:
> On Mon, 2013-08-05 at 14:43 -0700, H. Peter Anvin wrote:
>
>> For unconditional jmp that should be pretty safe barring any fundamental
>> changes to the instruction set, in which case we can enable it as
>> needed, but for extra robustness it probabl
On Tue, Aug 06, 2013 at 10:46:54AM +0200, Daniel Lezcano wrote:
> On 08/06/2013 03:28 AM, Sören Brinkmann wrote:
> > Hi Daniel,
> >
> > On Thu, Aug 01, 2013 at 07:48:04PM +0200, Daniel Lezcano wrote:
> >> On 08/01/2013 07:43 PM, Sören Brinkmann wrote:
> >>> On Thu, Aug 01, 2013 at 07:29:12PM +0200
perf_trace_buf_prepare() + perf_trace_buf_submit(task => NULL)
make no sense if hlist_empty(head). Change perf_trace_##call()
to check ->perf_events beforehand and do nothing if it is empty.
This removes the overhead for tasks without events associated
with them. For example, "perf record -e sched
Hello, Michal.
On Tue, Aug 06, 2013 at 05:58:04PM +0200, Michal Hocko wrote:
> I am objecting to moving the generic part of that code into memcg. The
> memcg part and the additional complexity (all the parsing and conditions
> for signalling) is already in the memcg code.
But how is it generic if
The next patch tries to avoid the costly perf_trace_buf_* calls
when possible but there is a problem. We can only do this if
__task == NULL, perf_tp_event(task != NULL) has the additional
code for this case.
Unfortunately, TP_perf_assign/__perf_xxx which changes the default
values of __count/__tas
On Mon, 2013-08-05 at 14:43 -0700, H. Peter Anvin wrote:
> For unconditional jmp that should be pretty safe barring any fundamental
> changes to the instruction set, in which case we can enable it as
> needed, but for extra robustness it probably should skip prefix bytes.
Would the assembler add
To simplify the review of the next patches:
1. We are going to reimplent __perf_task/counter and embedd them
into TP_ARGS(). expand TRACE_EVENT(sched_stat_runtime) into
DECLARE_EVENT_CLASS() + DEFINE_EVENT(), this way they can use
different TP_ARGS's.
2. Change perf_trace_##call() macro
On 08/05, Steven Rostedt wrote:
>
> > Sorry... should I resend once again ?
>
> Sure, why not. It's only 3 patches :-)
OK. Added "v2" to avoid the confusion.
The only change is
- Reviewed-and-Acked-by: Steven Rostedt
+ Reviewed-by: Steven Rostedt
+ Acked-by: Steven Rost
On Tue, Aug 06, 2013 at 06:09:09PM +0200, Daniel Lezcano wrote:
> On 08/06/2013 03:18 PM, Michal Simek wrote:
>
> [ ... ]
>
> > Soren: Are you able to replicate this issue on QEMU?
> > If yes, it should be the best if you can provide Qemu, kernel .config/
> > rootfs and simple manual
On 08/06/2013 03:18 PM, Michal Simek wrote:
[ ... ]
> Soren: Are you able to replicate this issue on QEMU?
> If yes, it should be the best if you can provide Qemu, kernel .config/
> rootfs and simple manual to Daniel how to reach that fault.
I tried to download qemu for zynq
On Tue, Aug 6, 2013 at 2:17 AM, Tom Gundersen wrote:
> On Tue, Aug 6, 2013 at 11:11 AM, Tom Gundersen wrote:
>> On Tue, Aug 6, 2013 at 10:20 AM, Maarten Lankhorst
>> wrote:
>>> Op 05-08-13 18:29, Andy Lutomirski schreef:
The systemd commit below can delay firmware loading by multiple
m
Hi Marek,
On Tue, Aug 6, 2013 at 6:17 AM, Marek Szyprowski
wrote:
...
> IMHO it is much better to have a simple driver, which binds to a single
> IOMMU controller and leave it to the driver whether to have a same virtual
> address
> space for all parts of FIMC-IS or MFC submodules/memory ports o
On Tue, Aug 06, 2013 at 04:30:01PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi
>
> We check submounts before doing d_drop() on a non-empty directory dentry in
> NFS (have_submounts()). But we do not exclude a racing mount. Nor do we
> prevent mounts to be added to the disconnected subtr
On 08/06/2013 11:08 AM, Alex Thorlton wrote:
Thanks, Andrew. I'm doing some more testing and looking into using a
different method for controlling this. At this point, I think it's fair
to say that we don't want to control this using the method that I've
proposed here, no matter how we look at
On Tue, Aug 6, 2013 at 7:39 PM, Tejun Heo wrote:
> Hello, Balbir.
>
> On Tue, Aug 06, 2013 at 08:56:34AM +0530, Balbir Singh wrote:
>> [off-topic] Has the unified hierarchy been agreed upon? I did not
>> follow that thread
>
> I consider it agreed upon enough. There of course are objections but
>
This patch adds common __clk_get(), __clk_put() clkdev helpers
which replace their platform specific counterparts when the
common clock API enabled.
An owner module pointer is added to struct clk so a reference
to the clock supplier module is taken when the clock has active
consumers.
Signed-off-
On Tue, Aug 6, 2013 at 5:43 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:29 PM, Johannes Berg
> wrote:
>> On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
>>> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
>>> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
>>> > wrote:
>>> >>
>
On Mon 05-08-13 15:44:31, Tejun Heo wrote:
> Hey, Michal.
>
> On Mon, Aug 05, 2013 at 09:16:41PM +0200, Michal Hocko wrote:
[...]
> > Besides that, is fsnotify really an interface to be used under memory
> > pressure? I might be wrong but from a quick look fsnotify depends on
> > GFP_KERNEL alloca
clk_unregister() is currently not implemented and it is required when
a clock provider module needs to be unloaded.
Normally the clock supplier module is prevented to be unloaded by
taking reference on the module in clk_get().
For cases when the clock supplier module deinitializes despite the
con
Hello,
This short patch set aims to fix issues in the common clock framework WRT
support of the clock suppliers as loadable modules. The thread [1] might
be a good summary and pre-requisiste reading on what this patch series is
trying to achieve.
The first patch adds common implementation of the
Felipe, thanks a lot. Yes fab840f is wrong, this "bug" is already
used as a feature.
Grazvydas, I cc'ed you because I do not really understand
set_thread_context(). It does a couple of extra PTRACE_POKEUSER's
with the "Linux 2.6.33+ needs ..." comment. It would be nice if you
can check if 3.11 sti
This reverts commit fab840fc2d542fabcab903db8e03589a6702ba5f.
This commit even has the test-case to prove that the tracee
can be killed by SIGTRAP if the debugger does not remove the
breakpoints before PTRACE_DETACH.
However, this is exactly what wineserver deliberately does,
set_thread_context()
Hi,
On Friday, July 19, 2013 06:45:31 PM Andreas Mohr wrote:
> Hi,
>
> On Fri, Jul 19, 2013 at 04:30:22PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Friday, July 19, 2013 02:26:53 PM Andreas Mohr wrote:
> > > - do a cable correction patch for libata side (I do think that indicating
> > > 4
On Aug 5, 2013, at 6:02 PM, Rohit Vaswani wrote:
> This patch adds basic board support for MSM8974 Dragonboard
> which belongs to the Snapdragon 800 family.
> For now, just support a basic machine with device tree.
I think the board is APQ8074 and not MSM8974.
>
> Signed-off-by: Rohit Vaswani
Hello,
My name is Jerry Palmer and I am sending this email to your
company regarding to purchase some Water Extractors from your
company, I would like you to email me with types and their price
ranges of of it so that i can determine which i was to purchase and
the quantity also and i h
On Tue, Aug 6, 2013 at 5:29 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
>> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
>> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
>> > wrote:
>> >>
>> >>
>> >>> I have sent you a v2 of my logs (with -d and rsysl
On Tue 06 August 2013 15:31 Steve Twiss wrote:
>Subject: [PATCH V4] DA9210 new driver files
...
It has already been pointed out that I have put the wrong subject line into
this patch.
I thought that my previous submission attempts were drawing comments
because of the body content of the e-mail wa
On 08/06/13 16:10, Borislav Petkov wrote:
> On Tue, Aug 06, 2013 at 12:08:08AM +0200, Borislav Petkov wrote:
>> Ok, thanks again for finding it, I'll go and try to figure out the whole
>> mess tomorrow.
>
> Ok, some more observations:
>
> Decompressing Linux... Parsing ELF... done.
> Booting the
On Tue, 2013-08-06 at 02:15 +0200, Rafael J. Wysocki wrote:
> On Monday, August 05, 2013 05:19:56 PM Toshi Kani wrote:
> > On Mon, 2013-08-05 at 15:14 +0200, Rafael J. Wysocki wrote:
> > :
> > > Can you please test the appended patch? I tested it somewhat, but since
> > > the
> > > greatest num
On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
> > wrote:
> >>
> >>
> >>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
> >>
> >> Hmm, that looks different? There no longer
On Tue, Aug 6, 2013 at 2:18 PM, Lucas Stach wrote:
> I strongly disagree with exposing low-level hardware details like tiling
> to userspace. If we have to do the negotiation of those things in
> userspace we will end up with having to pipe those information through
> things like the wayland proto
On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
> wrote:
>>
>>
>>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
>>
>> Hmm, that looks different? There no longer is anything about "PSK might
>> be wrong", but now just disconnections
Commit-ID: 3e21bb092d07e6d394e6d754057d4ff2d363d318
Gitweb: http://git.kernel.org/tip/3e21bb092d07e6d394e6d754057d4ff2d363d318
Author: Masami Hiramatsu
AuthorDate: Tue, 6 Aug 2013 16:37:50 +0900
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 08:08:47 -0700
x86, insn: Add new opc
On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg wrote:
>
>
>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
>
> Hmm, that looks different? There no longer is anything about "PSK might
> be wrong", but now just disconnections by the AP, which unfortunately
> indicate no reason.
>
> When
> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
Hmm, that looks different? There no longer is anything about "PSK might
be wrong", but now just disconnections by the AP, which unfortunately
indicate no reason.
When was it working last?
johannes
--
To unsubscribe from this list: s
On Tue, 2013-08-06 at 14:46 +0100, Ivan T. Ivanov wrote:
> > > + reg = <0xf920 0xcd00>;
> > > + interrupts = <0 131 0>;
> > > + interrupt-names = "irq";
> > > + usb-phy = <&dwc3_usb2>, <&dwc3_usb3>;
> > > + tx-fifo-
On 08/06/2013 12:37 AM, Masami Hiramatsu wrote:
> Add TSX-NI related instructions and new instructions to
> x86-opcode-map.txt according to the Intel(R) 64 and IA-32
> Architectures Software Developer's Manual Vol2C (June, 2013).
> This also includes below updates.
> - Fix a typo of MWAIT (the lac
On Tue, Aug 06, 2013 at 10:29:16AM +0800, Tang Chen wrote:
> I'm sorry but seeing from lkml, it is OK. And the patch was formatted
> by git and sent by git send-email.
>
> https://lkml.org/lkml/2013/8/2/135
Yeah, I checked that too but I think lkml.org is doing the QP
decoding. The raw link fr
> What everyone else said, plus...
>
> I worry about the inherit-across-fork thing. A scenario we should
> think about is where the user doesn't build his own executables. So he
> writes a little wrapper which runs prctl(PR_SET_THP_DISABLED, 0) then
> execs the third-party-app. But what happens
On Tue, Aug 6, 2013 at 4:59 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 4:57 PM, Johannes Berg
> wrote:
>> On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote:
>>> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg
>>> wrote:
>>> > On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
>>> >
>>
On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg
> wrote:
> > On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
> >
> > Heh, the interesting messages are always cut out of the log:
> >
> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0:
On Tue, Aug 06, 2013 at 08:31:01PM +0800, Peng Tao wrote:
> From: Peng Tao
>
> We also missed ki_nbytes...
Applied to the aio-next.git tree.
-ben
> Cc: Kent Overstreet
> Cc: Andreas Dilger
> Cc: Greg Kroah-Hartman
> Signed-off-by: Peng Tao
> ---
> This fixes Lustre build in
On Tue, Aug 6, 2013 at 10:36 AM, Lucas Stach wrote:
> Am Dienstag, den 06.08.2013, 10:14 -0400 schrieb Rob Clark:
>> On Tue, Aug 6, 2013 at 8:18 AM, Lucas Stach wrote:
>> > Am Dienstag, den 06.08.2013, 12:31 +0100 schrieb Tom Cooksey:
>> >> Hi Rob,
>> >>
>> >> +lkml
>> >>
>> >> > >> On Fri, Jul 2
On Tue, Aug 6, 2013 at 4:57 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote:
>> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg
>> wrote:
>> > On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
>> >
>> > Heh, the interesting messages are always cut out of the log
On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
>
> Heh, the interesting messages are always cut out of the log:
>
> Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0: WPA: RX message 1 of
> 4-Way Handshake from 00:04:0e:e4:00:3d (ver=
On 13-08-05 11:54 PM, Peter Chang wrote:
2013/8/5 Roland Dreier :
From: Roland Dreier
There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances
leads to one process writing data into the address space of some other
random unrelated process if the ioctl is interrupted by a signal.
On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
Heh, the interesting messages are always cut out of the log:
Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0: WPA: RX message 1 of 4-Way
Handshake from 00:04:0e:e4:00:3d (ver=2)
Aug 6 16:30:34 fambox wpa_supplicant[2533]: RSN: msg 1/4 key
On Tue, Aug 6, 2013 at 3:54 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 15:51 +0200, Sedat Dilek wrote:
>> OK, I did not try with debugging enabled and/or w/o Network-Manager.
>>
>> If you know of an issue, please let me know.
>
> No, but the dmesg looks like security problems - check wpa_sup
Hi,
On Tue, 2013-08-06 at 15:07 +0100, Mark Rutland wrote:
> On Tue, Aug 06, 2013 at 12:53:11PM +0100, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
>
> What does the "glue layer" do? Is it an actual piece of hardware, or
> just some platform-specific code?
>
It is hardware layer around S
On Mon, Aug 05, 2013 at 09:27:12PM +0300, Aaro Koskinen wrote:
> Commit 42913c799 (MIPS: Loongson2: Use clk API instead of direct
> dereferences) broke the cpufreq functionality on Loongson2 boards:
> clk_set_rate() is called before the CPU frequency table is initialized,
> and therefore will alwa
On Tue, Aug 6, 2013 at 10:03 AM, Tom Cooksey wrote:
> Hi Rob,
>
>> >> > We may also then have additional constraints when sharing buffers
>> >> > between the display HW and video decode or even camera ISP HW.
>> >> > Programmatically describing buffer allocation constraints is very
>> >> > difficu
Am Dienstag, den 06.08.2013, 10:14 -0400 schrieb Rob Clark:
> On Tue, Aug 6, 2013 at 8:18 AM, Lucas Stach wrote:
> > Am Dienstag, den 06.08.2013, 12:31 +0100 schrieb Tom Cooksey:
> >> Hi Rob,
> >>
> >> +lkml
> >>
> >> > >> On Fri, Jul 26, 2013 at 11:58 AM, Tom Cooksey
> >> > >> wrote:
> >> > >> >
From: Steve Twiss
I2C driver for the Dialog DA9210 Multi-phase 12A DC-DC Buck.
Signed-off-by: Steve Twiss
Signed-off-by: David Dajun Chen
---
Checks performed with next-20130806/scripts/checkpatch.pl
Kconfig total: 0 errors, 36 warnings, 565 lines checked
da9210
Hi,
On Tue, 2013-08-06 at 15:03 +0100, Mark Rutland wrote:
> On Tue, Aug 06, 2013 at 12:53:10PM +0100, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > Signed-off-by: Ivan T. Ivanov
> > ---
> > .../devicetree/bindings/usb/msm-ssusb.txt | 49 +++
> > drivers/usb/phy/Kconfig
From: Miklos Szeredi
We check submounts before doing d_drop() on a non-empty directory dentry in
NFS (have_submounts()). But we do not exclude a racing mount. Nor do we
prevent mounts to be added to the disconnected subtree using relative paths
after the d_drop().
This patch fixes these issues
301 - 400 of 614 matches
Mail list logo