Clément, All,
On 2013-11-17 12:55 +0100, Clement Chauplannaz spake thusly:
> A bug in script `config' prevented from modifying an existing variable's
> value to a string that contains a colon ':'. The reason behind it is that
> colons are used as a separator in `sed' commands that script
On 11/15/2013 10:47 AM, Andrea Arcangeli wrote:
Hi,
1/3 is a bugfix so it should be applied more urgently. 1/3 is not as
fast as the current upstream code in the hugetlbfs + directio extreme
8GB/sec benchmark (but 3/3 should fill the gap later). The code is
identical to the one I posted in v1
On 11/18, Oleg Nesterov wrote:
>
> On 11/15, Eric W. Biederman wrote:
> >
> > I don't understand that one. Having a preforked thread with the proper
> > environment that can act like kthreadd in terms of spawning user mode
> > helpers works and is simple.
>
> Can't we ask ->child_reaper to create
On Monday 18 November 2013 11:02 PM, Lee Jones wrote:
On Mon, 18 Nov 2013, Mark Brown wrote:
On Mon, Nov 18, 2013 at 04:02:26PM +, Lee Jones wrote:
On Mon, 18 Nov 2013, Mark Brown wrote:
Like I say I'm suggesting that the bit of the code that understands the
flash chip is separate to the
On Mon, Nov 18, 2013 at 03:10:21PM +0100, Peter Zijlstra wrote:
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -746,13 +746,23 @@ void irq_exit(void)
> #endif
>
> account_irq_exit_time(current);
> - trace_hardirq_exit();
> sub_preempt_count(HARDIRQ_OFFSET);
> - if
On Mon, 18 Nov 2013, Michal Marek wrote:
> MFD_AS3722 can only be builtin, so it needs I2C builtin as well.
> With I2C=m, we get:
>
> drivers/mfd/as3722.c:372: undefined reference to `devm_regmap_init_i2c'
> drivers/built-in.o: In function `as3722_i2c_driver_init':
> drivers/mfd/as3722.c:444:
On 11/18/2013 10:30 AM, Catalin Marinas wrote:
> On Mon, Nov 18, 2013 at 05:03:37PM +, Stephen Warren wrote:
>> On 11/18/2013 04:58 AM, Catalin Marinas wrote:
>> ...
>>> Of course, trusted foundations interface could be plugged into cpu_ops
>>> on arm64 but I will NAK it on the grounds of not
Replace all mixed indentation with tabs
Signed-off-by: Johannes Löthberg
---
arch/x86/boot/a20.c | 62 ++---
1 file changed, 31 insertions(+), 31 deletions(-)
diff --git a/arch/x86/boot/a20.c b/arch/x86/boot/a20.c
index 64a31a6..c837ac6 100644
On Mon, Nov 18, 2013 at 03:26:53PM +0100, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > On Mon, Nov 18, 2013 at 09:59:45AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Nov 15, 2013 at 06:46:09AM +0100, Ingo Molnar escreveu:
> > > > btw., here's some 'perf top' call graph performance
On 11/15/2013 05:32 PM, Rafael J. Wysocki wrote:
On Friday, November 15, 2013 05:16:31 PM Shuah Khan wrote:
On 11/15/2013 05:21 PM, Rafael J. Wysocki wrote:
On Friday, November 15, 2013 05:03:57 PM Shuah Khan wrote:
device_wakeup_enable() uses dev_name(dev) as the wakeup source name.
When it
Hi Stephen,
You may want to CC intel-...@lists.freedesktop.org for i915 issues (even
if you are not subscribed and you mail will wait for a moderator to let
it go through).
In case of intel GPU hangs you should at least include
/sys/kernel/debug/dri/0/i915_error_state, probably submitting as a
[+cc Myron, Amos, Thomas, Ben]
On Mon, Nov 18, 2013 at 2:40 AM, Adam Lee wrote:
> This patch adds the PCI_EXP_FLAGS_SLOT check back before setting
> hotplug bridge, which is omitted by an API switching commit,
> 59875ae489609b2267548dc85160c5f0f0c6f9d4 "PCI/core: Use PCI Express
> Capability
On 11/18/2013 09:35 AM, David Cohen wrote:
> On 11/18/2013 07:28 AM, Christoph Hellwig wrote:
>> On Fri, Nov 15, 2013 at 04:09:18PM -0800, David Cohen wrote:
>>> This patch adds a test module to validate sfi_device() when used from a
>>> driver module.
>>
>> I don't think this is all that useful.
On 11/18/2013 08:42 AM, One Thousand Gnomes wrote:
After upgrading to kernel 3.12 I noticed one issue with tmux software.
The easiest way to reproduce will be:
1. Start tmux session as root.
2. Connect via ssh and use "tmux attach" to attach to the running
session.
3. Kill ssh client.
Heorhi,
On Mon, 18 Nov 2013, Mark Brown wrote:
> On Mon, Nov 18, 2013 at 04:02:26PM +, Lee Jones wrote:
> > On Mon, 18 Nov 2013, Mark Brown wrote:
>
> > > Like I say I'm suggesting that the bit of the code that understands the
> > > flash chip is separate to the bit of code that knows the mechanics
On Mon, Nov 18, 2013 at 05:03:37PM +, Stephen Warren wrote:
> On 11/18/2013 04:58 AM, Catalin Marinas wrote:
> ...
> > Of course, trusted foundations interface could be plugged into cpu_ops
> > on arm64 but I will NAK it on the grounds of not using the PSCI API, nor
> > the SMC calling
On 11/15, Eric W. Biederman wrote:
>
> I don't understand that one. Having a preforked thread with the proper
> environment that can act like kthreadd in terms of spawning user mode
> helpers works and is simple.
Can't we ask ->child_reaper to create the non-daemonized kernel thread
with the
Some SoCs, like Keystone 2, can support more than one WDT and each
watchdog device has to use it's own base address, clock source,
watchdog device, so add new davinci_wdt_device structure to hold
device data.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
Reviewed-by: Guenter roeck
On Mon, Nov 18, 2013 at 03:02:24PM +0100, Stanislaw Gruszka wrote:
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 7c70201..f02a567 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -727,7 +727,7 @@ static void update_curr(struct cfs_rq *cfs_rq)
> u64 now =
MFD_AS3722 can only be builtin, so it needs I2C builtin as well.
With I2C=m, we get:
drivers/mfd/as3722.c:372: undefined reference to `devm_regmap_init_i2c'
drivers/built-in.o: In function `as3722_i2c_driver_init':
drivers/mfd/as3722.c:444: undefined reference to `i2c_register_driver'
On Mon, Nov 18, 2013 at 05:00:32PM +, Stephen Warren wrote:
> On 11/17/2013 08:59 AM, Catalin Marinas wrote:
> > On 17 November 2013 08:49, Alexandre Courbot wrote:
> >> The ARM tree includes a firmware_ops interface that is designed to
> >> implement support for simple, TrustZone-based
On Mon, Nov 18, 2013 at 04:02:26PM +, Lee Jones wrote:
> On Mon, 18 Nov 2013, Mark Brown wrote:
> > Like I say I'm suggesting that the bit of the code that understands the
> > flash chip is separate to the bit of code that knows the mechanics of
> > sending commands and data to the chip.
>
The keystone arch use the same IP watchdog, so add "ti,keystone-wdt"
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
---
Add watchdog entry to keystone device tree.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Guenter Roeck
---
arch/arm/boot/dts/keystone.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/keystone.dts b/arch/arm/boot/dts/keystone.dts
index 100bdf5..a6e5f91 100644
---
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
---
.../devicetree/bindings/watchdog/davinci-wdt.txt |4
1 file changed, 4
To reduce code duplicate and increase code readability use WDT core
code to handle WDT interface.
Remove io_lock as the WDT core uses mutex to lock each wdt device.
Remove wdt_state as the WDT core track state with its own variable.
The watchdog_init_timeout() can read timeout value from
These patches are intended to update Davinci watchdog to use WDT core
and reuse driver for keystone arch, because Keystone uses the similar
IP like Davinci.
See Documentation:
Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf
Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Signed-off-by: Ivan Khoronzhuk
Acked-by: Santosh Shilimkar
---
drivers/watchdog/davinci_wdt.c | 26 ++
1 file changed, 26
From: Linus Pizunski
Update month and day of month to the alarm month/day instead
of current day/month when setting the RTC alarm mask.
Signed-off-by: Linus Pizunski
Acked-by: Nicolas Ferre
---
drivers/rtc/rtc-at91rm9200.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 11/18/2013 10:10 AM, Russell King - ARM Linux wrote:
> On Mon, Nov 18, 2013 at 10:03:37AM -0700, Stephen Warren wrote:
>> On 11/18/2013 04:58 AM, Catalin Marinas wrote:
>> ...
>>> Of course, trusted foundations interface could be plugged into cpu_ops
>>> on arm64 but I will NAK it on the
* Vince Weaver wrote:
> On Mon, 18 Nov 2013, Peter Zijlstra wrote:
>
> > On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
> > >
> > > (figured out the minicom issue).
> > >
> > > Anyway while trying to reproduce the last bug I instead got this with
> > > the perf_fuzzer.
> > >
On Sun, Nov 17, 2013 at 03:59:04PM +, Catalin Marinas wrote:
> No L2x0 (L210, L220, PL310) cache on ARMv8. And here I strongly
> recommend the hardware people to make proper external caches which can
> be flushed by standard CPU instructions, not MMIO. Any such caches
> must be enabled by
On Mon, Nov 18, 2013 at 10:03:37AM -0700, Stephen Warren wrote:
> On 11/18/2013 04:58 AM, Catalin Marinas wrote:
> ...
> > Of course, trusted foundations interface could be plugged into cpu_ops
> > on arm64 but I will NAK it on the grounds of not using the PSCI API, nor
> > the SMC calling
On 11/18/2013 04:58 AM, Catalin Marinas wrote:
...
> Of course, trusted foundations interface could be plugged into cpu_ops
> on arm64 but I will NAK it on the grounds of not using the PSCI API, nor
> the SMC calling convention (and it's easy to fix when porting to ARMv8).
> If a supported
On 11/17/2013 08:59 AM, Catalin Marinas wrote:
> On 17 November 2013 08:49, Alexandre Courbot wrote:
>> The ARM tree includes a firmware_ops interface that is designed to
>> implement support for simple, TrustZone-based firmwares but could
>> also cover other use-cases. It has been suggested that
On Mon, Nov 18, 2013 at 5:44 PM, Vince Weaver wrote:
> On Mon, 18 Nov 2013, Stephane Eranian wrote:
>
>> What's the config for this test?
>> Need to host CPU type and the event config.
>> Otherwise there is not much I can do with the crash dump.
>
> It's 3.12, on a core2 machine.
>
On core2,
On Mon 18-11-13 10:41:15, Johannes Weiner wrote:
> On Thu, Nov 14, 2013 at 03:26:51PM -0800, David Rientjes wrote:
> > When current has a pending SIGKILL or is already in the exit path, it
> > only needs access to memory reserves to fully exit. In that sense, the
> > memcg is not actually oom for
On 18-11-2013 12:25, Guenter Roeck wrote:
> On Mon, Nov 18, 2013 at 10:27:41AM -0400, Eduardo Valentin wrote:
>> On 15-11-2013 03:43, Jean Delvare wrote:
>>> Hi Eduardo,
>>>
>>
>> Hello Jean!
>>
>>> Sorry for joining the discussion a little late, I could never find the
>>> time to look into this
2013/11/18 James Bottomley :
> On Mon, 2013-11-18 at 14:18 -0200, Geyslan Gregório Bem wrote:
>> 2013/11/18 James Bottomley :
>> > On Sun, 2013-11-17 at 23:12 -0200, Geyslan Gregório Bem wrote:
>> >> 2013/11/17 James Bottomley :
>> >> > On Sun, 2013-11-17 at 19:09 -0200, Geyslan Gregório Bem
On 11/18/2013 09:57 AM, Shawn Guo wrote:
> On Mon, Nov 18, 2013 at 08:45:12AM -0600, Nishanth Menon wrote:
>
>> I do not agree about this stance - device tree describes hardware
>> capabilities to kernel -> I agree with that statement. Kernel should
>> not care if that is provided by
On Wed, Nov 13, 2013 at 04:48:32PM -0800, David Rientjes wrote:
> On Wed, 13 Nov 2013, Johannes Weiner wrote:
>
> > > The reclaim will fail, the only reason current has TIF_MEMDIE set is
> > > because reclaim has completely failed.
> >
> > ...for somebody else.
> >
>
> That process is in the
On Sat, Nov 16, 2013 at 11:01 AM, Oleg Nesterov wrote:
> set_dumpable() updates MMF_DUMPABLE_MASK in a non-trivial way to
> ensure that get_dumpable() can't observe the intermediate state,
> but this all can't help if multiple threads call set_dumpable()
> at the same time.
>
> And in theory
On Mon, 18 Nov 2013, Stephane Eranian wrote:
> What's the config for this test?
> Need to host CPU type and the event config.
> Otherwise there is not much I can do with the crash dump.
It's 3.12, on a core2 machine.
Sadly I don't have the event config. To reproduce I start my perf_fuzzer
On Mon, 18 Nov 2013, Peter Zijlstra wrote:
> On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
> >
> > (figured out the minicom issue).
> >
> > Anyway while trying to reproduce the last bug I instead got this with
> > the perf_fuzzer.
> >
> > Is it worth continuing to run and
On 11/18/2013 06:24 PM, Guenter Roeck wrote:
On Mon, Nov 18, 2013 at 04:21:06PM +0200, ivan.khoronzhuk wrote:
On 11/17/2013 04:24 AM, Guenter Roeck wrote:
On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote:
When watchdog timer is expired we can know about it thought
thought -> through or with
On Mon, Nov 18, 2013 at 10:27:41AM -0400, Eduardo Valentin wrote:
> On 15-11-2013 03:43, Jean Delvare wrote:
> > Hi Eduardo,
> >
>
> Hello Jean!
>
> > Sorry for joining the discussion a little late, I could never find the
> > time to look into this patch series so far.
>
> Well, better late
On Mon, 2013-11-18 at 14:18 -0200, Geyslan Gregório Bem wrote:
> 2013/11/18 James Bottomley :
> > On Sun, 2013-11-17 at 23:12 -0200, Geyslan Gregório Bem wrote:
> >> 2013/11/17 James Bottomley :
> >> > On Sun, 2013-11-17 at 19:09 -0200, Geyslan Gregório Bem wrote:
> >> >> 2013/11/17 James
On Mon, Nov 18, 2013 at 04:21:06PM +0200, ivan.khoronzhuk wrote:
> On 11/17/2013 04:24 AM, Guenter Roeck wrote:
> > On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote:
> >> When watchdog timer is expired we can know about it thought
> >
> > thought -> through or with
> >
>
> Ok
>
> >> GET_STATUS
2013/11/18 James Bottomley :
> On Sun, 2013-11-17 at 23:12 -0200, Geyslan Gregório Bem wrote:
>> 2013/11/17 James Bottomley :
>> > On Sun, 2013-11-17 at 19:09 -0200, Geyslan Gregório Bem wrote:
>> >> 2013/11/17 James Bottomley :
>> >> > On Sun, 2013-11-17 at 15:51 -0300, Geyslan G. Bem wrote:
>>
On 11/18/2013 04:35 PM, Dmitry Kasatkin wrote:
On Thu, Nov 7, 2013 at 4:00 PM, Roberto Sassu wrote:
This patch allows users to provide a custom template format through the
new kernel command line parameter 'ima_template_fmt'. If the supplied
format is not valid, IMA uses the default template
On Fri, Nov 15, 2013 at 3:30 PM, Tim Kryger wrote:
> On Fri, Nov 15, 2013 at 2:52 PM, Wolfram Sang wrote:
>
>> Fixed Kconfig sorting, squashed broken out patches 1-3 into one and
>> applied to for-next, thanks! Let me know if I should take patches 4-5
>> also, but usually they go via arm-soc.
On Mon, 18 Nov 2013, Mark Brown wrote:
> On Mon, Nov 18, 2013 at 03:31:10PM +, Lee Jones wrote:
> > On Mon, 18 Nov 2013, Mark Brown wrote:
>
> > > This doesn't seem realistic, you're assuming that system integrators
> > > won't go and use chips you've not heard of and at least in the case of
On Mon, Nov 18, 2013 at 08:45:12AM -0600, Nishanth Menon wrote:
> I do not agree about this stance - device tree describes hardware
> capabilities to kernel -> I agree with that statement. Kernel should
> not care if that is provided by bootloader/firmware/fused into
> flash/ROM etc.
Yea,
>> +static int bcm2835_i2s_hw_params(struct snd_pcm_substream *substream,
>> + struct snd_pcm_hw_params *params,
>> + struct snd_soc_dai *dai)
>> +{
>> +struct bcm2835_i2s_dev *dev = snd_soc_dai_get_drvdata(dai);
>> +
>> +unsigned int
On Mon, 2013-11-18 at 17:30 +0200, Dmitry Kasatkin wrote:
> On Fri, Nov 15, 2013 at 3:45 PM, Roberto Sassu
> wrote:
> > @@ -160,12 +161,13 @@ static int ima_calc_field_array_hash_tfm(struct
> > ima_field_data *field_data,
> > return rc;
> >
> > for (i = 0; i <
Vince,
What's the config for this test?
Need to host CPU type and the event config.
Otherwise there is not much I can do with the crash dump.
Thanks.
On Mon, Nov 18, 2013 at 4:32 PM, Peter Zijlstra wrote:
> On Mon, Nov 18, 2013 at 04:18:34PM +0100, Stephane Eranian wrote:
>> Peter,
>>
>> I
On 18 November 2013 21:04, Nishanth Menon wrote:
> depends on how we look at it.. if we consider freq_table as a list of
> valid frequencies, anything that is not in there is an invalid entry.
Partly correct. Yes freq table has a list of valid frequencies, but normally
we just build a table of
On Mon, Nov 18, 2013 at 03:31:10PM +, Lee Jones wrote:
> On Mon, 18 Nov 2013, Mark Brown wrote:
> > This doesn't seem realistic, you're assuming that system integrators
> > won't go and use chips you've not heard of and at least in the case of
> > things like quad read my understanding is
On Fri, Nov 15, 2013 at 12:13:08PM -0700, jerry.hoem...@hp.com wrote:
[..]
> > Is it possible to fix it the way hpa suggested?
>
> I think the changes to enable ,high is a step in the
> right direction. its an improvement But it is still green.
>
> We are having lots more problems w/
On Thu, Nov 14, 2013 at 03:26:51PM -0800, David Rientjes wrote:
> When current has a pending SIGKILL or is already in the exit path, it
> only needs access to memory reserves to fully exit. In that sense, the
> memcg is not actually oom for current, it simply needs to bypass memory
> charges to
* Peter Zijlstra wrote:
> I would be tempted to say you should simply mark the tsc unstable on
> boot and live with that -- we fully assume the sched_clock stuff is
> not going backwards in an 'observable' way.
BIOS crap and actual hardware bugs do happen - so kernel code needs to
consider
* Peter Zijlstra wrote:
> On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
> >
> > (figured out the minicom issue).
> >
> > Anyway while trying to reproduce the last bug I instead got this
> > with the perf_fuzzer.
> >
> > Is it worth continuing to run and report these issues?
On 11/18/2013 09:22 AM, Viresh Kumar wrote:
> On 18 November 2013 20:38, Nishanth Menon wrote:
>> On 11/15/2013 11:22 PM, viresh kumar wrote:
>
>>> I have a untested patch for this. If this looks okay, Nishant can you
>>> please try
>>> below patch? With some fixups from your side :)
>>
>>
On Mon, Nov 18, 2013 at 04:18:34PM +0100, Stephane Eranian wrote:
> Peter,
>
> I missed the beginning of this thread somehow.
> What's the initial problem?
lkml.kernel.org/r/alpine.deb.2.10.1311141412060.8...@vincent-weaver-1.um.maine.edu
On Fri, Nov 15, 2013 at 02:24:25PM -0800, Yinghai Lu wrote:
> On Fri, Nov 15, 2013 at 10:03 AM, Vivek Goyal wrote:
> > On Fri, Nov 15, 2013 at 09:33:41AM -0800, Yinghai Lu wrote:
>
> >> I have one system with 6TiB memory, kdump does not work even
> >> crashkernel=512M in legacy mode. ( it only
On Mon, 18 Nov 2013, Mark Brown wrote:
> On Mon, Nov 18, 2013 at 02:56:14PM +, Lee Jones wrote:
>
> > I think it's a good idea for people using the m25p80, but still
> > doesn't effect us. All of our chips are dynamically probable. We are
>
> This doesn't seem realistic, you're assuming
On Fri, Nov 15, 2013 at 3:45 PM, Roberto Sassu wrote:
> To maintain compatibility with userspace tools, the field length must not
> be included in the template digest calculation for the 'ima' template.
>
> Signed-off-by: Roberto Sassu
> Signed-off-by: Mimi Zohar
> ---
>
On 11/17/2013 04:28 AM, Guenter Roeck wrote:
On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote:
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk
---
.../devicetree/bindings/watchdog/davinci-wdt.txt
On 18 November 2013 20:38, Nishanth Menon wrote:
> On 11/15/2013 11:22 PM, viresh kumar wrote:
>> I have a untested patch for this. If this looks okay, Nishant can you please
>> try
>> below patch? With some fixups from your side :)
>
> http://pastebin.mozilla.org/3628975
>
> I agree that it
Peter,
I missed the beginning of this thread somehow.
What's the initial problem?
On Mon, Nov 18, 2013 at 9:54 AM, Peter Zijlstra wrote:
> On Fri, Nov 15, 2013 at 12:26:16PM -0500, Vince Weaver wrote:
>> On Fri, 15 Nov 2013, Peter Zijlstra wrote:
>> >
>> > Please enable CONFIG_FRAME_POINTER to
On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
>
> (figured out the minicom issue).
>
> Anyway while trying to reproduce the last bug I instead got this with
> the perf_fuzzer.
>
> Is it worth continuing to run and report these issues? I'm losing track
> of all the open bugs.
On Mon, Nov 18, 2013 at 02:56:14PM +, Lee Jones wrote:
> I think it's a good idea for people using the m25p80, but still
> doesn't effect us. All of our chips are dynamically probable. We are
This doesn't seem realistic, you're assuming that system integrators
won't go and use chips you've
On 11/18/2013 04:31 PM, Guenter Roeck wrote:
On 11/18/2013 03:47 AM, ivan.khoronzhuk wrote:
MODULE_LICENSE("GPL");
-MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR);
MODULE_ALIAS("platform:watchdog");
You might want to rename the platform driver to something like
davinci-wdt and change the
On Sat, 16 Nov 2013, Vishal Annapurve wrote:
> Hi,
>
> Here are the updated patches:
>
> [PATCH 1/3] usb: storage: Proper cmd result assignment
>
> This change replaces DID_ABORT with DID_TIMEOUT as a command result
> whenever US_FLIDX_TIMED_OUT bit is set.
>
> This change is made to bring
On 11/15/2013 11:22 PM, viresh kumar wrote:
> On Saturday 16 November 2013 06:40 AM, Rafael J. Wysocki wrote:
>> On Friday, November 15, 2013 06:20:43 PM Nishanth Menon wrote:
>
>>> So, instead of having a statistics information that never ever
>>> reflects valid data in the mentioned case and
On Mon, Nov 18, 2013 at 02:24:43PM +, Lars-Peter Clausen wrote:
> On 11/18/2013 03:16 PM, Mark Rutland wrote:
> >
> >> +static void bcm2835_i2s_stop_clock(struct bcm2835_i2s_dev *dev)
> >> +{
> >> + uint32_t clkreg;
> >
> > s/uint32_t/u32/ (and elsewhere...)
>
> Please don't do that.
On Mon, Nov 18, 2013 at 06:40:41PM +0530, Laxman Dewangan wrote:
> From: Ashwini Ghuge
>
> NVIDIA Tegra124 supports has the new gpio port as GPIO_FF.
> Add the macro for this port name.
>
> Signed-off-by: Ashwini Ghuge
> Signed-off-by: Laxman Dewangan
> ---
>
On 11/17/2013 04:27 AM, Guenter Roeck wrote:
On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote:
The keystone arch use the same IP watchdog, so add "ti,keystone-wdt"
compatible and correct identity.
Signed-off-by: Ivan Khoronzhuk
---
.../devicetree/bindings/watchdog/davinci-wdt.txt | 11
On Mon, Nov 18, 2013 at 02:54:00PM +, Russell King - ARM Linux wrote:
> On Mon, Nov 18, 2013 at 04:30:17PM +0200, Andy Shevchenko wrote:
> > On Mon, 2013-11-18 at 13:16 +0100, Florian Meier wrote:
> > > >> + uint32_t chans_available;
> > > >
> > > > Why uint32_t?
> > >
> > > Because it
On Sun, 2013-11-17 at 23:12 -0200, Geyslan Gregório Bem wrote:
> 2013/11/17 James Bottomley :
> > On Sun, 2013-11-17 at 19:09 -0200, Geyslan Gregório Bem wrote:
> >> 2013/11/17 James Bottomley :
> >> > On Sun, 2013-11-17 at 15:51 -0300, Geyslan G. Bem wrote:
> >> >> This patch fix memory leakage
On Mon, Nov 18, 2013 at 8:10 PM, Marc Zyngier wrote:
> On 2013-11-18 14:18, Vinayak Kale wrote:
>>
>> On Mon, Nov 18, 2013 at 7:16 PM, Marc Zyngier
>> wrote:
>>>
>>> Vinayak,
>>>
>>>
>>> On 2013-11-18 13:22, Vinayak Kale wrote:
Add support for irq registration when pmu interrupt
On Mon, 18 Nov 2013, Mark Brown wrote:
> On Mon, Nov 18, 2013 at 02:24:47PM +, Lee Jones wrote:
>
> > For example, we have thought about inserting a layer which handles the
> > type of communication that'll be utilised i.e. true SPI, or our
> > bespoke FSM implementation for instance. This
Ping^2. I still haven't seen any comments on any of these patches.
--
Joseph S. Myers
jos...@codesourcery.com
--
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
On Mon, Nov 18, 2013 at 04:30:17PM +0200, Andy Shevchenko wrote:
> On Mon, 2013-11-18 at 13:16 +0100, Florian Meier wrote:
> > >> +uint32_t chans_available;
> > >
> > > Why uint32_t?
> >
> > Because it is a bit mask of fixed length that directly comes from the
> > firmware.
>
> Like one
Hello Jean,
I will try to complement what Rui's already commented.
On 18-11-2013 02:04, Zhang Rui wrote:
> On 五, 2013-11-15 at 09:07 +0100, Jean Delvare wrote:
>> Hi Eduardo,
>>
>> On Tue, 12 Nov 2013 15:46:04 -0400, Eduardo Valentin wrote:
>>> This patch introduces a device tree bindings for
On Mon, Nov 18, 2013 at 02:24:47PM +, Lee Jones wrote:
> For example, we have thought about inserting a layer which handles the
> type of communication that'll be utilised i.e. true SPI, or our
> bespoke FSM implementation for instance. This would enable us to issue
> serial_flash_write(),
On 11/16/2013 10:02 PM, Viresh Kumar wrote:
> On 16 November 2013 19:14, Shawn Guo wrote:
>> No, it's not a kernel bug.
>>
>> OPP is not a definition that belongs to kernel. Instead, it's
>> characteristics of hardware, and that's why we can naturally put the
>> definition into device tree.
On Sun, Nov 17, 2013 at 03:39:19PM +, Florian Meier wrote:
> Add support for DMA controller of BCM2835 as used in the Raspberry Pi.
> Currently it only supports cyclic DMA.
>
> Signed-off-by: Florian Meier
> ---
>
> This version includes some more style improvements
> suggested in the
On 2013-11-18 14:18, Vinayak Kale wrote:
On Mon, Nov 18, 2013 at 7:16 PM, Marc Zyngier
wrote:
Vinayak,
On 2013-11-18 13:22, Vinayak Kale wrote:
Add support for irq registration when pmu interrupt is percpu.
Signed-off-by: Vinayak Kale
Signed-off-by: Tuan Phan
---
401 - 500 of 1351 matches
Mail list logo
