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
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:
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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,
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
> > >
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
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
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
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
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
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
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
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:
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 = <_usb2>, <_usb3>;
> > > + tx-fifo-resize;
>
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
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
> 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
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]:
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
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
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
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
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
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
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
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
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
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
>> >> >
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
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.
Process A: have_submounts() -> returns false
Process B: mount() -> success
Process A: d_drop()
This patch prepares the ground for
From: Miklos Szeredi
Use d_materialise_unique() instead of d_splice_alias(). This allows dentry
subtrees to be moved to a new place if there moved, even if something is
referencing a dentry in the subtree (open fd, cwd, etc..).
This will also allow us to drop a subtree if it is found to be
From: Anand Avati
Drop a subtree when we find that it has moved or been delated. This can be
done as long as there are no submounts under this location.
If the directory was moved and we come across the same directory in a
future lookup it will be reconnected by d_materialise_unique().
Here's a series for fixing issues with d_drop on a directory dentry with
children and adding support for such dropped directories in fuse.
I tested the fuse part, but not the other filesystems (AFS, GFS2, NFS, SYSFS).
The changes to filesystems are pretty trivial, though.
Thanks,
Miklos
---
Laxman,
On Tue, Aug 06, 2013 at 07:42:49PM +0530, Laxman Dewangan wrote:
> Many of Key device tree bindings uses the constant number as key code
> which matches with kernel header key code and then comment as follows
> for reference/better readability:
> linux,code = <102>; /* KEY_HOME */
>
On Mon, 2013-08-05 at 11:49 -0700, Linus Torvalds wrote:
> Ugh. Why the crazy update_jump_label script stuff?
After playing with the patches again, I now understand why I did that.
It wasn't just for optimization.
Currently the way jump labels work is that we use asm goto() and place a
5 byte
On Tuesday, August 06, 2013 07:06:37 PM Yasuaki Ishimatsu wrote:
> (2013/08/06 12:07), Yasuaki Ishimatsu wrote:
> >
> > I acked the following commit but I hit a problem by the commit.
> > So I report it.
> >
> > commit cecdb193c8d91a42d9489d00618cc3dfff92e55a
> > Author: Rafael J. Wysocki
> >
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:
>> > >> >> > * It abuses flags parameter of DRM_IOCTL_MODE_CREATE_DUMB to
>> > >> >>
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 kernel.
[0.00] memblock_reserve:
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
I feel fairly comfortable with the amount of existing
On Tue, 2013-08-06 at 11:05 +0300, Phil Carmody wrote:
> > On Mon, 2013-08-05 at 14:08 +0300, Phil Carmody wrote:
> > > Lines with incorrect spacing around an operator, such as:
> > > bystander, correct,incorrect
> > > would get "fixed" to
> > > bystander,correct, incorrect
> > > as the
On Tue, Aug 06, 2013 at 11:28:06PM +1000, Michael Ellerman wrote:
> Add a negative test to test__checkevent_pmu_events() to get lots of
> coverage of the negative case, ie. when the modifier is not specified.
>
> Add a test of a single event, and of the group case.
nice! :)
jirka
--
To
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?
>
> Signed-off-by: Ivan T. Ivanov
> ---
> .../devicetree/bindings/usb/msm-ssusb.txt | 39
On Tuesday, August 06, 2013 11:12:51 AM Yasuaki Ishimatsu wrote:
> (2013/08/06 9:15), 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
On Tuesday, August 06, 2013 08:08:20 AM Nishanth Menon wrote:
> change in subject to reflect new discussion.
>
> On 05:53-20130806, Randy Dunlap wrote:
> > On 08/03/2013 02:25 AM, Viresh Kumar wrote:
> > >Export opp_add() so that modules can use it.
> > >
Hi Gleb, Paolo, Marcelo, Takuya,
Any comments or further comments? :)
On 07/30/2013 09:01 PM, Xiao Guangrong wrote:
> Background
> ==
> Currently, when mark memslot dirty logged or get dirty page, we need to
> write-protect large guest memory, it is the heavy work, especially, we need to
On Tue, Aug 6, 2013 at 1:02 AM, 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.
>
> Signed-off-by: Rohit Vaswani
> ---
> arch/arm/boot/dts/Makefile|
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| 11 +
> drivers/usb/phy/Makefile
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
On Tue, Aug 06, 2013 at 11:28:05PM +1000, Michael Ellerman wrote:
> This commit adds support for a new modifier "D", which requests that the
> event, or group of events, be pinned to the PMU.
>
> The "p" modifier is already taken for precise, and "P" may be used in
> future to mean "fully
Many of Key device tree bindings uses the constant number as key code
which matches with kernel header key code and then comment as follows
for reference/better readability:
linux,code = <102>; /* KEY_HOME */
Create a DT header which defines all the key code so that DT key bindings
can
On Tue, Aug 06, 2013 at 11:28:05PM +1000, Michael Ellerman wrote:
SNIP
>
> while (*p) {
> @@ -812,6 +818,9 @@ int parse_events__modifier_event(struct list_head *list,
> char *str, bool add)
> evsel->attr.exclude_guest = mod.eG;
> evsel->exclude_GH =
In place of hardcoding the key code in DTS file and comment the key code
as side notes, use the key code macro defines in the dt-bindings/input/input.h
directly.
Signed-off-by: Laxman Dewangan
---
arch/arm/boot/dts/tegra114-dalmore.dts |9 +
1 files changed, 5 insertions(+), 4
value of devm_request_irq
device tree bindings document:
5. add description of DT DMA node
Applies to next-20130806
.../devicetree/bindings/mmc/moxa,moxart-mmc.txt| 28 +
drivers/mmc/host/Kconfig | 9 +
drivers/mmc/host/Makefile
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_supplicant
log
johannes
--
To unsubscribe from this list:
On Fri, 02 Aug, at 02:29:03PM, Roy Franz wrote:
> No code changes made, just moving functions from x86 arch directory
> to common location.
> Code is shared using #include, similar to how decompression code
> is shared among architectures.
>
> Signed-off-by: Roy Franz
> ---
>
On Fri, 02 Aug, at 02:29:04PM, Roy Franz wrote:
> * Change the EFI helper functions to be more flexible to allow their use
> by other architectures.
> * Pass system table pointer as argument to all functions that use it,
> rather than use a global variable.
> * Change name of __get_map to
On Tuesday, August 06, 2013 07:08:24 PM Viresh Kumar wrote:
> On 3 August 2013 17:19, Viresh Kumar wrote:
> > 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
On Tue, 2013-08-06 at 13:21 +0100, Pawel Moll wrote:
> On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > Signed-off-by: Ivan T. Ivanov
>
> The same comment as for the RFC 1/2 here...
Will fix this.
>
> > .../devicetree/bindings/usb/msm-ssusb.txt
I have an open bug again the aforementioned patch:
https://bugs.freedesktop.org/show_bug.cgi?id=67276 . Can you, please,
hold the patch, untill the bug is resolved?
--
--joshua
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 3 August 2013 17:19, Viresh Kumar wrote:
> 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
> ++---
>
Am 06.08.2013 12:14, schrieb Greg Kroah-Hartman:
>> What exactly is a platform device anyway?
>
> Originally it was a "something that wasn't connected to a bus, but just
> had memory-mapped i/o." Like the PS2 keyboard controller.
>
> Embedded systems got ahold of this and went to town, and
Hi!
I just did some block device tuning according to some expert's advice which
resulted in multipath failures. I'm not going to discuss this as I'll have to
investigate further, but I'd like to point out that the messages like
"[440682.559851] blk_rq_check_limits: over max size limit." lack
Hi,
On Tue, 2013-08-06 at 13:12 +0100, Pawel Moll wrote:
> On Tue, 2013-08-06 at 12:53 +0100, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > Signed-off-by: Ivan T. Ivanov
>
> I am sure that the information in the subject is more than enough for
> you, but would you care to give
Add a negative test to test__checkevent_pmu_events() to get lots of
coverage of the negative case, ie. when the modifier is not specified.
Add a test of a single event, and of the group case.
Signed-off-by: Michael Ellerman
---
tools/perf/tests/parse-events.c | 53
301 - 400 of 1196 matches
Mail list logo
