regulator_get_voltage() may return negative error code.
Don't set error code to to pos_voltage_uv and neg_voltage_uv.
Signed-off-by: Axel Lin
---
drivers/iio/dac/ad5791.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/dac/ad5791.c
On 12/14/2012 03:45 PM, Mike Galbraith wrote:
> On Fri, 2012-12-14 at 14:36 +0800, Alex Shi wrote:
>> On 12/14/2012 12:45 PM, Mike Galbraith wrote:
> Do you have further ideas for buddy cpu on such example?
>>>
>>> Which kind of sched_domain configuration have you for such system ?
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to voltage_uv.
Signed-off-by: Axel Lin
---
drivers/iio/dac/ad5686.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/dac/ad5686.c
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to voltage_uv.
Signed-off-by: Axel Lin
---
drivers/iio/dac/ad5624r_spi.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/dac/ad5624r_spi.c
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to voltage_uv.
Signed-off-by: Axel Lin
---
drivers/iio/dac/ad5504.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/dac/ad5504.c
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to st->vref_uv.
Signed-off-by: Axel Lin
---
drivers/iio/dac/ad5380.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/dac/ad5380.c
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to st->vref_uv.
Signed-off-by: Axel Lin
---
drivers/iio/adc/ad7266.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/adc/ad7266.c
On Fri, 2012-12-14 at 14:36 +0800, Alex Shi wrote:
> On 12/14/2012 12:45 PM, Mike Galbraith wrote:
> >> > Do you have further ideas for buddy cpu on such example?
> >>> > >
> >>> > > Which kind of sched_domain configuration have you for such system ?
> >>> > > and how many sched_domain level
Hi all,
Changes since 20121213:
Lots of conflicts are migrating between trees.
The powerpc tree lost its build failure.
The xtensa tree gained a conflict against Linus' tree.
The akpm tree lost lots of commits that turned up elsewhere and lost its
build failure
On 12/14/2012 04:34 PM, Thierry Reding wrote:
On Fri, Dec 14, 2012 at 03:58:58PM +0900, Joonyoung Shim wrote:
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
I've modified the subject a bit to make it clear the assignment of
s3c->pwm_id was
On 2012-12-14 03:26, Jack Wang wrote:
> 2012/12/14 Jens Axboe :
>> On Mon, Dec 03 2012, Kent Overstreet wrote:
>>> Last posting: http://thread.gmane.org/gmane.linux.kernel.aio.general/3169
>>>
>>> Changes since the last posting should all be noted in the individual
>>> patch descriptions.
>>>
>>>
On Fri, Dec 14, 2012 at 03:58:58PM +0900, Joonyoung Shim wrote:
> The s3c->pwm_id is used to calculate offset of related register.
>
> Signed-off-by: Joonyoung Shim
I've modified the subject a bit to make it clear the assignment of
s3c->pwm_id was missing, not the s3c->pwm_id field altogether.
On Thu, Dec 13, 2012 at 09:49:43PM -0800, Andy Lutomirski wrote:
> This is a serious cause of mmap_sem contention. MAP_POPULATE
> and MCL_FUTURE, in particular, are disastrous in multithreaded programs.
>
> Signed-off-by: Andy Lutomirski
> ---
>
> Sensible people use anonymous mappings. I
In v3.3, the gma500 drm driver moved from staging to drm group by
Alan Cox's 3abcf41fb patch. the gma500 drm driver should control
brightness well and don't need gma500 stub driver anymore.
Reference:
http://lists.freedesktop.org/archives/dri-devel/2012-May/023426.html
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
making use of information passed through DT for achieving this.
Signed-off-by: Venu Byravarasu
---
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
added a new property to USB DT node for this purpose.
Modified host driver to make use of the information passed
through DT to
As Tegra USB host driver is using instance number for resetting
PORT0 twice, adding a new DT property for handling this.
Signed-off-by: Venu Byravarasu
---
.../bindings/usb/nvidia,tegra20-ehci.txt |2 ++
arch/arm/boot/dts/tegra20.dtsi |1 +
2 files changed,
On Tue, 2012-12-11 at 10:08 -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 11, 2012 at 04:12:52PM +0800, Huang Ying wrote:
[snip]
> > Which tree should I base the patch on?
>
> 3.6.10 would be great.
Here is the patch for 3.6.10.
On Mon, 10 Sep 2012 10:57:07 -0700 Kevin Hilman
wrote:
> OK thanks, I'll queue this up for v3.6-rc as this should qualify as a
> regression.
I don't think this did actually get queued. At least I'm still seeing the
bug in 3.7 and I cannot see a patch in the git history that looks right.
But
On Fri, Dec 14, 2012 at 1:34 AM, Andrew Morton
wrote:
> On Mon, 10 Dec 2012 13:37:44 +0200
> Andy Shevchenko wrote:
>
>> We get a warning if CONFIG_DMA_API_DEBUG=y
>>
>> [ 28.150631] WARNING: at lib/dma-debug.c:933 check_unmap+0x5d6/0x6ac()
>> [ 28.157058] dw_dmac dw_dmac.0: DMA-API: device
On Fri, Dec 14, 2012 at 2:56 PM, Jason Gao wrote:
> On Fri, Dec 14, 2012 at 12:45 PM, Alex Williamson
> wrote:
>> Is the MegaRAID firmware and system management firmware the same as
>> well? Thanks.
>
> I'v updated all the firmware using Dell's firmware-tools:
>
> # inventory_firmware
> Wait
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
---
Changelog from v1:
- move the assignment code to below.
drivers/pwm/pwm-samsung.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
On Fri, Dec 14, 2012 at 12:45 PM, Alex Williamson
wrote:
> Is the MegaRAID firmware and system management firmware the same as
> well? Thanks.
I'v updated all the firmware using Dell's firmware-tools:
# inventory_firmware
Wait while we inventory system:
System inventory:
BIOS = 6.3.0
On Fri, Dec 14, 2012 at 01:20:09PM +0900, Joonyoung Shim wrote:
> The s3c->pwm_id is used to calculate offset of related register.
>
> Signed-off-by: Joonyoung Shim
> ---
> drivers/pwm/pwm-samsung.c |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pwm/pwm-samsung.c
Remove wrong "shift" for --keep-case. There is always "shift" at
beginning of while-loop. No need "shift" at --keep-case just before
"continue" to process next argument.
Now the following works as expected:
./scripts/config -e aAa -k -e bBb -e cCc && tail -3 .config
CONFIG_AAA=y
CONFIG_bBb=y
2012-12-14 (금), 14:41 +0900, Namjae Jeon:
> 2012/12/14, Jaegeuk Kim :
> > Hi,
> >
> >> diff --git a/fs/f2fs/hash.c b/fs/f2fs/hash.c
> >> index a60f042..5e48bac 100644
> >> --- a/fs/f2fs/hash.c
> >> +++ b/fs/f2fs/hash.c
> >> @@ -76,6 +76,10 @@ f2fs_hash_t f2fs_dentry_hash(const char *name, int
> >>
On 12/14/2012 12:45 PM, Mike Galbraith wrote:
>> > Do you have further ideas for buddy cpu on such example?
>>> > >
>>> > > Which kind of sched_domain configuration have you for such system ?
>>> > > and how many sched_domain level have you ?
>> >
>> > it is general X86 domain configuration.
On Fri, Dec 14, 2012 at 12:49 AM, Alan Stern wrote:
> On Thu, 13 Dec 2012, prasannatsmkumar wrote:
>
>> On Thu, Dec 13, 2012 at 11:40 PM, Alan Stern
>> wrote:
>> > On Thu, 13 Dec 2012, prasannatsmkumar wrote:
>> >
>> >> On Wed, Dec 12, 2012 at 2:07 AM, Alan Stern
>> >> wrote:
>> >> > STOP
On 13.12.2012 19:58, Stephen Warren wrote:
> On 12/13/2012 01:57 AM, Thierry Reding wrote:
>> After some more discussion with Stephen on IRC we came to the
>> conclusion that the easiest might be to have tegra-drm call into
>> host1x with something like:
>>
>> void host1x_set_drm_device(struct
The arbitrator is a general purpose function which uses two GPIOs to
communicate with another device to claim/release a bus.
i2c_transfer()
if adapter->gpio_arbit
i2c_bus_claim();
__i2c_transfer();
i2c_bus_release();
Signed-off-by:
Makes use of the generic fucntions in of_i2c.c to parse arbitration
timing information and GPIOs for arbitration.
Also uses devm_gpio_request() instead of gpio_request() and
removes the gpio_free() calls
Signed-off-by: Naveen Krishna Chatradhi
---
drivers/i2c/busses/i2c-s3c2410.c | 79
This patchset adds
1. Support for generic gpio based i2c bus arbitration between 2 i2c Masters
Ex: between AP(exynos), device(EC).
2. Documentation and sample implmentation in i2c-s3c2410 driver.
Naveen Krishna Chatradhi (2):
i2c-core: Add gpio based bus arbitration implementation
From: Magnus Damm
Add a comment about different register layouts
supported by the CMT driver.
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c | 15 +++
1 file changed, 15 insertions(+)
--- 0005/drivers/clocksource/sh_cmt.c
+++ work/drivers/clocksource/sh_cmt.c
This is a serious cause of mmap_sem contention. MAP_POPULATE
and MCL_FUTURE, in particular, are disastrous in multithreaded programs.
Signed-off-by: Andy Lutomirski
---
Sensible people use anonymous mappings. I write kernel patches :)
I'm not entirely thrilled by the aesthetics of this
From: Magnus Damm
Introduce sh_cmt_read_cmstr/cmcsr/cmcnt() and
sh_cmt_write_cmstr/cmcsr/cmcnt/cmcor() to in the
future allow us to split counter registers from
control registers and reduce code complexity by
removing sh_cmt_read() and sh_cmt_write().
Signed-off-by: Magnus Damm
---
From: Magnus Damm
Update hardware register access code for CMSTR and CMCSR
from using sh_cmt_read() and sh_cmt_write() to make use
of 16-bit register access functions such as sh_cmt_read16()
and sh_cmt_write16(). Also update sh_cmt_read() and
sh_cmt_write() now when the special cases are gone.
From: Magnus Damm
Break out the CMCNT and CMCOR register access code
into separate 16-bit and 32-bit functions that are
hooked into callbacks at init time. This reduces
the amount of software calculations happening at
runtime.
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c |
From: Magnus Damm
This patch adds control register callbacks for the CMT
driver. At this point only 16-bit access is supported
but in the future this will be updated to allow 32-bit
access as well.
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c | 16
1 file
From: Magnus Damm
Cleanup the use of platform_set_drvdata() to reduce code size
Signed-off-by: Shinya Kuribayashi
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- 0003/drivers/clocksource/sh_cmt.c
+++
From: Magnus Damm
Move the setup of spinlock and max_match_value to sh_cmt_setup().
There's no need to defer those steps until sh_cmt_register().
Signed-off-by: Shinya Kuribayashi
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c | 16
1 file changed, 8
clocksource: sh_cmt: CMT driver update
[PATCH 01/08] clocksource: sh_cmt: Take care of clk_put() when setup_irq() fails
[PATCH 02/08] clocksource: sh_cmt: Initialize 'max_match_value' and 'lock' in
sh_cmt_setup()
[PATCH 03/08] clocksource: sh_cmt: Consolidate platform_set_drvdata() call
[PATCH
From: Magnus Damm
Make sure clk_put() is called in case of failure in sh_cmt_setup().
Signed-off-by: Shinya Kuribayashi
Signed-off-by: Magnus Damm
---
drivers/clocksource/sh_cmt.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
--- 0001/drivers/clocksource/sh_cmt.c
+++
On 3.7.0 + irrelevant patches, I get this on boot. I've seen it on
and off on earlier kernels, I think (although I'm not currently
getting it on 3.5).
[ 10.230054] PERCPU: allocation failed, size=304 align=32, alloc
from reserved chunk failed
[ 10.230059] Pid: 1026, comm: modprobe Tainted: G
2012/12/14, Jaegeuk Kim :
> Hi,
>
>> diff --git a/fs/f2fs/hash.c b/fs/f2fs/hash.c
>> index a60f042..5e48bac 100644
>> --- a/fs/f2fs/hash.c
>> +++ b/fs/f2fs/hash.c
>> @@ -76,6 +76,10 @@ f2fs_hash_t f2fs_dentry_hash(const char *name, int
>> len)
>> const char *p;
>> __u32 in[8], buf[4];
>>
On Thu, Dec 13, 2012 at 8:11 PM, Eric W. Biederman
wrote:
> Andy Lutomirski writes:
>
>> One more issue: the requirement that both upper and lower uids (etc.)
>> in the maps are in order is rather limiting. I have no objection if
>> you only require upper ids to be monotonic, but currently
Hi,
> diff --git a/fs/f2fs/hash.c b/fs/f2fs/hash.c
> index a60f042..5e48bac 100644
> --- a/fs/f2fs/hash.c
> +++ b/fs/f2fs/hash.c
> @@ -76,6 +76,10 @@ f2fs_hash_t f2fs_dentry_hash(const char *name, int len)
> const char *p;
> __u32 in[8], buf[4];
>
> + if ((len <= 2) && (name[0]
On Thu, Dec 13, 2012 at 10:25:43PM +, Satoru Moriya wrote:
>
> On 12/13/2012 11:05 AM, Michal Hocko wrote:> On Thu 13-12-12 16:29:59, Michal
> Hocko wrote:
> >> On Thu 13-12-12 10:34:20, Mel Gorman wrote:
> >>> On Wed, Dec 12, 2012 at 04:43:34PM -0500, Johannes Weiner wrote:
> When a
On 12/14/2012 06:54 AM, Marcelo Tosatti wrote:
> On Thu, Dec 13, 2012 at 04:05:55AM +0800, Xiao Guangrong wrote:
>> On 12/12/2012 07:36 AM, Marcelo Tosatti wrote:
>>> On Mon, Dec 10, 2012 at 05:11:35PM +0800, Xiao Guangrong wrote:
Changelog:
There are some changes from Marcelo and Gleb's
On Fri, 2012-12-14 at 10:01 +0800, Jason Gao wrote:
> On Fri, Dec 14, 2012 at 12:23 AM, Alex Williamson
> wrote:
> >
> > Device 03:00.0 is your raid controller:
> >
> > 03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078
> > (rev 04)
> >
> > For some reason it's trying to
On Thu, 2012-12-13 at 22:25 +0800, Alex Shi wrote:
> On 12/13/2012 06:11 PM, Vincent Guittot wrote:
> > On 13 December 2012 03:17, Alex Shi wrote:
> >> On 12/12/2012 09:31 PM, Vincent Guittot wrote:
> >>> During the creation of sched_domain, we define a pack buddy CPU for each
> >>> CPU
> >>>
The logging style in this file is "baroque".
Convert indirect uses of net__ratelimited to
simply use net__ratelimited.
Add a nd_dbg macro and #define ND_DEBUG for the other
generally inactivated logging messages.
Make those inactivated messages emit only at KERN_DEBUG
instead of other levels.
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
---
drivers/pwm/pwm-samsung.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
index 023a3be..b415102 100644
---
Andy Lutomirski writes:
> On Thu, Dec 13, 2012 at 2:01 PM, Eric W. Biederman
> wrote:
>> Andy Lutomirski writes:
>>
>>> On 12/11/2012 01:17 PM, Eric W. Biederman wrote:
>
>> But please also note the difference between capable and ns_capable. Any
>> security check that is capable() still
On Fri, Dec 14, 2012 at 11:13:30AM +0800, Feng Tang wrote:
> > This seems like a great use of that hardware resource, and no doubt
> > those mach's also have a class RTC driver available talking to
> > different hardware.
>
> Interesting to know this, thanks for the info. For the x86 desktop
>
Stephen Rothwell writes:
> The virtio tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git#virtio-next)
> has a conflict with the net-next tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git#master)
> that requires the following extra fix up patch:
>
> diff
Hello Omar Ramirez Luna:
in drivers/staging/tidspbridge/rmgr/proc.c:
if strlen(drv_datap->base_img) == size, will pass checking (line 397)
the size is the full length of exec_file (line 382, line 468..469)
strcpy causes issue: src len is strlen(drv_datap->base_img) + '\0'. (line
On 12/14/2012 07:02 AM, Marcelo Tosatti wrote:
>>> Same comment as before: the only case where it should not attempt to
>>> emulate is when there is a condition which makes it impossible to fix
>>> (the information is available to detect that condition).
>>>
>>> The earlier suggestion
>>>
>>>
On Thu, Dec 13, 2012 at 06:10:49PM -0800, Darrick J. Wong wrote:
> On Thu, Dec 13, 2012 at 05:48:06PM -0800, Andy Lutomirski wrote:
> > On 12/13/2012 12:08 AM, Darrick J. Wong wrote:
> > > Several complaints have been received regarding long file write latencies
> > > when
> > > memory pages must
"Serge E. Hallyn" writes:
> Quoting Eric W. Biederman (ebied...@xmission.com):
>>
>> Andy Lutomirski pointed out that the current behavior of allowing the
>> owner of a user namespace to have all caps when that owner is not in a
>> parent user namespace is wrong.
>
> To make sure I understand
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> Andy Lutomirski pointed out that the current behavior of allowing the
> owner of a user namespace to have all caps when that owner is not in a
> parent user namespace is wrong.
To make sure I understand right, the issue is when a uid is
Andy Lutomirski pointed out that the current behavior of allowing the
owner of a user namespace to have all caps when that owner is not in a
parent user namespace is wrong. Add a test to ensure the owner of a user
namespace is in the parent of the user namespace to fix this bug.
Thankfully this
Last post of this patch appears lost, so I resend this.
Now discard merge works, add plug for blkdev_issue_discard. This will help
discard request merge especially for raid0 case. In raid0, a big discard
request is split to small requests, and if correct plug is added, such small
requests can be
In MD raid case, discard granularity might not be power of 2, for example, a
4-disk raid5 has 3*chunk_size discard granularity. Correct the calculation for
such cases.
Reported-by: Neil Brown
Signed-off-by: Shaohua Li
---
block/blk-lib.c| 23 +--
On Thu, Dec 13, 2012 at 07:38:26PM -0700, Jason Gunthorpe wrote:
> On Thu, Dec 13, 2012 at 06:00:23PM -0800, John Stultz wrote:
>
> > So per Jason's related patch, he's made the point that the
> > persistent_clock and RTC class functionality are basically exclusive
> > (well, in his case, he said
On 2012/12/14 7:01, Naoya Horiguchi wrote:
> Hi,
>
> I wrote this patch inspired by the discussion about fixing mce_bad_pages bug.
> https://lkml.org/lkml/2012/12/7/66
> As mentioned by Andrew, this bug seemed to be undetected because of the
> messiness of soft_offline_page(), so with this patch
On Thu, 13 Dec 2012, Stephen Rothwell wrote:
> Hi James,
>
> On Fri, 7 Dec 2012 10:21:31 +1100 (EST) James Morris
> wrote:
> >
> > On Thu, 6 Dec 2012, Linus Torvalds wrote:
> >
> > > Have people pulled that thing into anything else? Because quite
> > > frankly, I think it's unsalvageable
On Thu, Dec 13, 2012 at 11:55:24AM +, Lee Jones wrote:
> I understand your logic, hence why I wrote such a lengthy commit
> message. However, I'm not sure I see a logical way around it. Asking
> all users of MMCI to provide a not-regulator to declare that a
> secondary regulator isn't
In
http://www.mail-archive.com/linux-usb@vger.kernel.org/msg07976.html
Ulrich reported that his USB3 cardreader does not work reliably when
connected to the USB3 port. It turns out that USB3 controller failed
to be waken up when plugging in the USB3 cardreader. Further
experiment found that
On Thu, Dec 13, 2012 at 02:25:34PM -0800, Andrew Morton wrote:
> On Thu, 13 Dec 2012 13:12:20 -0500
> Neil Horman wrote:
>
> > On Thu, Dec 13, 2012 at 06:20:48AM -0600, Serge Hallyn wrote:
> > > Quoting Neil Horman (nhor...@tuxdriver.com):
> > > > Theres one problem I currently see with it, and
On Thu, Dec 13, 2012 at 08:17:26PM +0800, Zhi Yong Wu wrote:
> On Thu, Dec 13, 2012 at 3:50 AM, Darrick J. Wong
> wrote:
> > On Mon, Dec 10, 2012 at 11:30:03AM +0800, Zhi Yong Wu wrote:
> >> HI, all guys.
> >>
> >> any comments or suggestions?
> >
> > Why did ffsb drop from 924 transactions/sec
On Thu, Dec 13, 2012 at 11:48:18AM +, Lee Jones wrote:
> On Mon, 10 Dec 2012, Mark Brown wrote:
> > On Mon, Dec 10, 2012 at 08:55:51AM +, Lee Jones wrote:
> > > If a regulator is specified as always-on, then it can't have an
> > > enable/disable pin, as it can't be turned off.
> >
On Thu, Dec 13, 2012 at 06:00:23PM -0800, John Stultz wrote:
> So per Jason's related patch, he's made the point that the
> persistent_clock and RTC class functionality are basically exclusive
> (well, in his case, he said this with respect to updating the RTC,
> not reading it - I don't mean to
On Thu, Dec 13, 2012 at 6:33 PM, Eric W. Biederman
wrote:
>
> Andy thank you for your review.
>
> Andy Lutomirski writes:
>> This is confusing enough that I can't immediately tell whether it's
>> correct. I think it's close but out of order.
>
> Yeah. That is the trick. Figuring out how to
Andy thank you for your review.
Andy Lutomirski writes:
> This is confusing enough that I can't immediately tell whether it's
> correct. I think it's close but out of order.
Yeah. That is the trick. Figuring out how to write that code so it is
correct and obvious.
I have added a comment at
2012/12/14 Jens Axboe :
> On Mon, Dec 03 2012, Kent Overstreet wrote:
>> Last posting: http://thread.gmane.org/gmane.linux.kernel.aio.general/3169
>>
>> Changes since the last posting should all be noted in the individual
>> patch descriptions.
>>
>> * Zach pointed out the aio_read_evt() patch
From: fangxiaozhi
1. Add a new macro define for USB storage match rule.
2. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
3. Add to support new switch command for new Huawei USB
The DCACHE_NEED_AUTOMOUNT flag is cleared on mount and set on expire
for autofs rootless multi-mount dentrys to prevent unnecessary calls
to ->d_automount().
Since DCACHE_MANAGE_TRANSIT is always set on autofs dentrys ->d_managed()
is always called so the check can be done in ->d_manage() without
For direct (and offset) mounts, if an automounted mount is manually
umounted the trigger mount dentry can appear non-empty causing it to
not trigger mounts. This can also happen if there is a file handle
leak in a user space automounting application.
This happens because, when a ioctl control
On Thu, Dec 13, 2012 at 6:18 PM, H. Peter Anvin wrote:
> Wouldn't the vdso get mapped already and could be mremap()'d. If we really
> need more control I'd almost push for a device/filesystem node that could be
> mmapped the usual way.
Hmm. That may work, but it'll still break ABI. I'm not
Wouldn't the vdso get mapped already and could be mremap()'d. If we really
need more control I'd almost push for a device/filesystem node that could be
mmapped the usual way.
Andy Lutomirski wrote:
>On Thu, Dec 13, 2012 at 5:49 PM, H. Peter Anvin wrote:
>> On 12/13/2012 05:42 PM, Andy
Since MCE is an x86 concept, and this code is in mm/, it would be
better to use the name num_poisoned_pages instead of mce_bad_pages.
Signed-off-by: Xishi Qiu
Signed-off-by: Jiang Liu
Suggested-by: Borislav Petkov
Reviewed-by: Wanpeng Li
---
fs/proc/meminfo.c |2 +-
include/linux/mm.h
Move poisoned page check at the beginning of the function in order to
fix the error.
Signed-off-by: Xishi Qiu
Signed-off-by: Jiang Liu
Tested-by: Naoya Horiguchi
---
mm/memory-failure.c | 38 +-
1 files changed, 17 insertions(+), 21 deletions(-)
diff
On Thu, Dec 13, 2012 at 3:27 PM, H. Peter Anvin wrote:
> if we depend on other
> things we should make that explicit, not just here but in boot.txt.
please check lines for boot.txt
---
64-bit BOOT PROTOCOL
For machine with 64bit cpus and 64bit kernel, we could use 64bit bootloader
We
$ echo paddr > /sys/devices/system/memory/soft_offline_page to offline a
*free* page, the value of mce_bad_pages will be added, and the page is set
HWPoison flag, but it is still managed by page buddy alocator.
$ cat /proc/meminfo | grep HardwareCorrupted shows the value.
If we offline the same
There are too many return points randomly intermingled with some
"goto done" return points. So adjust the function structure, one
for the success path, the other for the failure path.
Use atomic_long_inc instead of atomic_long_add.
Signed-off-by: Xishi Qiu
Signed-off-by: Jiang Liu
Suggested-by:
On Thu, Dec 13, 2012 at 06:00:23PM -0800, John Stultz wrote:
> On 12/13/2012 05:37 PM, Feng Tang wrote:
> >On Thu, Dec 13, 2012 at 05:20:36PM -0800, John Stultz wrote:
> >>On 12/12/2012 06:05 PM, Feng Tang wrote:
> >>>In current kernel, there are several places which need to check
> >>>whether
On Thu, Dec 13, 2012 at 05:48:06PM -0800, Andy Lutomirski wrote:
> On 12/13/2012 12:08 AM, Darrick J. Wong wrote:
> > Several complaints have been received regarding long file write latencies
> > when
> > memory pages must be held stable during writeback. Since it might not be
> > acceptable to
On Thu, Dec 13, 2012 at 5:49 PM, H. Peter Anvin wrote:
> On 12/13/2012 05:42 PM, Andy Lutomirski wrote:
>>
>> The 64-bit/x32 case is currently very simple and fast because it uses
>> absolute addressing. Admittedly, pcrel references are free, so
>> changing this wouldn't cost much. For native,
On Thu, 2012-12-13 at 10:24 -0800, Greg KH wrote:
> On Thu, Dec 13, 2012 at 09:30:51AM -0700, Toshi Kani wrote:
> > On Thu, 2012-12-13 at 04:24 +, Greg KH wrote:
> > > On Wed, Dec 12, 2012 at 09:02:45PM -0700, Toshi Kani wrote:
> > > > On Wed, 2012-12-12 at 15:54 -0800, Greg KH wrote:
> > > >
On Fri, Dec 14, 2012 at 12:23 AM, Alex Williamson
wrote:
>
> Device 03:00.0 is your raid controller:
>
> 03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev
> 04)
>
> For some reason it's trying to read from ffe65000, ffe8a000, ffe89000,
> ffe86000, ffe87000, ffe84000.
On 12/13/2012 05:37 PM, Feng Tang wrote:
On Thu, Dec 13, 2012 at 05:20:36PM -0800, John Stultz wrote:
On 12/12/2012 06:05 PM, Feng Tang wrote:
In current kernel, there are several places which need to check
whether there is a persistent clock for the platform. Current check
is done by calling
On Thu, 2012-12-13 at 10:30 -0800, Greg KH wrote:
> On Thu, Dec 13, 2012 at 09:03:54AM -0700, Toshi Kani wrote:
> > On Thu, 2012-12-13 at 04:16 +, Greg KH wrote:
> > > On Wed, Dec 12, 2012 at 08:37:44PM -0700, Toshi Kani wrote:
> > > > On Wed, 2012-12-12 at 16:55 -0800, Greg KH wrote:
> > > >
Hi,
On Fri, Dec 14, 2012 at 02:23:36AM +0100, Sebastian Reichel wrote:
> On Mon, Nov 12, 2012 at 02:47:03PM -0800, Tony Lindgren wrote:
> > * Aaro Koskinen [121112 10:49]:
> > > Convert omap_wdt to new watchdog core. On OMAP boards, there are usually
> > > multiple watchdogs. Since the new
On 12/13/2012 07:35 PM, Borislav Petkov wrote:
> On Thu, Dec 13, 2012 at 11:07:43AM +0800, Alex Shi wrote:
now, on the other hand, if you have two threads of a process that
share a bunch of data structures, and you'd spread these over 2
sockets, you end up bouncing data between the
On 12/13/2012 05:42 PM, Andy Lutomirski wrote:
>
> The 64-bit/x32 case is currently very simple and fast because it uses
> absolute addressing. Admittedly, pcrel references are free, so
> changing this wouldn't cost much. For native, it'll be slower, but
> maybe no one cares. I seem to care
On 12/13/2012 12:08 AM, Darrick J. Wong wrote:
> Several complaints have been received regarding long file write latencies when
> memory pages must be held stable during writeback. Since it might not be
> acceptable to stall programs for the entire duration of a page write (which
> may
> take
Hi Tony,
On Thu, Dec 13, 2012 at 05:32:57PM -0800, Tony Lindgren wrote:
> * Sebastian Reichel [121213 17:26]:
> > What's the status of this patchset? If I'm not mistaken it is
> > neither included in linux-omap, nor in linux-watchdog-next.
>
> It should be all linux-watchdog-next with what got
On 12/13/2012 11:48 PM, Vincent Guittot wrote:
> On 13 December 2012 15:53, Vincent Guittot wrote:
>> On 13 December 2012 15:25, Alex Shi wrote:
>>> On 12/13/2012 06:11 PM, Vincent Guittot wrote:
On 13 December 2012 03:17, Alex Shi wrote:
> On 12/12/2012 09:31 PM, Vincent Guittot
On Mon, Nov 12, 2012 at 02:47:03PM -0800, Tony Lindgren wrote:
> * Aaro Koskinen [121112 10:49]:
> > Convert omap_wdt to new watchdog core. On OMAP boards, there are usually
> > multiple watchdogs. Since the new watchdog core supports multiple
> > watchdogs, all watchdog drivers used on OMAP
On Thu, Dec 13, 2012 at 5:32 PM, H. Peter Anvin wrote:
> On 12/13/2012 04:20 PM, Andy Lutomirski wrote:
>>
>>
>> What you could do is probably arrange (using some linker script magic)
>> for a symbol to exist that points at the page *before* the vdso
>> starts. Then just map the vvar page there
1 - 100 of 1552 matches
Mail list logo
