> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, October 04, 2013 11:42 PM
> To: Bhushan Bharat-R65777
> Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> linux-
> ker...@vger.kernel.org;
On Sun, Oct 06, 2013 at 09:41:21AM +0100, Russell King - ARM Linux wrote:
> On Sun, Oct 06, 2013 at 03:58:11PM +0800, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
> > commit c817a67ecba7c3c2aaa104796d78f160af60920d
> > Author: Russell King
> >
After read the code again, I have addtional opinion for discussing,
please check thanks.
The related contents are at bottom.
On 09/13/2013 09:52 AM, Chen Gang wrote:
> On 09/13/2013 07:36 AM, Thomas Gleixner wrote:
>> That crusade does not involve any failure analysis or test cases. It's
>>
On Mon, Oct 07, 2013 at 10:11:18AM +0800, Fengguang Wu wrote:
> On Sun, Oct 06, 2013 at 10:26:24AM -0700, Linus Torvalds wrote:
> > On Sun, Oct 6, 2013 at 1:23 AM, Fengguang Wu wrote:
> > >
> > > I got the below dmesg and the first bad commit is commit cf39c8e5352b:
> > > Merge tag
Got it.
On Mon, Oct 7, 2013 at 12:41 PM, Mike Galbraith wrote:
> On Fri, 2013-10-04 at 20:06 +0800, Ethan Zhao wrote:
>> Mike, Peter,
>>Seems lots of work has been done these days, studious guys. those
>> patches merged in last stable/dev branch (fix performance regression
>> caused by extra
On 10/06/2013 05:41 PM, Russell King - ARM Linux wrote:
> On Sun, Oct 06, 2013 at 05:30:47PM -0500, Joel Fernandes wrote:
>> On receiving IRQ exception in SVC mode, all the SVC mode registers are saved
>> onto the stack very early on.
>>
>> The stack frame allocation code for IRQ entry during SVC
This patch suppresses the following compilation warnings (mostly unused
variables):
fs/btrfs/backref.c: In function 'iterate_inode_extrefs':
fs/btrfs/backref.c:1652:6: warning: variable 'slot' set but not used
[-Wunused-but-set-variable]
int slot;
^
fs/btrfs/ctree.c: In function
Quoting Jonas Jensen (2013-07-29 02:44:22)
> This patch adds MOXA ART SoCs clock driver support.
>
> Signed-off-by: Jonas Jensen
I've taken this patch into clk-next. Thanks for the rework.
Is it possible for parent clocks of these moxa core clocks to change
rate? It might make sense for your
On Fri, 2013-10-04 at 20:06 +0800, Ethan Zhao wrote:
> Mike, Peter,
>Seems lots of work has been done these days, studious guys. those
> patches merged in last stable/dev branch (fix performance regression
> caused by extra rtimer programming and rescheduling IPI,confusing
> idle... etc) ? So
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> Programs have been known to test for empty directories by attempting
> to remove them. To keep from violating the principle of least
> surprise don't let directories the caller can see with someting
> mounted on them be deleted.
Do you
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> Signed-off-by: Eric W. Biederman
> ---
> fs/mount.h |1 +
> fs/namespace.c | 24
> 2 files changed, 25 insertions(+), 0 deletions(-)
>
> diff --git a/fs/mount.h b/fs/mount.h
> index
Ping? :)
(2013/09/30 18:21), Masami Hiramatsu wrote:
> Fix to find the correct (as much as possible) line information
> for listing probes. Without this fix, perf probe --list action
> will show incorrect line information as below;
>
> # perf probe getname_flags
> # perf probe -l
>
Hi,
This a partial review, based on the stuff I've managed to review
so far!
1. This is a substantial performance improvement, which is great
stuff!
But like the "squashfs: remove cache for normal data page" patch
it needs to be optional, with the previous behaviour retained as
So instead of breaking superblock sharing and fscache functionality
with 2), it may be better off to explore 1). Will spend some time doing so.
Regards,
Shirish
On Fri, May 10, 2013 at 9:27 AM, Jeff Layton wrote:
> On Fri, 10 May 2013 16:13:30 +0200
> Miklos Szeredi wrote:
>
>> Hi,
>>
>> A
On 10/06/2013 08:57 PM, Alex Dubov wrote:
Hi,
In the good old times, when this driver was first written, device name used to
be a fixed
size array (of 32 chars, if I'm not mistaken) in the kobj struct, so there was
no need to
free it explicitly.
Since than, somebody changed the name field to
(2013/10/03 15:12), HATAYAMA Daisuke wrote:
(2013/10/02 21:03), Michael Holzheu wrote:
Hello Alexey,
Looks like the following commit broke mmap for /proc/vmcore:
commit c4fe24485729fc2cbff324c111e67a1cc2f9adea
Author: Alexey Dobriyan
Date: Tue Aug 20 22:17:24 2013 +0300
sparc: fix
Hi,
Please do checkpatch.pl before sending a patch.
Thanks,
2013-09-30 (월), 18:28 +0800, yuan zhong:
> Previously, do_checkpoint() will call congestion_wait() for waiting the
> pages (previous submitted node/meta/data pages) to be written back.
> Because congestion_wait() will set a regular
Hi Sergei,
(replying from my personal e-mail)
On Sun, Oct 6, 2013 at 3:02 PM, Sergei Shtylyov
wrote:
>
> Hello.
>
> On 05-10-2013 0:30, David Cohen wrote:
>
>> If USB_FUNCTIONFS is selected without USB_FUNCTIONFS_ETH and
>> USB_FUNCTIONFS_RNIS, u_ether.h won't be included and then
>>
On Sun, Oct 6, 2013 at 8:54 PM, Theodore Ts'o wrote:
> On Mon, Oct 07, 2013 at 02:27:04AM +0100, Matthew Garrett wrote:
>> > > Having a per-entry comment is significantly clearer.
>> >
>> > That is your opinion, it's not a demonstrable fact.
>>
>> Say one of the machines turns out to need the
Hi Felipe,
On Sun, Oct 06, 2013 at 09:55:17PM -0300, Felipe Pena wrote:
> The zynq_clk_register_fclk function can leak memory (fclk_lock) when unable
> to alloc memory for fclk_gate_lock
>
> Signed-off-by: Felipe Pena
> ---
> drivers/clk/zynq/clkc.c |1 +
> 1 file changed, 1 insertion(+)
On Sun, Oct 6, 2013 at 8:27 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 08:01:34PM -0500, Felipe Contreras wrote:
>> On Sun, Oct 6, 2013 at 7:53 PM, Matthew Garrett wrote:
>> > No, it demonstrably doesn't. The comments that do exist refer to only a
>> > subset of the entries underneath
On Sun, Oct 06, 2013 at 10:26:24AM -0700, Linus Torvalds wrote:
> On Sun, Oct 6, 2013 at 1:23 AM, Fengguang Wu wrote:
> >
> > I got the below dmesg and the first bad commit is commit cf39c8e5352b:
> > Merge tag 'stable/for-linus-3.12-rc0-tag' of
> >
In my original patch[1] I wrote a comment describing the reason for
disabling Windows 2012 OSI mode for a group of machines, however, due to
unknown reasons (probably a conflict resolution mismatch), the comment
was dropped in 94fb982 (ACPI: blacklist win8 OSI for buggy laptops).
Since Matthew
On Sun, Oct 06, 2013 at 08:18:15PM +0100, Oussama Ghorbel wrote:
> Yes, to summarize, the idea of this patch was to fix the incoherence
> in the condition of ip6gre_tunnel_change_mtu function
>
> if (new_mtu < 68 ||
>new_mtu > 0xFFF8 - dev->hard_header_len - tunnel->hlen)
>
> From the
(2013/10/03 22:47), Dave Anderson wrote:
- Original Message -
(2013/10/02 18:13), HATAYAMA Daisuke wrote:
(2013/10/02 16:48), Kees Cook wrote:
+
+ return 0;
+}
+
+/*
* Determine if we were loaded by an EFI loader. If so, then we have also
been
* passed the efi
Runtime power management by exynos-iommu driver independently from
master H/W's runtime pm is not useful for power saving since attaching
master H/W in probing time turns on its local power endlessly.
Thus this removes runtime pm API calls.
Runtime PM support is added in the following commits to
Patch written by Antonios Motakis :
IOMMU groups are expected by certain users of the IOMMU API,
e.g. VFIO. Since each device is behind its own System MMU, we
can allocate a new IOMMU group for each device.
Reviewd-by: Cho KyongHo
Signed-off-by: Antonios Motakis
---
iommu_attach_device() against exynos-iommu positive integer on success
if the caller calls iommu_attach_device() with the same iommu_domain
multiple times without call to iommu_detach_device() to inform the
caller how many calls to iommu_detach_device() to really detach iommu.
However the
This adds support for Suspend to RAM and Runtime Power Management.
Since System MMU is located in the same local power domain of its
master H/W, System MMU must be initialized before it is working if
its power domain was ever turned off. TLB invalidation according to
unmapping on page tables must
This turns on ACGEN and SYSSEL.
ACGEN is architectural clock gating that gates clocks by System MMU
itself if it is not active. Note that ACGEN is different from clock
gating by the CPU. ACGEN just gates clocks to the internal logic of
System MMU while clock gating by the CPU gates clocks to the
Since acquiring read_lock is not more frequent than write_lock, it is
not beneficial to use rwlock, this commit changes rwlock to spinlock.
Reviewed-by: Grant Grundler
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 35 ++-
1 files changed, 18
Hi,
In the good old times, when this driver was first written, device name used to
be a fixed
size array (of 32 chars, if I'm not mistaken) in the kobj struct, so there was
no need to
free it explicitly.
Since than, somebody changed the name field to become a loose pointer, but it's
not
This commit adds device tree support for System MMU.
This also include the following changes and enhancements:
* use managed device helper functions.
Simplyfies System MMU device driver.
Signed-off-by: Cho KyongHo
---
drivers/iommu/Kconfig|5 ++---
drivers/iommu/exynos-iommu.c |
This commit removes custom fault handler. The device drivers that
need to register fault handler can register
with iommu_set_fault_handler().
CC: Grant Grundler
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 80 -
1 files changed, 24
This patch adds dts entries for the System MMU devices found on
Exynos4 and Exynos5 SoC series and the System MMU binding
documentation.
CC: Sylwester Nawrocki
Signed-off-by: Cho KyongHo
---
.../bindings/iommu/samsung,exynos4210-sysmmu.txt | 76 +
arch/arm/boot/dts/exynos4.dtsi
This adds gate clocks of all System MMUs and their master IPs
that are not apeared in clk-exynos5250.c and clk-exynos5420.c
Also fixes GATE_IP_ACP to 0x18800 and changed GATE_DA to GATE
for System MMU clocks in clk-exynos4.c
Signed-off-by: Cho KyongHo
---
This patch gates clocks of master H/W as well as clocks of System MMU
if master clocks are specified.
Some Exynos SoCs (i.e. GScalers in Exynos5250) have dependencies in
the gating clocks of master H/W and its System MMU. If a H/W is the
case, accessing control registers of System MMU is
This patch uses managed device helper functions in the probe().
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 64 -
1 files changed, 25 insertions(+), 39 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c
Checking if the probing device has a parent device was just to discover
if the probing device is involved in a power domain when the power
domain controlled by Samsung's custom implementation.
Since generic IO power domain is applied, it is required to remove
the condition to see if the probing
This patch removes dbgname member from sysmmu_drvdata structure.
Kernel message for debugging already has the name of a single
System MMU node.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 34 +-
1 files changed, 13 insertions(+), 21
Since kmalloc() does not guarantee that the allignment of 1KiB when it
allocates 1KiB, it is required to allocate lv2 page table from own
slab that guarantees alignment of 1KiB
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 34 --
1 files
L2TLB is 8-way set-associative TLB with 512 entries. The number of
sets is 64.
A single 4KB(small page) translation information is cached
only to a set whose index is the same with the lower 6 bits of the page
frame number.
A single 64KB(large page) translation information can be
cached to any 16
On Mon, Oct 07, 2013 at 02:27:04AM +0100, Matthew Garrett wrote:
> > > Having a per-entry comment is significantly clearer.
> >
> > That is your opinion, it's not a demonstrable fact.
>
> Say one of the machines turns out to need the quirk for two different
> reasons. How do we document that?
System MMU driver is changed to control only a single instance of
System MMU at a time. Since a single instance of System MMU has only
a single clock descriptor for its clock gating, there is no need to
obtain two or more clock descriptors.
Signed-off-by: Cho KyongHo
---
This patch changes not to panic on any error when updating page table.
Instead prints error messages with callstack.
Signed-off-by: Cho KyongHo
---
drivers/iommu/exynos-iommu.c | 58 +++--
1 files changed, 44 insertions(+), 14 deletions(-)
diff --git
This commit adds cache flush for removed small and large page entries
in exynos_iommu_unmap(). Missing cache flush of removed page table
entries can cause missing page fault interrupt when a master IP
accesses an unmapped area.
Reviewed-by: Tomasz Figa
Tested-by: Grant Grundler
Signed-off-by:
Commit 25e9d28d92 (ARM: EXYNOS: remove system mmu initialization from
exynos tree) removed arch/arm/mach-exynos/mach/sysmmu.h header without
removing remaining use of it from exynos-iommu driver, thus causing a
compilation error.
This patch fixes the error by removing respective include line
from
The current exynos-iommu(System MMU) driver does not work autonomously
since it is lack of support for power management of peripheral blocks.
For example, MFC device driver must ensure that its System MMU is disabled
before MFC block is power-down not to invalidate IOTLB in the System MMU
when I/O
On Sun, Oct 06, 2013 at 05:04:36PM -0700, Dmitry Torokhov wrote:
> Peter Hutterer wrote:
> >On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote:
> >> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote:
> >> > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote:
On Sun, Oct 06, 2013 at 08:01:34PM -0500, Felipe Contreras wrote:
> On Sun, Oct 6, 2013 at 7:53 PM, Matthew Garrett wrote:
> > No, it demonstrably doesn't. The comments that do exist refer to only a
> > subset of the entries underneath them.
>
> That's not true.
>
> /*
> * BIOS invocation of
On Sun, Oct 6, 2013 at 7:53 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 07:50:18PM -0500, Felipe Contreras wrote:
>> On Sun, Oct 6, 2013 at 7:32 PM, Matthew Garrett wrote:
>> > I don't get the final
>> > say in whether or not this patch gets merged, but there's a decent
>> > chance that
The zynq_clk_register_fclk function can leak memory (fclk_lock) when unable
to alloc memory for fclk_gate_lock
Signed-off-by: Felipe Pena
---
drivers/clk/zynq/clkc.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/zynq/clkc.c b/drivers/clk/zynq/clkc.c
index cc40fe6..7ea4b5c
On Sun, Oct 06, 2013 at 07:50:18PM -0500, Felipe Contreras wrote:
> On Sun, Oct 6, 2013 at 7:32 PM, Matthew Garrett wrote:
> > I don't get the final
> > say in whether or not this patch gets merged, but there's a decent
> > chance that I'm going to be the one who has to remove the entries again
>
On Fri, Oct 04, 2013 at 07:13:31AM +0100, Phillip Lougher wrote:
> Minchan Kim wrote:
> >Sqsuashfs have used cache for normal data pages but it's pointless
> >because MM already has cache layer and squashfs adds extra pages
> >into MM's page cache when it reads a page from compressed block.
> >
>
On Sun, Oct 6, 2013 at 7:32 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 07:27:48PM -0500, Felipe Contreras wrote:
>
>> If _you_ want to add comments for each entry in the list you can do so
>> after this patch is applied.
>
> If you want to participate in a collaborative development
On Sun, Oct 06, 2013 at 07:27:48PM -0500, Felipe Contreras wrote:
> If _you_ want to add comments for each entry in the list you can do so
> after this patch is applied.
If you want to participate in a collaborative development effort you
should pay attention to other people's concerns. I don't
On Sun, Oct 6, 2013 at 6:57 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 06:36:57PM -0500, Felipe Contreras wrote:
>> On Sun, Oct 6, 2013 at 6:31 PM, Matthew Garrett wrote:
>> > On Sun, Oct 06, 2013 at 06:27:28PM -0500, Felipe Contreras wrote:
>> >> From acpi_osi_dmi_table:
>> >>
>> >>
On Fri, Oct 04 2013 at 1:07pm -0400,
Mike Snitzer wrote:
> With your latest fix I was able to create a thin device and format with
> XFS. Unfortunately, when I tried to run the thinp-test-suite the very
> first BasicTests test (test_dd_benchmark) fails -- need to look closer
> but it would
Turn the initial value of sysctl kernel.sysrq (SYSRQ_DEFAULT_ENABLE)
into a Kconfig variable.
Original version by Bastian Blank .
Signed-off-by: Ben Hutchings
---
v2:
- Added cross-references between sysrq.txt and Kconfig help
(and added the hex values with a preparatory patch)
- Removed the
Peter Hutterer wrote:
>On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote:
>> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote:
>> > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote:
>> > > As we painfully noticed during the 3.12 merge-window our
>> > >
On 10/04/2013 03:54 AM, Catalin Marinas wrote:
On 3 October 2013 22:13, Larry Finger wrote:
diff --git a/drivers/memstick/core/memstick.c b/drivers/memstick/core/memstick.c
index ffcb10a..0c73a45 100644
--- a/drivers/memstick/core/memstick.c
+++ b/drivers/memstick/core/memstick.c
@@ -415,6
Looks good.
Will plan to merge into cifs-2..6.git soon.
Probably should also go to stable kernels
On Sun, Oct 6, 2013 at 2:08 PM, Jan Klos wrote:
> When connecting to SMB2/3 shares, maximum file size is set to non-LFS maximum
> in superblock. This is due to cap_large_files bit being different
On Sun, Oct 06, 2013 at 06:36:57PM -0500, Felipe Contreras wrote:
> On Sun, Oct 6, 2013 at 6:31 PM, Matthew Garrett wrote:
> > On Sun, Oct 06, 2013 at 06:27:28PM -0500, Felipe Contreras wrote:
> >> From acpi_osi_dmi_table:
> >>
> >> /*
> >> * BIOS invocation of _OSI(Linux) is almost always a BIOS
It makes more sense to enter a bitmask in hexadecimal rather than
decimal. Sadly we can't make it read back as hexadecimal.
Signed-off-by: Ben Hutchings
---
Documentation/sysrq.txt | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/Documentation/sysrq.txt
On Sun, Oct 6, 2013 at 6:31 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 06:27:28PM -0500, Felipe Contreras wrote:
>> From acpi_osi_dmi_table:
>>
>> /*
>> * BIOS invocation of _OSI(Linux) is almost always a BIOS bug.
>> * Linux ignores it, except for the machines enumerated below.
>> */
>
On Sun, Oct 06, 2013 at 06:27:28PM -0500, Felipe Contreras wrote:
> From acpi_osi_dmi_table:
>
> /*
> * BIOS invocation of _OSI(Linux) is almost always a BIOS bug.
> * Linux ignores it, except for the machines enumerated below.
> */
Which was a mistake. We learn from mistakes rather than
Уж перстня верного утратя впечатленье,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sun, Oct 6, 2013 at 3:59 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 03:51:05PM -0500, Felipe Contreras wrote:
>> On Sun, Oct 6, 2013 at 3:45 PM, Matthew Garrett wrote:
>> > On Sun, Oct 06, 2013 at 03:40:42PM -0500, Felipe Contreras wrote:
>> >
>> >> In case you didn't hear, the plan
On Sun, Oct 06, 2013 at 12:47:00AM -0700, Dmitry Torokhov wrote:
> On Fri, Oct 04, 2013 at 09:32:23AM +1000, Peter Hutterer wrote:
> > On Thu, Oct 03, 2013 at 12:10:36AM +0200, David Herrmann wrote:
> > > As we painfully noticed during the 3.12 merge-window our
> > > EVIOCGABS/EVIOCSABS API is
(Adding Andrew Morton)
On Sun, 2013-10-06 at 15:23 -0700, Josh Triplett wrote:
> Kernel maintainers reject new instances of the GPL boilerplate paragraph
> directing people to write to the FSF for a copy of the GPL, since the
> FSF has moved in the past and may do so again.
>
> Make this an
On Sun, Oct 06, 2013 at 03:23:42PM -0700, Josh Triplett wrote:
> Kernel maintainers reject new instances of the GPL boilerplate paragraph
> directing people to write to the FSF for a copy of the GPL, since the
> FSF has moved in the past and may do so again.
>
> Make this an error for new code,
On Sun, Oct 06, 2013 at 05:30:47PM -0500, Joel Fernandes wrote:
> On receiving IRQ exception in SVC mode, all the SVC mode registers are saved
> onto the stack very early on.
>
> The stack frame allocation code for IRQ entry during SVC mode (svc_entry) is
> hard to read as 4-less is allocated
On receiving IRQ exception in SVC mode, all the SVC mode registers are saved
onto the stack very early on.
The stack frame allocation code for IRQ entry during SVC mode (svc_entry) is
hard to read as 4-less is allocated initially only to be allocated later
implicity using the mov r3, [sp, #-4]!
Kernel maintainers reject new instances of the GPL boilerplate paragraph
directing people to write to the FSF for a copy of the GPL, since the
FSF has moved in the past and may do so again.
Make this an error for new code, but just a --strict CHK in --file mode;
anyone interested in doing
- torva...@linux-foundation.org wrote:
> On Sun, Oct 6, 2013 at 1:23 AM, Fengguang Wu
> wrote:
> >
> > I got the below dmesg and the first bad commit is commit
> cf39c8e5352b:
> > Merge tag 'stable/for-linus-3.12-rc0-tag' of
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
>
>
On Sun, Oct 06, 2013 at 03:01:26PM -0700, Joe Perches wrote:
> On Sun, 2013-10-06 at 14:48 -0700, Josh Triplett wrote:
> > There are two common approaches to breaking long lines at binary
> > operators: breaking the line before the operator (putting the operator
> > at the start of the next line),
On Sun, Oct 6, 2013 at 2:33 PM, Al Viro wrote:
>
> Objections?
No objections, my comment was more of a "probably nobody cares" rather
than much of an objection to you deciding you care enough to fix it..
Linus
--
To unsubscribe from this list: send the line "unsubscribe
On Sun, 2013-10-06 at 14:48 -0700, Josh Triplett wrote:
> There are two common approaches to breaking long lines at binary
> operators: breaking the line before the operator (putting the operator
> at the start of the next line), or breaking the line after the operator
> (putting the operator at
On Sun, 2013-10-06 at 14:33 -0700, Josh Triplett wrote:
> On Sun, Oct 06, 2013 at 02:27:17PM -0700, Joe Perches wrote:
> > On Sun, 2013-10-06 at 14:18 -0700, Josh Triplett wrote:
> > > On Sat, Oct 05, 2013 at 11:27:39PM -0700, Greg Kroah-Hartman wrote:
> > > > On Sat, Oct 05, 2013 at 11:51:48AM
There are two common approaches to breaking long lines at binary
operators: breaking the line before the operator (putting the operator
at the start of the next line), or breaking the line after the operator
(putting the operator at the end of the previous line).
CodingStyle doesn't define any
> Andrew has mentioned, that some bootloaders might disable clocks but
> leave the nodes enabled. Reading those registers would lock up
> the HW, of course. So we thought about to check clk gate status first,
> which this patch is about.
>
> Of course, we can do clk_enable, read, clk_disable as
On Sun, Oct 06, 2013 at 01:42:05PM -0700, Linus Torvalds wrote:
> On Sat, Oct 5, 2013 at 5:43 PM, Al Viro wrote:
> >
> > In other words, the size of notes section is ignored for
> > RLIMIT_CORE purposes. Is that intentional?
>
> I doubt it is intentional, but I also cannot really feel
On Sun, Oct 06, 2013 at 02:27:17PM -0700, Joe Perches wrote:
> On Sun, 2013-10-06 at 14:18 -0700, Josh Triplett wrote:
> > On Sat, Oct 05, 2013 at 11:27:39PM -0700, Greg Kroah-Hartman wrote:
> > > On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote:
> > > > On Sat, 2013-10-05 at 11:43
On Sun, 2013-10-06 at 14:18 -0700, Josh Triplett wrote:
> On Sat, Oct 05, 2013 at 11:27:39PM -0700, Greg Kroah-Hartman wrote:
> > On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote:
> > > On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote:
> > > > Kernel maintainers reject new
Hmm. rc4 has more new commits than rc3, which doesn't make me feel all
warm and fuzzy, but nothing major really stands out. More filesystem
upfates than normal at this stage, perhaps, but I suspect that is just
happenstance. We have cifs, xfs, btrfs, fuse and nilfs2 fixes here.
There's the usual
On Sat, Oct 05, 2013 at 11:27:39PM -0700, Greg Kroah-Hartman wrote:
> On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote:
> > On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote:
> > > Kernel maintainers reject new instances of the GPL boilerplate paragraph
> > > directing people to
On Sun, Oct 06, 2013 at 12:01:52AM -0700, Joe Perches wrote:
> On Sat, 2013-10-05 at 23:27 -0700, Greg Kroah-Hartman wrote:
> > On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote:
> > > On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote:
> > > > Kernel maintainers reject new instances
On Sun, Oct 6, 2013 at 4:42 PM, Linus Torvalds
wrote:
> I doubt it is intentional, but I also cannot really feel that we care
> deeply. Afaik we don't really honor the size limit exactly anyway, ie
> we tend to check only at page boundaries etc. So do we really care?
I could imagine in the case
On Sun, Oct 6, 2013 at 3:24 PM, Sebastian Hesselbarth
wrote:
> On 10/06/2013 10:02 PM, Mike Turquette wrote:
>>
>> Quoting Sebastian Hesselbarth (2013-10-06 12:42:01)
>>>
>>> On 10/06/2013 06:30 PM, Andrew Lunn wrote:
On Sun, Oct 06, 2013 at 11:06:09AM +0200, Gerhard Sittig wrote:
>
Hello.
On 05-10-2013 0:30, David Cohen wrote:
If USB_FUNCTIONFS is selected without USB_FUNCTIONFS_ETH and
USB_FUNCTIONFS_RNIS, u_ether.h won't be included and then
USB_ETHERNET_MODULE_PARAMAETERS macro won't be available causing the
following warning compilation:
On Sun, Oct 06, 2013 at 03:51:05PM -0500, Felipe Contreras wrote:
> On Sun, Oct 6, 2013 at 3:45 PM, Matthew Garrett wrote:
> > On Sun, Oct 06, 2013 at 03:40:42PM -0500, Felipe Contreras wrote:
> >
> >> In case you didn't hear, the plan was to add an entry if a user
> >> reports the backlight not
On Mon, Oct 07, 2013 at 12:45:44AM +0400, Evgeniy Polyakov wrote:
> Hi
>
> 06.10.2013, 23:13, "Hans-Frieder Vogt" :
> > In recent kernels the 1-wire kernel modules do not work any more. The module
> > wire got broken in 3.11-rc1 and 3.12-rc1 introduced a further problem:
>
> Looks like I somehow
On 09/30/2013 03:45 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Sep 27, 2013 at 10:49:37PM +0100, Julien Grall wrote:
On 09/27/2013 10:25 PM, Konrad Rzeszutek Wilk wrote:
@@ -641,7 +641,20 @@ struct console xenboot_console = {
void xen_raw_console_write(const char *str)
{
-
Hi
06.10.2013, 23:13, "Hans-Frieder Vogt" :
> In recent kernels the 1-wire kernel modules do not work any more. The module
> wire got broken in 3.11-rc1 and 3.12-rc1 introduced a further problem:
Looks like I somehow missed it and bugs got in
> 1: 3.11-rc1 introduced the automatic loading of
Hello.
On 05-10-2013 18:02, Matthias Beyer wrote:
s/asterix/asterisk/. Asterix is a hero of the infamous French movies,
asterisk is *.
instead of type
Don't continue the subject this way in he changelog.
Signed-off-by: Matthias Beyer
WBR, Sergei
--
To unsubscribe from this
On Sun, Oct 6, 2013 at 3:45 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 03:40:42PM -0500, Felipe Contreras wrote:
>
>> In case you didn't hear, the plan was to add an entry if a user
>> reports the backlight not working correctly, and acpi_osi="!Windows
>> 2012" fixing it with no
On Sun, Oct 06, 2013 at 03:40:42PM -0500, Felipe Contreras wrote:
> In case you didn't hear, the plan was to add an entry if a user
> reports the backlight not working correctly, and acpi_osi="!Windows
> 2012" fixing it with no negative effects. and that's what users did in
> bug #60682.
So add
Hello, I am Mr. M. Barlow from Paris, France. I have been advised to contact
you regarding my business investment in your country. For urgent response and
more details, kindly get back to me via this E-mail: bc82...@gmail.com or
Telephone number below. Thank you as I wait for your response.
On Sat, Oct 5, 2013 at 5:43 PM, Al Viro wrote:
>
> In other words, the size of notes section is ignored for
> RLIMIT_CORE purposes. Is that intentional?
I doubt it is intentional, but I also cannot really feel that we care
deeply. Afaik we don't really honor the size limit exactly
On Sun, Oct 6, 2013 at 3:33 PM, Matthew Garrett wrote:
> On Sun, Oct 06, 2013 at 03:29:10PM -0500, Felipe Contreras wrote:
>> On Fri, Oct 4, 2013 at 11:12 AM, Matthew Garrett wrote:
>> > On Thu, Oct 03, 2013 at 12:13:03PM -0500, Felipe Contreras wrote:
>> >> More people have reported they need
1 - 100 of 442 matches
Mail list logo
