On Thu, 10 Jul 2014, Satoru Takeuchi wrote:
> Hi Himangi,
>
> (2014/07/09 7:21), Himangi Saraogi wrote:
> > Use BUG_ON(x) rather than if(x) BUG();
> >
> > The semantic patch that fixes this problem is as follows:
> >
> > //
> > @@ identifier x; @@
> > -if (x) BUG();
> > +BUG_ON(x);
> > //
From: Anil Belur
- as kfree() internally check for NULL, additional check it not
required.
Signed-off-by: Anil Belur
---
drivers/staging/rtl8723au/core/rtw_ap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
From: Anil Belur
- as kfree() internally checks for NULL, additional check it not
required.
Signed-off-by: Anil Belur
---
drivers/staging/rtl8723au/core/rtw_cmd.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_cmd.c
On Thursday 10 July 2014 03:06 AM, Greg KH wrote:
> On Tue, Jul 08, 2014 at 11:42:42AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> On Tuesday 08 July 2014 07:14 AM, Greg KH wrote:
>>> On Mon, Jul 07, 2014 at 12:18:20PM +0530, Kishon Vijay Abraham I wrote:
From: Kamil Debski
Set cmd_per_lun to reflect value supported by the Host.
In this version of the patch I have addressed comments from
Christoph Hellwig
Signed-off-by: K. Y. Srinivasan
Cc:
---
drivers/scsi/storvsc_drv.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Going forward it is possible that some of the commands that are not currently
implemented will be implemented on future Windows hosts. Even if they are not
implemented, we are told the host will corrrectly handle unsupported
commands (by returning appropriate return code and sense information).
From: Behan Webster
With compilers which follow the C99 standard (like modern versions of gcc and
clang), "extern inline" does the wrong thing (emits code for an externally
linkable version of the inline function). In this case using static inline
and removing the NULL version of return_address
Implement a simple abort handler. The host does not support "Abort"; just
ensure that all inflight I/Os have been accounted for.
In this version of the patch I have addressed comments from
Christoph Hellwig
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c | 22
SRB status can have additional information. Mask these out before processing
SRB status.
In this version of the patch I have addressed comments from
Christoph Hellwig
Signed-off-by: K. Y. Srinivasan
Cc:
---
drivers/scsi/storvsc_drv.c |5 -
1 files changed, 4 insertions(+), 1
Based on the negotiated VMBUS protocol version, we adjust the size of the
storage
protocol messages. The two sizes we currently handle are pre-win8 and post-win8.
In WS2012 R2, we are negotiating higher VMBUS protocol version than the win8
version. Make adjustments to correctly handle this.
In
On some Windows hosts on FC SANs, TEST_UNIT_READY can return SRB_STATUS_ERROR.
Correctly handle this.
In this version of the patch I have addressed comments from
Christoph Hellwig
Signed-off-by: K. Y. Srinivasan
Cc:
---
drivers/scsi/storvsc_drv.c |7 +++
1 files changed, 7
Correctly set SRB flags for all valid I/O directions. Some IHV drivers on the
Windows host require this.
Signed-off-by: K. Y. Srinivasan
Cc:
---
drivers/scsi/storvsc_drv.c | 12 +---
1 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c
Hyper-V hosts can support multiple targets and multiple channels and larger
number of
LUNs per target. Update the code to reflect this. With this patch we can
correctly
enumerate all the paths in a multi-path storage environment.
In this version of the patch I have addressed comments from
In this patch set I have fixed a few bugs and implemented some enhancements.
In this version of the patch I have addressed comments from
Christoph Hellwig
K. Y. Srinivasan (8):
Drivers: scsi: storvsc: Change the limits to reflect the values on
the host
Drivers: scsi: storvsc: Set
On 10 July 2014 10:47, Olof Johansson wrote:
>> I didn't sign-off because I haven't even looked closed at many of the
>> patches around PCI and Acked whatever I could understand.
>
> Thanks, good to know that the series hasn't been fully reviewed. That
> makes me even more hesitant to apply it at
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2
The usb device will autoresume from choose_wakeup() if it is
autosuspended with the wrong wakeup setting, but below errors occur
because usb3503 misc driver will switch to standby mode when suspended.
As add USB_QUIRK_RESET_RESUME, it can stop setting wrong wakeup from
autosuspend_check().
[
Greetings,
I am a Financial Consultant with the Capital One United State
I am in control of privately owned funds placed for long term investments.
Our interest is to fund projects in form of Loan. Viable projects ranging from
any amount would be funded at a guaranteed 3% Fixed
Interest Rate
> On Thu, Jul 10, 2014 at 12:26 AM, Frank Filz
> wrote:
> >> On Wed, Jul 9, 2014 at 7:06 PM, Trond Myklebust
> >> wrote:
> >> > On Wed, Jul 9, 2014 at 6:42 PM, Frank Filz
> >> >
> >> wrote:
> >> >>> On Wed, Jul 9, 2014 at 5:54 PM, Frank S. Filz
> >> >>>
> >> >>> wrote:
> >> >>> > From: "Frank
On Wed, Jul 9, 2014 at 5:18 PM, Viresh Kumar wrote:
> On 9 July 2014 23:39, Olof Johansson wrote:
>> * Why are you sending a pull request for a repo that is not yours?
>
> Because Mohit/Pratyush were facing some issues in pushing patches
> to the SPEAr public git repo. And so I tried to help
On 07/10/2014 02:05 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
>> Hi Joonyoung,
>>
>> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim
>> wrote:
>>> This fixes below build warning.
>>>
>>> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
> Hi Joonyoung,
>
> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim
> wrote:
> > This fixes below build warning.
> >
> > drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
> > drivers/usb/misc/usb3503.c:195:11: warning: ‘err’
Hi Joonyoung,
On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim wrote:
> This fixes below build warning.
>
> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
> drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ may be used uninitialized
> in this function [-Wmaybe-uninitialized]
>
Alexey Dobriyan writes:
> [broken email]
>
> On Wed, Jul 9, 2014 at 3:17 PM, Alexey Dobriyan wrote:
>>> I originally posted this two years ago (*) but received no response.
>>> I just had a look and the problem still exists on the 3.14 kernel
>>> I am currently running.
>>>
>>> I *think* I've
We assume that modification of some special application could result in zeroed
name_len, or it is consciously made by somebody. We will deadloop in
find_in_block when name_len of dir entry is zero.
This patch is added for preventing deadloop in above scenario.
change log from v1:
o use
On Thu, Jul 10, 2014 at 12:26:07PM +0800, WANG Chao wrote:
> Currently map_vm_area() takes (struct page *** pages) as third argument,
> and after mapping, it moves (*pages) to point to (*pages + nr_mappped_pages).
>
> It looks like this kind of increment is useless to its caller these
> days. The
Will,
> (1) Updating syscallno based on w8, but this ties us to the current ABI
> and could get messy if this register changes in the future.
So, is this the conclusion that I should follow?
-Takahiro AKASHI
On 07/09/2014 01:12 PM, Will Deacon wrote:
Hi Akashi,
On Fri, Jul 04, 2014
On Thu, Jul 10, 2014 at 12:26 AM, Frank Filz wrote:
>> On Wed, Jul 9, 2014 at 7:06 PM, Trond Myklebust
>> wrote:
>> > On Wed, Jul 9, 2014 at 6:42 PM, Frank Filz
>> wrote:
>> >>> On Wed, Jul 9, 2014 at 5:54 PM, Frank S. Filz
>> >>>
>> >>> wrote:
>> >>> > From: "Frank S. Filz"
>> >>> >
>> >>> >
Currently map_vm_area() takes (struct page *** pages) as third argument,
and after mapping, it moves (*pages) to point to (*pages + nr_mappped_pages).
It looks like this kind of increment is useless to its caller these
days. The callers don't care about the increments and actually they're
trying
> On Wed, Jul 9, 2014 at 7:06 PM, Trond Myklebust
> wrote:
> > On Wed, Jul 9, 2014 at 6:42 PM, Frank Filz
> wrote:
> >>> On Wed, Jul 9, 2014 at 5:54 PM, Frank S. Filz
> >>>
> >>> wrote:
> >>> > From: "Frank S. Filz"
> >>> >
> >>> > The NFS v4 client sends a COMPOUND with an OPEN and an ACCESS.
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2
This fixes below build warning.
drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
dev_err(dev, "unable to request refclk (%d)\n", err);
^
Signed-off-by:
Hello,
This patchset is simple just to fix and support PM for usb3503. They was
tested on odroid U3 board.
Thanks.
Joonyoung Shim (3):
usb: usb3503: fix build warning
usb: usb3503: add PM functions
USB: add reset resume quirk for usb3503
drivers/usb/core/quirks.c | 3 +++
The usb device will autoresume from choose_wakeup() if it is
autosuspended with the wrong wakeup setting, but below errors occur
because usb3503 misc driver will switch to standby mode when suspended.
As add USB_QUIRK_RESET_RESUME, it can stop setting wrong wakeup from
autosuspend_check().
[
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Wednesday, July 09, 2014 9:48 PM
> To: Chao Yu
> Cc: 'Changman Lee'; linux-f2fs-de...@lists.sourceforge.net;
> linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re:
On Wed, Jul 9, 2014 at 8:30 AM, Chanwoo Choi wrote:
> On 07/01/2014 09:33 AM, Chanwoo Choi wrote:
>> This patch add registers, bit fields and compatible strings for Exynos3250
>> TMU
>> (Thermal Management Unit). Exynos3250 uses the Cortex-A7 dual cores and has
>> a target speed of 1.0 GHz.
>>
This patch focuses on clock setting for RK3288 mmc controller.
In RK3288 mmc controller, CLKDIV register can only be set 0 or 1,
and if DDR 8bit mode, CLKDIV register must be set 1.
Signed-off-by: Addy Ke
---
changes since v1:
- dw_mci_rk3288_setup_clock: do not call clk_get_rate(), just use
Null checks for tty, un and ch are already done by caller,
so replace parameter "tty" with "ch" and "un".
Signed-off-by: Daeseok Youn
---
V2: revert return type from int to void.
leave it originally.
drivers/staging/dgap/dgap.c | 21 -
1 files changed, 4 insertions(+), 17
Adding MFD maintainers
On Tue, Jul 8, 2014 at 5:58 PM, Amit Daniel Kachhap
wrote:
> This patch makes the regulator description macro take minimum and
> steps voltage as parameter. In this way many repeated macros can be
> removed. Now these macros are repeated only if the the LDO/BUCK ctrl
>
Adding MFD maintainers.
On Tue, Jul 8, 2014 at 5:57 PM, Amit Daniel Kachhap
wrote:
> This patch makes the regulator description macro take minimum and
> steps voltage as parameter. In this way many repeated macros can be
> removed. Now these macros are repeated only if the the LDO/BUCK ctrl
>
On Wed, Jul 9, 2014 at 2:55 PM, Mark Brown wrote:
> On Tue, Jul 08, 2014 at 05:57:58PM +0530, Amit Daniel Kachhap wrote:
>
>> include/linux/mfd/samsung/core.h| 21
>> include/linux/mfd/samsung/s2mpa01.h | 12 -
>> include/linux/mfd/samsung/s2mps11.h | 9 ---
>>
Dear RT Folks,
I'm pleased to announce the 3.4.97-rt120 stable release.
This release is just an update to the new stable 3.4.97 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.10.47-rt49 stable release.
This release is just an update to the new stable 3.10.47 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.12.24-rt37 stable release.
This release is just an update to the new stable 3.12.24 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Thu, Jul 10, 2014 at 10:27:00AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Fri, 20 Jun 2014 09:53:53 -0700 Greg KH wrote:
> >
> > On Fri, Jun 20, 2014 at 02:18:07PM +1000, Stephen Rothwell wrote:
> > > Hi Greg,
> > >
> > > After merging the staging tree, today's linux-next build
The maximum jumbo frame size for RTL8153 is 9K bytes.
Change the max rx packet size to 9K.
Change the use of the shared fifo from 6K (default) to 12K for tx.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 36
1 file changed, 32 insertions(+), 4
The smsc95xx needs to resume with reset operation. Otherwise it causes
system hang by network error like below after resume. This case appears
on odroid u3 board.
[9.727600] smsc95xx 1-2:1.0 eth0: kevent 2 may have been dropped
[9.727648] smsc95xx 1-2:1.0 eth0: kevent 2 may have been
On Wed, Jul 09, 2014 at 10:08:42AM -0700, bseg...@google.com wrote:
> > That I believe is not a problem. It is a matter of when cfs_rq->load.weight
> > changes and when we look at it to contribute to the cfs_rq's load_avg.
> > Fortunately, we will not miss any change of cfs_rq->load.weight,
Preliminary patch. Not tested. Just sending out to give an idea of what I'm
looking to do. Expect a lot more simplification when it's done.
Benefits:
* A lot more simpler code.
* Less stability issues.
* Suspend/resume time would improve.
* Hotplug time would improve.
* Sysfs file permissions
The issue of boundary checking on bitmaps is introduced by this commit
in below.
commit 4d852ef8c2544ce21ae41414099a7504c61164a0
Author: Andreas Herrmann
Date: Tue Feb 25 13:09:53 2014 +0100
arm: dma-mapping: Add support to extend DMA IOMMU mappings
Multiple bitmaps were introduced as
On Thursday, July 10, 2014 7:08 AM, Rickard Strandqvist wrote:
> 2014-07-09 18:30 GMT+02:00 Lee Jones :
> > On Mon, 07 Jul 2014, Rickard Strandqvist wrote:
> >
> >> Variable ar assigned a value that is never used.
> >> I have also removed all the code that thereby serves no purpose,
> >> and made
On 2014/7/9 20:45, Rafael J. Wysocki wrote:
> On Tuesday, July 08, 2014 05:54:35 PM Dmitry Torokhov wrote:
>> On Wed, Jul 09, 2014 at 02:59:33AM +0200, Rafael J. Wysocki wrote:
>>> On Tuesday, July 08, 2014 05:15:06 PM Dmitry Torokhov wrote:
On Wed, Jul 09, 2014 at 01:06:07AM +0200, Rafael J.
Hi Boris,
On 07/10/2014 12:34 AM, Boris BREZILLON wrote:
Hello Bo,
I know you're quite busy, but if you have some time could you test this
series on both CPU Modules (Embest and Ronetix): I only own the Embest
one.
Best Regards,
Boris
On Thu, 26 Jun 2014 12:13:33 +0200
Boris BREZILLON
On Thu, Jul 10, 2014 at 06:56:39AM +0530, navin patidar wrote:
> On Thu, Jul 10, 2014 at 6:29 AM, Greg KH wrote:
> > On Thu, Jul 10, 2014 at 06:24:21AM +0530, navin patidar wrote:
> >> On Thu, Jul 10, 2014 at 12:34 AM, Greg KH
> >> wrote:
> >> > On Tue, Jul 01, 2014 at 10:35:09PM +0530, navin
On Wed, Jul 09, 2014 at 11:30:41PM +0200, Thomas Gleixner wrote:
> On Wed, 9 Jul 2014, Viresh Kumar wrote:
>
> So your patch series drops active hrtimer checks after adding it,
> according to your subject line.
>
> Quite useeul to drop something after adding it, right?
>
> > hrtimer_start*()
On 2014/7/9 19:45, vaughan wrote:
On 07/09/2014 07:32 PM, Manish Chopra wrote:
-Original Message-
From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
On Behalf Of ethan zhao
Sent: Wednesday, July 09, 2014 8:11 AM
To: David Miller
Cc: ba...@ti.com; netdev;
On Thu, Jul 10, 2014 at 6:29 AM, Greg KH wrote:
> On Thu, Jul 10, 2014 at 06:24:21AM +0530, navin patidar wrote:
>> On Thu, Jul 10, 2014 at 12:34 AM, Greg KH wrote:
>> > On Tue, Jul 01, 2014 at 10:35:09PM +0530, navin patidar wrote:
>> >> Remove WEXT_PRIV (non-standard) ioctl handlers.
>> >>
>>
Sam Ravnborg writes:
> On Wed, Jul 09, 2014 at 11:41:48AM +0200, Rasmus Villemoes wrote:
>> For several years, the pattern "foo$" has effectively been treated as
>> equivalent to "foo" due to a bug in the (misnamed) helper
>> number_prefix(). This hasn't been observed to cause any problems, so
>>
Since the struct hc_driver is mostly the same across the xhci-pci,
xhci-plat, and the upcoming xhci-tegra driver, introduce the function
xhci_init_driver() which will populate the hc_driver with the default
xHCI operations. The caller must supply a setup function which will
be used as the
In preparation for allowing the xHCI host controller drivers to be built
as separate modules, export symbols from the xHCI core that may be used
by the host controller drivers.
Signed-off-by: Andrew Bresticker
---
drivers/usb/host/xhci-dbg.c | 1 +
drivers/usb/host/xhci.c | 3 +++
2 files
On Wed, 9 Jul 2014, Hugh Dickins wrote:
> On Wed, 9 Jul 2014, Vlastimil Babka wrote:
> > On 07/09/2014 06:03 PM, Sasha Levin wrote:
> > >
> > > We can see that it's not blocked since it's in the middle of a spinlock
> > > unlock
> > > call, and we can guess it's been in that function for a while
Instead of building all of the xHCI code into a single module, separate
it out into the core (xhci-hcd), PCI (xhci-pci, now selected by the new
config option CONFIG_USB_XHCI_PCI), and platform (xhci-plat) drivers.
Also update the PCI/platform drivers with module descriptions/licenses
and have them
Instead of calling xhci_compliance_mode_recovery_timer_quirk_check() again
in the PCI suspend path, just check for XHCI_COMP_MODE_QUIRK which will
have been set based on xhci_compliance_mode_recovery_timer_quirk_check()
in xhci_init().
Signed-off-by: Andrew Bresticker
---
It was suggested in the review of the Tegra xHCI driver [1] that we
allow xHCI drivers to be built as individual modules (like EHCI) instead
of building them all into the single xhci-hcd module as they are today.
Patches 1-3 prepare for making the xHCI PCI and platform drivers able
to be built as
On Thu, Jul 10, 2014 at 06:24:21AM +0530, navin patidar wrote:
> On Thu, Jul 10, 2014 at 12:34 AM, Greg KH wrote:
> > On Tue, Jul 01, 2014 at 10:35:09PM +0530, navin patidar wrote:
> >> Remove WEXT_PRIV (non-standard) ioctl handlers.
> >>
> >> Signed-off-by: navin patidar
> >> ---
> >>
> -Original Message-
> From: Jens Axboe [mailto:ax...@kernel.dk]
> Sent: Wednesday, 09 July, 2014 2:38 PM
> To: dgilb...@interlog.com; Christoph Hellwig; James Bottomley; Bart Van
> Assche; Elliott, Robert (Server Storage); linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
>
On 7/8/2014 5:38 PM, H. Peter Anvin wrote:
> On 07/08/2014 03:34 PM, Stuart Hayes wrote:
>>
>> I haven't received any responses... is there a problem with the patch? Also
>> CCing a couple people.
>>
>
> I was on vacation last week and am still catching up.
>
> It would also help if you
On Thu, Jul 10, 2014 at 12:34 AM, Greg KH wrote:
> On Tue, Jul 01, 2014 at 10:35:09PM +0530, navin patidar wrote:
>> Remove WEXT_PRIV (non-standard) ioctl handlers.
>>
>> Signed-off-by: navin patidar
>> ---
>> drivers/staging/rtl8188eu/os_dep/ioctl_linux.c | 6335
>> +++-
>>
On Wed, 9 Jul 2014, Hugh Dickins wrote:
> On Wed, 9 Jul 2014, Johannes Weiner wrote:
> > On Thu, Jun 26, 2014 at 10:36:20PM -0700, Hugh Dickins wrote:
> > > Hannes, a question for you please, I just could not make up my mind.
> > > In mm/truncate.c truncate_inode_pages_range(), what should be done
On Thu, May 29, 2014 at 02:24:00PM -0700, Sudeep Dutt wrote:
> From: Siva Yerramreddy
>
> This patch implements DMA Engine API for DMA controller on MIC X100
> Coprocessors. DMA h/w is shared between host and card s/w.
> Channels 0 to 3 are used by host and 4 to 7 are used by card.
> Since the
On Thu, May 29, 2014 at 02:23:59PM -0700, Sudeep Dutt wrote:
> +/**
> + * mbus_device - representation of a device using mbus
> + * @priv: private pointer for the driver's use.
> + * @mmio_va: virtual address of mmio space
> + * @hw_ops: the hardware ops supported by this device.
> + * @id: the
On Fri, Jul 04, 2014 at 12:35:57PM +0530, Vineet Gupta wrote:
> Hi Greg,
>
> On Wednesday 25 June 2014 02:35 AM, Rob Herring wrote:
> > On Tue, Jun 24, 2014 at 3:25 AM, Vineet Gupta
> > wrote:
> >> Hi,
> >>
> >> This is slightly modified repost of series posted last week
> >>
On Fri, Jun 27, 2014 at 10:32:10PM +0200, Fabian Frederick wrote:
> null test before debugfs_remove_recursive is not needed so one line function
> dma_buf_uninit_debugfs can be removed.
>
> This patch calls debugfs_remove_recursive under CONFIG_DEBUG_FS
>
> Cc: Sumit Semwal
> Cc: Greg
Hi Greg,
On Fri, 20 Jun 2014 09:53:53 -0700 Greg KH wrote:
>
> On Fri, Jun 20, 2014 at 02:18:07PM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > After merging the staging tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > drivers/staging/board/board.c: In
On Fri, May 30, 2014 at 03:16:22PM +0900, Yoshihiro YUNOMAE wrote:
> Add tunable RX interrupt trigger I/F of FIFO buffers.
>
> Serial devices are used as not only message communication devices but control
> or sending communication devices. For the latter uses, normally small data
> will be
On Sun, Jun 8, 2014 at 6:37 PM, wrote:
> From: Fan Wu
[...]
> diff --git a/drivers/pinctrl/pinctrl-msm.c b/drivers/pinctrl/pinctrl-msm.c
> index df6dda4c..bdfaba4 100644
> --- a/drivers/pinctrl/pinctrl-msm.c
> +++ b/drivers/pinctrl/pinctrl-msm.c
> @@ -165,36 +165,11 @@ static int
On 9 July 2014 23:39, Olof Johansson wrote:
> * Why are you sending a pull request for a repo that is not yours?
Because Mohit/Pratyush were facing some issues in pushing patches
to the SPEAr public git repo. And so I tried to help them out publicly
and nobody objected then:
Hi Himangi,
(2014/07/09 7:21), Himangi Saraogi wrote:
Use BUG_ON(x) rather than if(x) BUG();
The semantic patch that fixes this problem is as follows:
//
@@ identifier x; @@
-if (x) BUG();
+BUG_ON(x);
//
Strictly speaking, BUG_ON() is "if (unlikely(x)) BUG".
Anyway, I consider that put
The mm-of-the-moment snapshot 2014-07-09-17-08 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
> I guess the other alternative is curl.. could u check for this one as well?
I looked at this earlier, but it made a complete mess of the download
script to handle both. So right now I stayed with wget only.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
> what happens if we fail to realloc?
Then the field doesn't get added. No problem.
-Andi
--
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
On Thu, Jul 10, 2014 at 12:19:58AM +0200, Jiri Olsa wrote:
> Im confused, your branch shows v4 in patch Subject,
> while this patch has v3... ?
Patchkits and patches both have their own numeric
version spaces.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, Jun 25, 2014 at 06:30:37PM +0100, Sudeep Holla wrote:
> +static const struct device_attribute *cache_optional_attrs[] = {
> + _attr_coherency_line_size,
> + _attr_ways_of_associativity,
> + _attr_number_of_sets,
> + _attr_size,
> + _attr_attributes,
> +
> FWIW, I definitely agree with this -- if KASAN can do everything that
> kmemcheck can, it is no doubt the right way forward.
Thanks
BTW I didn't want to sound like I'm against kmemcheck. It is a very
useful tool and was impressive work given the constraints (no help from
the compiler)
-andi
On Thu, 10 Jul 2014, Frederic Weisbecker wrote:
> On Wed, Jul 09, 2014 at 12:25:33PM +0530, Viresh Kumar wrote:
> > hrtimer_start*() family never fails to enqueue a hrtimer to a clock-base.
> > The
> > only special case is when the hrtimer was in past. If it is getting
> > enqueued to
> > local
Signed-off-by: Steven Stewart-Gallus
---
man2/access.2| 14 +-
man2/chmod.2 | 14 +-
man2/chown.2 | 14 +-
man2/fanotify_mark.2 | 15 ++-
man2/futimesat.2 | 14 +-
man2/link.2
On Sun, Jun 08, 2014 at 11:51:43PM +0100, Ben Hutchings wrote:
> snprintf() returns the number of bytes that could have been written
> (excluding the null), not the actual number of bytes written. Given a
> long enough subsystem or device name, these functions will advance
> beyond the end of the
From: Richard Weinberger
Date: Wed, 9 Jul 2014 16:23:59 +0200
> In order to have at least a netconsole to debug kernel issues on
> Windows Azure this patch implements netpoll support.
> Sending packets is easy, netvsc_start_xmit() does already everything
> needed.
>
> Signed-off-by: Richard
From: Grygorii Strashko
Date: Wed, 9 Jul 2014 16:10:50 +0300
> Required properties:
> -- compatible : Should be "ti,davinci_mdio"
> +- compatible : Should be "ti,davinci_mdio" or "ti,keystone-mdio"
Why the inconsistency in naming schemes? I don't see any reason
to be different
This way people can use existing functionality (passing an invalid value
for dirfd to allow only absolute paths in *at style functions) and be
compatible for the future if Linux ever adds in new AT_* flags.
Signed-off-by: Steven Stewart-Gallus
---
include/uapi/linux/fcntl.h | 11 +--
From: Hayes Wang
Date: Wed, 9 Jul 2014 16:07:02 +0800
> +static int rtl8152_change_mtu(struct net_device *dev, int new_mtu)
> +{
> + struct r8152 *tp = netdev_priv(dev);
> +
> + if (dev->mtu == new_mtu)
> + return 0;
This method will never be invoked if the MTU is actually
From: Mugunthan V N
Date: Wed, 9 Jul 2014 12:44:07 +0530
> A system/cpu can be loaded by a hacker with flooding of broadcast or
> multicast packets, to prevent this some Ethernet controllers like CPSW
> provide a mechanism to limit the broadcast/multicast packet rate via
> hardware limiters.
Thank you for the criticisms Christopher Hellwig.
I will edit the commit message to be better and comments in the code
to be clearer. I will also document the constant in the manpages. I
think I will call the constant AT_FDABSOLUTE though because I want it
to be prepended with FD the same way
Future patch will potentially call this twice, so make it
separate.
Signed-off-by: NeilBrown
---
fs/autofs4/expire.c | 153 ++-
1 file changed, 79 insertions(+), 74 deletions(-)
diff --git a/fs/autofs4/expire.c b/fs/autofs4/expire.c
index
From: Francois Romieu
Date: Thu, 10 Jul 2014 00:09:54 +0200
> Hayes Wang :
>> For RTL8411, RTL8111G, RTL8402, RTL8105, and RTL8106, disable the feature
>> of entering the L2/L3 link state of the PCIe. When the nic starts the process
>> of entering the L2/L3 link state and the PCI reset occurs
Any attempt to look up a pathname that passes though an
autofs4 mount is currently forced out of RCU-walk into
REF-walk.
This can significantly hurt performance of many-thread work
loads on many-core systems, especially if the automounted
filesystem supports RCU-walk but doesn't get to benefit
->fs_lock protects AUTOFS_INF_EXPIRING. We need to be sure
that once the flag is set, no new references beneath the dentry
are taken. So rcu-walk currently needs to take fs_lock before
checking the flag. This hurts performance.
Change the expiry to a two-stage process.
First set
The variable 'ino' already exists and already
has the correct value. The d_fsdata of a dentry
is never changed after the d_fsdata is instantiated,
so this new assignment cannot be necessary.
It was introduced in
commit b5b801779d59165c4ecf1009009109545bd1f642
autofs4: Add d_manage() dentry
If the expiring_list is empty, we can avoid a costly spinlock
in the rcu-walk path through authfs4_d_manage.
Signed-off-by: NeilBrown
---
fs/autofs4/root.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/autofs4/root.c b/fs/autofs4/root.c
index 1ad119407e2f..774c2dab331b 100644
---
autofs4 currently doesn't support RCU-walk - it immediately
aborts any attempt at RCU-walk to force REF-walk for path name
lookup.
This can cause a significant performance impact on multi-core
systems.
I have a client with a test case which spends >80% of its time
waiting for spinlocks with a
1 - 100 of 2152 matches
Mail list logo
