Re: [PATCH 1/2] bluetooth: don't include local processing of HCI commands in the command timeout

Am 31.05.2014 08:45, schrieb Alexander Holler: Am 31.05.2014 07:28, schrieb Marcel Holtmann: so I actually wonder if we should move away from timer and move to a delayed work item to handle the timeout and if that would actually fix this issue. The problem is that I have absolutely no clue

RE: [PATCH v2 0/10] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate

> > Date: Thu, 08 May 2014 19:23:19 +0900 > > From: Namjae Jeon > > To: Dave Chinner , Theodore Ts'o > > Cc: linux-ext4 , x...@oss.sgi.com, > > linux-fsde...@vger.kernel.org, linux-kernel@vger.kernel.org, > > Ashish Sangwan > > Subject: [PATCH v2 0/10] fs: Introduce FALLOC_FL_INSERT_RA

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

Hi Arnd, On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: > + * The variant using bit fields is less efficient to access, but > + * small and has a wider range as the 32-bit one, plus it keeps > + * the signedness of the original timespec. > + */ > +struct inode_time { > + long long

Re: [RFC 06/32] isofs: fix timestamps beyond 2027

On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: > isofs uses a 'char' variable to load the number of years since > 1900 for an inode timestamp. On architectures that use a signed > char type by default, this results in an invalid date for > anything beyond 2027. > > This adds a cast to 'u8'

Re: [PATCH] driver core/platform: remove unused implicit padding in platform_object

Hi Dan, Le vendredi 30 mai 2014 à 23:10 +0300, Dan Carpenter a écrit : > This changelog doesn't match the patch. > Hum, let me guess I've failed to set the proper subject prefix to add v6 suffic to PATCH: I've changed the patch title since v5 (from Emil Goode)... so it's like a new one. I

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

Geert Uytterhoeven writes: > Hi Arnd, > > On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: >> + * The variant using bit fields is less efficient to access, but >> + * small and has a wider range as the 32-bit one, plus it keeps >> + * the signedness of the original timespec. >> + */ >> +st

Re: [RFC 11/32] xfs: convert to struct inode_time

On 05/30/2014 10:54 PM, Dave Chinner wrote: > > If we are changing the in-kernel timestamp to have a greater dynamic > range that anything we current support on disk, then we need support > for all filesystems for similar translation and constraint. The > filesystems need to be able to tell the ke

Re: [RFC 06/32] isofs: fix timestamps beyond 2027

On 05/31/2014 12:59 AM, Geert Uytterhoeven wrote: > On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: >> isofs uses a 'char' variable to load the number of years since >> 1900 for an inode timestamp. On architectures that use a signed >> char type by default, this results in an invalid date f

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

On 05/30/2014 01:01 PM, Arnd Bergmann wrote: > +#ifdef CONFIG_NEW_INODE_TIME > +/* > + * This is the type we use internally in the kernel to represent > + * absolute times in file system metadata. > + * This structure must not leak out to user space, and new interfaces > + * should be using 64-bit

Re: [RFC 13/32] ext3: convert to struct inode_time

On 05/30/2014 01:01 PM, Arnd Bergmann wrote: > ext3fs uses unsigned 32-bit seconds for inode timestamps, which will work > for the next 92 years, but the VFS uses struct timespec for timestamps, > which is only good until 2038 on 32-bit CPUs. > > This gets us one small step closer to lifting the V

Investment Proposal

-- Dear Friend, it is understandable that you might be a little bit apprehensive because you do not know me but I have a lucrative business proposal of mutual interest to share with you. I got your reference in my search for someone who suits my proposed business relationship. I am Mr. James Wil

Re: [RFC 03/32] fs: introduce sys_utimens64at

Arnd Bergmann writes: > +asmlinkage long sys_utimens64at(int dfd, const char __user *filename, All existing syscall names have the 64 suffix last, including the *at variants, so sys_utimensat64 would be more in line. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA

Re: [PATCH] console: Add persistent scrollback buffers for all VGA consoles

On Sa, 2014-05-31 at 00:26 +0200, Jakub Wilk wrote: > * Manuel Schölling , 2014-05-30, 15:27: > >Add a scrollback buffers for each VGA console. The benefit is that the > >scrollback history is not flushed when switching between consoles but > >is persistent. > > Some people rely on this scrollba

Re: [PATCH 1/3] IIO: Add iio magn_north ABI documentation

On 28/05/14 22:06, Reyad Attiyat wrote: Update documentation for HID compass true/magnetic north sensor. Signed-off-by: Reyad Attiyat --- Documentation/ABI/testing/sysfs-bus-iio | 76 + 1 file changed, 76 insertions(+) diff --git a/Documentation/ABI/testing/s

Re: [PATCH 2/3] IIO: Add iio_chan modifier for True/Magnetic North HID usages

On 28/05/14 22:06, Reyad Attiyat wrote: Updated iio_chan_info_enum for compass north sensor usages, including magnetic/true north and tilt compensation. Signed-off-by: Reyad Attiyat --- drivers/iio/industrialio-core.c | 4 include/linux/iio/types.h | 4 2 files changed, 8 in

Re: [PATCH] IIO: Support for True/Magnetic north

On 27/05/14 16:34, Srinivas Pandruvada wrote: Hi Reyad, On 05/26/2014 08:20 PM, Reyad Attiyat wrote: Hey Jonathan and Srinivas, I have added in the needed magn_north iio sysfs attributes to the documentation. I hope I did everything correct. I noticed that the line length was very long as comp

Re: [PATCH -mm 4/8] slub: never fail kmem_cache_shrink

On Fri, May 30, 2014 at 09:46:33AM -0500, Christoph Lameter wrote: > On Fri, 30 May 2014, Vladimir Davydov wrote: > > > SLUB's kmem_cache_shrink not only removes empty slabs from the cache, > > but also sorts slabs by the number of objects in-use to cope with > > fragmentation. To achieve that, it

Re: [PATCH] IIO: Added iio magn_north ABI documentation

On 27/05/14 16:27, Srinivas Pandruvada wrote: On 05/26/2014 08:20 PM, Reyad Attiyat wrote: Added documentation for HID magnometer true/magnetic north sensor. --- Documentation/ABI/testing/sysfs-bus-iio | 76 + 1 file changed, 76 insertions(+) diff --git a/Docu

[PATCH] power: fixed typo in comment

fixed a trivial comment typo (s/mam/map) in kernel/power/swap.c. Signed-off-by: Niv Yehezkel --- kernel/power/swap.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/swap.c b/kernel/power/swap.c index 8c9a481..aaa3261 100644 --- a/kernel/power/swap.c +++ b/kern

Re: [PATCH -mm 5/8] slab: remove kmem_cache_shrink retval

On Fri, May 30, 2014 at 09:49:55AM -0500, Christoph Lameter wrote: > On Fri, 30 May 2014, Vladimir Davydov wrote: > > > First, nobody uses it. Second, it differs across the implementations: > > for SLUB it always returns 0, for SLAB it returns 0 if the cache appears > > to be empty. So let's get r

[tip:x86/vdso] x86/vdso, build: Make LE access macros clearer, host-safe

Commit-ID: c191920f737a09a7252088f018f6747f0d2f484d Gitweb: http://git.kernel.org/tip/c191920f737a09a7252088f018f6747f0d2f484d Author: H. Peter Anvin AuthorDate: Fri, 30 May 2014 17:03:22 -0700 Committer: H. Peter Anvin CommitDate: Sat, 31 May 2014 03:35:27 -0700 x86/vdso, build: Make

[PATCH v2] console: Add persistent scrollback buffers for all VGA consoles

Add a scrollback buffers for each VGA console. The benefit is that the scrollback history is not flushed when switching between consoles but is persistent. The buffers are allocated on demand when a new console is opened. Signed-off-by: Manuel Schölling --- drivers/video/console/Kconfig | 19

Re: [PATCH -mm 7/8] slub: make dead caches discard free slabs immediately

On Fri, May 30, 2014 at 09:57:10AM -0500, Christoph Lameter wrote: > On Fri, 30 May 2014, Vladimir Davydov wrote: > > > (3) is a bit more difficult, because slabs are added to per-cpu partial > > lists lock-less. Fortunately, we only have to handle the __slab_free > > case, because, as there shoul

[PATCH] driver/netfilter/nfnetlink: removed unused variable

Removes the unused struct net *net = sock_net(skb->sk); Signed-off-by: Robin Schroer --- net/netfilter/nfnetlink.c | 1 - 1 file changed, 1 deletion(-) diff --git a/net/netfilter/nfnetlink.c b/net/netfilter/nfnetlink.c index c138b8f..5cc9db2 100644 --- a/net/netfilter/nfnetlink.c +++ b/net/netf

Re: [PATCH -mm 8/8] slab: reap dead memcg caches aggressively

On Fri, May 30, 2014 at 10:01:26AM -0500, Christoph Lameter wrote: > On Fri, 30 May 2014, Vladimir Davydov wrote: > > > We don't disable free objects caching for SLAB, because it would force > > kfree to always take a spin lock, which would degrade performance > > significantly. > > You can use a

Re: [PATCH RFC - TAKE TWO - 11/12] block, bfq: boost the throughput on NCQ-capable flash-based devices

Hello, Paolo. So, I've actually looked at the code. Here are some questions. On Thu, May 29, 2014 at 11:05:42AM +0200, Paolo Valente wrote: > + * 1) all active queues have the same weight, > + * 2) all active groups at the same level in the groups tree have the same > + *weight, > + * 3) all

[PATCH] staging: gdm724x: Added blank lines after declarations in gdm_lte.c

This patch fixes following checkpatch.pl warning: WARNING: Missing a blank line after declarations in gdm_lte.c Signed-off-by: Scott Weir --- drivers/staging/gdm724x/gdm_lte.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/gdm724x/gdm_lte.c b/drivers/staging/gdm724x/gdm_l

Re: [PATCH] driver core/platform: remove unused implicit padding in platform_object

On Sat, May 31, 2014 at 10:01:39AM +0200, Yann Droneaud wrote: > Hi Dan, > > Le vendredi 30 mai 2014 à 23:10 +0300, Dan Carpenter a écrit : > > This changelog doesn't match the patch. > > > > Hum, let me guess I've failed to set the proper subject prefix > to add v6 suffic to PATCH: > I've

[RFC] Work the fuck out, fatass.

Dear Linus Torvalds, Work the fuck out, fatass. We don't approve of your fat ass. THINK OF THE CHILDREN DROP THAT WEIGHT LIFT DAT WEIGHT GET /FIT/ >Kernel should be called GNU/Linux, not Linux. goto gym your ass is as bloated as your kernel is install gentoo terveisin /g/ -- To unsubscri

Re: [PATCH] drivers/w1/w1_int.c: Fix style errors.

Hi Thomas 31.05.2014, 03:11, "Thomas Wood" : > Replace spaces at beginning of the string with tabs, and replace foo * bar > with foo *bar in a pointer declaration. > > Signed-off-by: Thomas Wood Looks good, thank you. Greg, please pull it into your tree or suggest appropriate. Acked-by: Evgeni

Re: [PATCH v5 11/13] mmc: mmci: add explicit clk control

On Fri, May 30, 2014 at 06:14:40PM +0100, srinivas.kandaga...@linaro.org wrote: > @@ -1325,6 +1329,18 @@ static void mmci_set_ios(struct mmc_host *mmc, struct > mmc_ios *ios) > if (!ios->clock && variant->pwrreg_clkgate) > pwr &= ~MCI_PWR_ON; > > + if ((host->variant->exp

Re: [PATCH v5 02/13] mmc: mmci: convert register bits to use BIT() macro.

On Fri, May 30, 2014 at 06:13:00PM +0100, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch converts the register bits in the header file to use BIT(() > macro, which looks much neater. > > No functional changes done. > > Signed-off-by: Srinivas Kandagatla This

[PATCH 11/11] drivers/net/ethernet/intel: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 6/11] net: wireless: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. wl_cfg80211.c verified by compilation only. phy/phy_cmn.c unverified. The coccinelle script that find and fixes this issu

[PATCH 5/11] drivers/scsi/bfa/bfad_bsg.c: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 9/11] drivers/media: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 10/11] vxge: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 8/11] drivers/media/usb/usbvision/usbvision-core.c: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 7/11] bnx2x: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 2/11] cw1200: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 3/11] isci: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 4/11] via-ircc: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

[PATCH 1/11] USB: kl5kusb105: Remove useless return variables

This patch remove variables that are initialized with a constant, are never updated, and are only used as parameter of return. Return the constant instead of using a variable. Verified by compilation only. The coccinelle script that find and fixes this issue is: // @@ type T; constant C; identif

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

Hi Andreas, On Sat, May 31, 2014 at 10:39 AM, Andreas Schwab wrote: > Geert Uytterhoeven writes: > >> Hi Arnd, >> >> On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: >>> + * The variant using bit fields is less efficient to access, but >>> + * small and has a wider range as the 32-bit one

Re: [PATCH RFC - TAKE TWO - 12/12] block, bfq: boost the throughput with random I/O on NCQ-capable HDDs

Hello, Okay, read this one properly too. On Thu, May 29, 2014 at 11:05:43AM +0200, Paolo Valente wrote: ... > + * As already said, things change with a rotational device, where idling > + * boosts the throughput with sequential I/O (even with NCQ). Hence, for > + * such a device the second compon

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

Geert Uytterhoeven writes: > "int" is signed, right? Or do you mean a bitfield needs an explicit "signed" > keyword to be signed? Yes, see 6.7.2#5. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something

Re: [PATCH RFC - TAKE TWO - 08/12] block, bfq: preserve a low latency also with NCQ-capable drives

On Thu, May 29, 2014 at 11:05:39AM +0200, Paolo Valente wrote: > This patch addresses this issue by not disabling device idling for This patch addresses this issue by allowing device idling for... > weight-raised queues, even if the device supports NCQ. This allows BFQ > to start serving a new qu

Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices

> Right, I read the function which provides the functionality, but my > point is; I don't think my patch changes the semantics in a way which > would adversely affect this option. If you think that it does, can you > specify how please? Currently, if a driver would be DT only and does not provid

Re: [PATCH RFC - TAKE TWO - 09/12] block, bfq: reduce latency during request-pool saturation

On Thu, May 29, 2014 at 11:05:40AM +0200, Paolo Valente wrote: > This patch introduces an heuristic that reduces latency when the > I/O-request pool is saturated. This goal is achieved by disabling > device idling, for non-weight-raised queues, when there are weight- > raised queues with pending or

Re: [PATCH 06/20] arch,avr32: Fold atomic_ops

On Tue, May 13, 2014 at 10:40:32PM +0200, Hans-Christian Egtvedt wrote: > Probably found the reason why we want to use sub with the signed 21-bit > limit, it uses one less register than the add instruction that can add up to > 32-bit values. > > Both instructions are 32-bit, to use a 16-bit instru

Re: [git pull] Re: fs/dcache.c - BUG: soft lockup - CPU#5 stuck for 22s! [systemd-udevd:1667]

On Fri, May 30, 2014 at 1:14 PM, Al Viro wrote: > On Fri, May 30, 2014 at 05:48:16PM +0100, Al Viro wrote: >> On Fri, May 30, 2014 at 08:31:30AM -0700, Linus Torvalds wrote: >> > On Fri, May 30, 2014 at 8:21 AM, Al Viro wrote: >> > > >> > > Linus, how would you prefer it to be handled? >> > >> >

Re: [RFC 24/32] hfs, hfsplus: convert to struct inode_time

Hi Arnd, On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote: > hfs uses 32-bit integers based at 1904 for inode timestamps, which will > only work until 2040, but the VFS uses struct timespec for timestamps, > which expires even earlier in 2038 on 32-bit CPUs. > > This gets us one small step

[PATCH v4 00/15] Thunderbolt driver for Apple MacBooks

Hi This is version 4 of my Thunderbolt driver for Apple hardware (see [1] for v3). Changes since v3: - Fix typos and style problems caught by Bjorn. - Changed the #ifdef CONFIG_ACPI block to cover the whole pci quirk. Andreas [1]: https://lkml.org/lkml/2014/5/26/308 Andreas Noever (15): t

[PATCH v4 04/15] thunderbolt: Add tb_regs.h

Every thunderbolt device consists (logically) of a switch with multiple ports. Every port contains up to four config regions (HOPS, PORT, SWITCH, COUNTERS) which are used to configure the device. The tb_regs.h file contains all known registers and capabilities from these config regions. Signed-of

[PATCH v4 14/15] thunderbolt: Read switch uid from EEPROM

Add eeprom access code and read the uid during switch initialization. The UID will be used to check device identity after suspend. Signed-off-by: Andreas Noever --- drivers/thunderbolt/Makefile | 2 +- drivers/thunderbolt/eeprom.c | 189 +++ drivers/thun

[PATCH v4 10/15] thunderbolt: Add path setup code.

A thunderbolt path is a unidirectional channel between two thunderbolt ports. Two such paths are needed to establish a pci tunnel. This patch introduces struct tb_path as well as a set of tb_path_* methods which are used to activate & deactivate paths. Signed-off-by: Andreas Noever --- drivers/

[PATCH v4 13/15] PCI: Suspend/resume quirks for Apple thunderbolt

Add two quirks to support thunderbolt suspend/resume on Apple systems. We need to perform two different actions during suspend and resume: The whole controller has to be powered down before suspend. If this is not done then the native host interface device will be gone after resume if a thunderbol

[PATCH v4 15/15] thunderbolt: Add suspend/hibernate support

We use _noirq since we have to restore the pci tunnels before the pci core wakes the tunneled devices. Signed-off-by: Andreas Noever --- drivers/thunderbolt/nhi.c| 33 + drivers/thunderbolt/switch.c | 84 drivers/thunderbolt/tb.c

[PATCH v4 12/15] PCI: Add pci_fixup_suspend_late quirk pass

Add pci_fixup_suspend_late as a new pci_fixup_pass. The pass is called from suspend_noirq and poweroff_noirq. Using the same pass for suspend and hibernate is consistent with resume_early which is called by resume_noirq and restore_noirq. The new quirk pass is required for Thunderbolt support on A

[PATCH v4 11/15] thunderbolt: Add support for simple pci tunnels

A pci downstream and pci upstream port can be connected through a tunnel. To establish the tunnel we have to setup two unidirectional paths between the two ports. Right now we only support paths with two hops (i.e. no chaining) and at most one pci device per thunderbolt device. Signed-off-by: And

[PATCH v4 05/15] thunderbolt: Initialize root switch and ports

This patch adds the structures tb_switch and tb_port as well as code to initialize the root switch. Signed-off-by: Andreas Noever --- drivers/thunderbolt/Makefile | 2 +- drivers/thunderbolt/switch.c | 186 +++ drivers/thunderbolt/tb.c | 8 ++ driv

[PATCH v4 09/15] thunderbolt: Handle hotplug events

We receive a plug event callback whenever a thunderbolt device is added or removed. This patch fills in the tb_handle_hotplug method and starts reacting to these events by adding/removing switches from the hierarchy. Signed-off-by: Andreas Noever --- drivers/thunderbolt/switch.c | 42 +++

Re: [RFC 00/32] making inode time stamps y2038 ready

Hi Arnd, On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote: [snip] > > Arnd Bergmann (32): > fs: introduce new 'struct inode_time' > uapi: add struct __kernel_timespec{32,64} > fs: introduce sys_utimens64at > fs: introduce sys_newfstat64/sys_newfstatat64 > arch: hook up new stat a

[PATCH v4 07/15] thunderbolt: Enable plug events

Thunderbolt switches have a plug events capability. This patch adds the tb_plug_events_active method and uses it to activate plug events during switch allocation. Signed-off-by: Andreas Noever --- drivers/thunderbolt/switch.c | 46 drivers/thunderbolt

[PATCH v4 08/15] thunderbolt: Scan for downstream switches

Add utility methods tb_port_state and tb_wait_for_port. Add tb_scan_switch which recursively checks for downstream switches. Signed-off-by: Andreas Noever --- drivers/thunderbolt/switch.c | 97 drivers/thunderbolt/tb.c | 44 d

[PATCH v4 02/15] thunderbolt: Add control channel interface

Thunderbolt devices are configured by reading/writing into their configuration space (similar to pci). This is done by sending packets through the NHI (native host interface) onto the control channel. This patch handles the low level packet based protocol and exposes higher level operations like t

[PATCH v4 01/15] thunderbolt: Add initial cactus ridge NHI support

Thunderbolt hotplug is supposed to be handled by the firmware. But Apple decided to implement thunderbolt at the operating system level. The firmare only initializes thunderbolt devices that are present at boot time. This driver enables hotplug of thunderbolt of non-chained thunderbolt devices on A

[PATCH v4 03/15] thunderbolt: Setup control channel

Add struct tb which will contain our view of the thunderbolt bus. For now it just contains a pointer to the control channel and a workqueue for hotplug events. Add thunderbolt_alloc_and_start() and thunderbolt_shutdown_and_free() which are responsible for setup and teardown of struct tb. Signed-

[PATCH v4 06/15] thunderbolt: Add thunderbolt capability handling

Thunderbolt config areas contain capability lists similar to those found on pci devices. This patch introduces a tb_find_cap utility method to search for capabilities. Signed-off-by: Andreas Noever --- drivers/thunderbolt/Makefile | 2 +- drivers/thunderbolt/cap.c| 116

Re: [RFC 13/32] ext3: convert to struct inode_time

On Saturday 31 May 2014 02:10:45 H. Peter Anvin wrote: > On 05/30/2014 01:01 PM, Arnd Bergmann wrote: > > ext3fs uses unsigned 32-bit seconds for inode timestamps, which will work > > for the next 92 years, but the VFS uses struct timespec for timestamps, > > which is only good until 2038 on 32-bit

Re: [PATCH 0/10] ACPI enumeration rework (was: Re: [PATCH V7 00/11] ACPI: ACPI enumeration rework)

On Fri, 2014-05-30 at 04:20 +0200, Rafael J. Wysocki wrote: > On Friday, May 23, 2014 02:02:22 AM Zhang Rui wrote: > > Hi, all, > > > > Currently, PNP bus is used as the default bus for for enumerating ACPI > > devices with _HID/_CID. > > For a device that needs to be enumerated to platform bus, w

Re: [git pull] Re: fs/dcache.c - BUG: soft lockup - CPU#5 stuck for 22s! [systemd-udevd:1667]

On Sat, 31 May 2014, Josh Boyer wrote: > > One of my machines got the lockdep report below when booting a kernel > that contained these patches. I think this is just a lacking annotation. We do nest dentry d_lock locking, and in order to avoid ABBA deadlocks the rule is that we lock things i

Re: [RFC 00/32] making inode time stamps y2038 ready

On Fri, May 30, 2014 at 10:01:24PM +0200, Arnd Bergmann wrote: > > I picked this because it is a fairly isolated problem, as the > inode time stamps are rarely assigned to any other time values. > As a byproduct of this work, I documented for each of the file > systems we support how long the on-d

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

On Saturday 31 May 2014 02:03:38 H. Peter Anvin wrote: > On 05/30/2014 01:01 PM, Arnd Bergmann wrote: > > +#ifdef CONFIG_NEW_INODE_TIME > > +/* > > + * This is the type we use internally in the kernel to represent > > + * absolute times in file system metadata. > > + * This structure must not leak

Re: [RFC 03/32] fs: introduce sys_utimens64at

On Saturday 31 May 2014 11:22:38 Andreas Schwab wrote: > Arnd Bergmann writes: > > > +asmlinkage long sys_utimens64at(int dfd, const char __user *filename, > > All existing syscall names have the 64 suffix last, including the *at > variants, so sys_utimensat64 would be more in line. Ok, makes s

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

On Saturday 31 May 2014 10:39:02 Andreas Schwab wrote: > Geert Uytterhoeven writes: > > > Hi Arnd, > > > > On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: > >> + * The variant using bit fields is less efficient to access, but > >> + * small and has a wider range as the 32-bit one, plus it

Re: [RFC 01/32] fs: introduce new 'struct inode_time'

Yes, s64/u32 or s64/s32. On May 31, 2014 7:53:01 AM PDT, Arnd Bergmann wrote: >On Saturday 31 May 2014 02:03:38 H. Peter Anvin wrote: >> On 05/30/2014 01:01 PM, Arnd Bergmann wrote: >> > +#ifdef CONFIG_NEW_INODE_TIME >> > +/* >> > + * This is the type we use internally in the kernel to represent

Re: [PATCH 1/11] USB: kl5kusb105: Remove useless return variables

On Sat, May 31, 2014 at 10:14:01AM -0300, Peter Senna Tschudin wrote: > This patch remove variables that are initialized with a constant, > are never updated, and are only used as parameter of return. > Return the constant instead of using a variable. > > Verified by compilation only. > > The coc

Re: [git pull] Re: fs/dcache.c - BUG: soft lockup - CPU#5 stuck for 22s! [systemd-udevd:1667]

On Sat, May 31, 2014 at 10:48 AM, Linus Torvalds wrote: > > > On Sat, 31 May 2014, Josh Boyer wrote: >> >> One of my machines got the lockdep report below when booting a kernel >> that contained these patches. > > I think this is just a lacking annotation. > > We do nest dentry d_lock locking, and

[GIT pull] core fixes for 3.15

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus Three fixlets for long standing issues in the futex/rtmutex code unearthed by Dave Jones syscall fuzzer: - Add missing early deadlock detection

[PATCH] wan: Use usleep_range()

Instead of using a jiffies hack we can use the standard api for delays. Signed-off-by: Manuel Schölling --- drivers/net/wan/farsync.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/drivers/net/wan/farsync.c b/drivers/net/wan/farsync.c index bcfff0d..02f6d1c 1006

Re: [RFC 02/32] uapi: add struct __kernel_timespec{32,64}

On Friday 30 May 2014 13:18:45 H. Peter Anvin wrote: > On 05/30/2014 01:01 PM, Arnd Bergmann wrote: > > We cannot use time_t or any derived structures beyond the year > > 2038 in interfaces between kernel and user space, on 32-bit > > machines. > > > > This is my suggestion for how to migrate sysc

Re: [PATCH 2/11] cw1200: Remove useless return variables

Am 31.05.2014 15:14, schrieb Peter Senna Tschudin: > This patch remove variables that are initialized with a constant, > are never updated, and are only used as parameter of return. > Return the constant instead of using a variable. > > Verified by compilation only. > > The coccinelle script th

Re: [RFC 00/32] making inode time stamps y2038 ready

On Saturday 31 May 2014 16:51:15 Richard Cochran wrote: > On Fri, May 30, 2014 at 10:01:24PM +0200, Arnd Bergmann wrote: > > > > I picked this because it is a fairly isolated problem, as the > > inode time stamps are rarely assigned to any other time values. > > As a byproduct of this work, I docu

Re: [RFC 11/32] xfs: convert to struct inode_time

On Saturday 31 May 2014 11:14:50 Dave Chinner wrote: > On Fri, May 30, 2014 at 05:41:14PM -0700, H. Peter Anvin wrote: > > On 05/30/2014 05:37 PM, Dave Chinner wrote: > > > > > > IOWs, the filesystem has to be able to reject any attempt to set a > > > timestamp that is can't represent on disk othe

[PATCH v2 0/4] clk: qcom: Add APQ8084 Global Clock Controller support

This patchset adds support for the global clock controller found on the APQ8084 based platforms. Patches 1,2 can go through clk-next and 3,4 through arm-soc. Changes from v1: - Moved APQ8084 clocks into a separate file and under separate Kconfig entry. Dropped the override function patch from

[PATCH v2 4/4] ARM: dts: qcom: Add APQ8084 serial port DT node

Add the necessary DT node to probe the serial driver on APQ8084 platforms. Signed-off-by: Georgi Djakov --- arch/arm/boot/dts/qcom-apq8084-mtp.dts |6 ++ arch/arm/boot/dts/qcom-apq8084.dtsi|8 2 files changed, 14 insertions(+) diff --git a/arch/arm/boot/dts/qcom-apq8084

[PATCH v2 1/4] clk: qcom: Add APQ8084 Global Clock Controller documentation

Add the compatible string for the APQ8084 global clock controller to the clock binding documentation. Signed-off-by: Georgi Djakov --- .../devicetree/bindings/clock/qcom,gcc.txt |1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc.txt b

[PATCH] leds: USB: Add support for MSI GT683R led panels

This driver adds support for USB controlled led panels that exist in MSI GT683R laptop. Signed-off-by: Janne Kanniainen --- drivers/leds/Kconfig | 6 ++ drivers/leds/Makefile | 1 + drivers/leds/leds-gt683r.c | 241 + 3 files changed, 2

[PATCH v2 3/4] ARM: dts: qcom: Add APQ8084 Global Clock Controller DT node

This patch adds the necessary node to probe the global clock controller on APQ8084 platforms. Signed-off-by: Georgi Djakov --- arch/arm/boot/dts/qcom-apq8084.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/qcom-apq8084.dtsi b/arch/arm/boot/dts/qcom-apq80

Re: [RFC 11/32] xfs: convert to struct inode_time

On Sat, 31 May 2014, H. Peter Anvin wrote: > On 05/30/2014 10:54 PM, Dave Chinner wrote: > > > > If we are changing the in-kernel timestamp to have a greater dynamic > > range that anything we current support on disk, then we need support > > for all filesystems for similar translation and constr

Warning!!!

Internet Account users, This email is from our Internet web-mail Customer service and we are sending it to every User Accounts Owner for safety,We are having congestion due to the fraudulent e-mails to accounts owners so we are shutting down some accounts and your account was among those to b

Re: [PATCH 1/2] MAINTAINERS: change the email address for f2fs

Hi, 2014-05-31 8:09 GMT+09:00 Stephen Rothwell : > Hi, > > On Sat, 31 May 2014 01:12:08 +0900 jaeg...@kernel.org wrote: >> >> From: Jaegeuk Kim >> >> This patch changes the valid email address to maintain the f2fs file system. > > Have you remembered to notify the linux-next maintainer? :-) Oop

[patch v2 3/5] rtmutex: Confine deadlock logic to futex

The builtin tester is gone,, so the deadlock logic is now only required for futexes. Remove the extra arguments for the public functions and also for the futex specific ones which get always called with deadlock detection enabled. Signed-off-by: Thomas Gleixner Cc: Peter Zijlstra Cc: Steven Ros

[patch v2 2/5] rtmutex: Cleanup deadlock detector debug logic

The conditions under which deadlock detection is conducted are unclear and undocumented. Add constants instead of using 0/1 and provide a selection function which hides the additional debug dependency from the calling code. Add comments where needed. Signed-off-by: Thomas Gleixner Cc: Peter Zij

[patch v2 4/5] rtmutex: Clarify the lock chain walk

Add a separate local variable for the boost/deboost logic to make the code more readable. Add comments where appropriate. Signed-off-by: Thomas Gleixner Cc: Peter Zijlstra Cc: Steven Rostedt Cc: Lai Jiangshan Link: http://lkml.kernel.org/r/20140522031950.168005...@linutronix.de Signed-off-by:

[patch v2 1/5] rtmutex: Remove builtin tester

The tester has been broken for quite some time. It's possible to fix it, but the main reason for having it in the kernel was the lock steal mechanism in the rtmutex code. That's gone, so we can implement a stateful correctness tester just via the futex syscall. Signed-off-by: Thomas Gleixner Cc:

[patch v2 0/5] rtmutex: Code clarification and optimization

Changes vs. v1 [1]: Dropped 1/N as it's queued already. Removed the config symbols as pointed out by Steven. Addressed the review feedback from Steven and Jason. Thanks, tglx --- [1] http://lkml.kernel.org/r/20140522031841.797415...@linutronix.de -- To unsubscribe from this list: send

[patch v2 5/5] rtmutex: Avoid pointless requeueing in the deadlock detection chain walk

In case the dead lock detector is enabled we follow the lock chain to the end in rt_mutex_adjust_prio_chain, even if we could stop earlier due to the priority/waiter constellation. But once we are not longer the top priority waiter in a certain step or the task holding the lock has already the sam

[PATCH 1/11 V2] USB: kl5kusb105: Remove klsi_105_tiocmset function

This patch remove the function klsi_105_tiocmset which was only returning -EINVAL. It also removes the function prototype and the .tiocmset entry in the struct usb_serial_driver. Verified by compilation only. Signed-off-by: Peter Senna Tschudin --- Changes from V1: - remove the function klsi_1

  1   2   >