With arch/arm calling of_clk_init(NULL) from time_init(), we can now
remove custom .init_time hooks. To get rid of it, move l2cc init to
.init_machine hook instead.
Signed-off-by: Sebastian Hesselbarth
Acked-by: Srinivas Kandagatla
---
Cc: Olof Johansson
Cc: Arnd Bergmann
Cc: Srinivas
With arch/arm calling of_clk_init(NULL) from time_init(), we can now
remove custom .init_time hooks.
Signed-off-by: Sebastian Hesselbarth
---
Cc: Olof Johansson
Cc: Arnd Bergmann
Cc: Russell King
Cc: Stephen Warren
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-te...@vger.kernel.org
Cc:
nomadik_clk_init currently also maps system reset controller base address
used by clocks and registers a reboot notifier. To allow further cleanup of
nomadik clk setup, this moves system reset controller setup from
nomadik_clk_init to its own function.
Signed-off-by: Sebastian Hesselbarth
---
Common clock framework allows to register clock providers to get called
on of_clk_init() by using CLK_OF_DECLARE. This converts prima2 clock
provider to make use of it and get rid of the mach specific clk init
call.
Signed-off-by: Sebastian Hesselbarth
---
Cc: Olof Johansson
Cc: Arnd Bergmann
* Javier Martinez Canillas [130918 07:20]:
>
> Hi Tony,
>
> I don't know if OMAP2+ DT will happen soon as you said. At least I
> know about a big issue we had with GPIO pins not being auto-requested
> when are mapped as IRQ. You can refer to [1] for the latest approach
> and how this discussion
* Pali Rohár [130918 09:08]:
> On Wednesday 18 September 2013 15:16:44 Pavel Machek wrote:
> > On Sun 2013-09-08 02:02:52, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > On Fri, Sep 06, 2013 at 10:34:05PM +0200, Pali Rohár wrote:
> > > > > --- /dev/null
> > > > > +++
On 27/06/13 14:48, Nick Dyer wrote:
The configuration is stored in NVRAM on the maXTouch chip. When the device is
reset it reports a CRC of the stored configuration values. Therefore it isn't
necessary to send the configuration on each probe - we can check the CRC
matches and avoid a
At Mon, 9 Sep 2013 08:31:38 +0530,
Ramkumar Ramachandra wrote:
>
> Davidlohr Bueso wrote:
> > diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> > index d318862..7784347 100644
> > --- a/tools/perf/builtin-lock.c
> > +++ b/tools/perf/builtin-lock.c
> > @@ -321,10 +321,12 @@
Hi Davidlohr, thanks for your enhancements and cleanings!
At Sun, 8 Sep 2013 19:19:17 -0700,
Bueso wrote:
>
> While this could be seen as personal taste, there really isn't any
> reason for being so stingy printing the lock name. Furthermore, some
> symbol names are really just too long, and
Hi,
On Wed, Sep 18, 2013 at 07:18:04PM +0200, Laurent Pinchart wrote:
> On Wednesday 18 September 2013 13:16:27 Linus Walleij wrote:
> > On Tue, Sep 17, 2013 at 9:07 PM, Felipe Balbi wrote:
> > > has anyone ever successfully using gpio-pcf857x.c driver with 16-bit
> > > gpio expanders ? We're
On Wed, Sep 18, 2013 at 06:45:09PM +0200, Thomas Petazzoni wrote:
> Dear Jean Pihet,
>
> On Wed, 18 Sep 2013 17:53:44 +0200, Jean Pihet wrote:
> > This commit:
> > 573145f08c2b92c45498468afbbba909f6ce6135
> > clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE
> >
> > replaced a call to
On Wed, Sep 18, 2013 at 06:43:49PM +0200, Pali Rohár wrote:
> On Wednesday 18 September 2013 18:36:49 Felipe Balbi wrote:
> > On Wed, Sep 18, 2013 at 05:56:12PM +0200, Pali Rohár wrote:
> > > On Wednesday 18 September 2013 15:57:13 Javier Martinez
> > > Canillas
> > >
> > > wrote:
> > > > to
The problem in efi_main was that the idt was cleared before the
interrupts were disabled.
The UEFI spec states that interrupts aren't used so this shouldn't be
too much of a problem. Peripherals however don't necessarily know about
this and thus might cause interrupts to happen anyway. Even if
The following changes since commit e831cbfc1ad843b5542cc45f777e1a00b73c0685:
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux (2013-09-11 08:36:03
-0700)
are available in the git repository at:
> As for aio-direct... Two questions:
> * had anybody tried to measure the effect on branch predictor from
> introducing that method vector? Commit d6afd4c4 ("iov_iter: hide iovec
> details behind ops function pointers")
FWIW, I never did. I only went that route to begin with because the
On Wed, Sep 18, 2013 at 6:52 PM, Peter Hurley wrote:
> Ouch. But thanks for clarifying that.
>
> Ok, so register access needs to be serialized. And a separate but
> related concern is that gen6+ resets also need to hold-off register
> access where forcewake is required.
>
>
> While I was
On Sun, Sep 15, 2013 at 01:40:36PM +0100, Grant Likely wrote:
> On Thu, 12 Sep 2013 09:50:40 -0700, Soren Brinkmann
> wrote:
> > Zynq is based on an ARM Cortex-A9 MPCore, which features the
> > arm_global_timer in its SCU. Therefore enable the timer for Zynq.
> >
> > Signed-off-by: Soren
On 27/06/13 14:48, Nick Dyer wrote:
The existing implementation which encodes the configuration as a binary blob
in platform data is unsatisfactory since it requires a kernel recompile for
the configuration to be changed, and it doesn't deal well with firmware
changes that move values around on
>phy.notifier is not initalized
Signed-off-by: Pali Rohár
diff --git a/drivers/usb/phy/phy-twl4030-usb.c
b/drivers/usb/phy/phy-twl4030-usb.c
index 8f78d2d..efe6155 100644
--- a/drivers/usb/phy/phy-twl4030-usb.c
+++ b/drivers/usb/phy/phy-twl4030-usb.c
@@ -705,6 +705,8 @@ static int
On Wed, Sep 18, 2013 at 12:03:09PM -0400, Eduardo Valentin wrote:
> This patch introduces a device tree bindings for
> describing the hardware thermal behavior and limits.
> Also a parser to read and interpret the data and feed
> it in the thermal framework is presented.
>
> This patch introduces
Hi,
On Mon, Aug 12, 2013 at 04:05:10PM +0200, Andreas Larsson wrote:
> diff --git a/drivers/usb/gadget/gr_udc.c b/drivers/usb/gadget/gr_udc.c
> new file mode 100644
> index 000..37a6c08
> --- /dev/null
> +++ b/drivers/usb/gadget/gr_udc.c
> @@ -0,0 +1,2268 @@
> +/*
> + * USB Peripheral
More power supply drivers depends on vbus events and without it they not
working. Power supply drivers using usb_register_notifier, so to deliver
events it is needed to call atomic_notifier_call_chain.
So without atomic notifier power supply driver isp1704 not retrieving
vbus status and reporting
On Wed, Sep 18, 2013 at 12:52:07PM -0400, Peter Hurley wrote:
> On 09/17/2013 04:55 PM, Daniel Vetter wrote:
> > On Tue, Sep 17, 2013 at 9:50 PM, Peter Hurley
> > wrote:
> >> On 09/11/2013 03:31 PM, Peter Hurley wrote:
> >>>
> >>> [+cc dri-devel]
> >>>
> >>> On 09/11/2013 11:38 AM, Steven
Hi José,
On Wednesday 18 of September 2013 16:52:49 José Miguel Gonçalves wrote:
> The Samsung serial driver currently does not support setting the
> RTS pin with an ioctl(TIOCMSET) call. This patch adds this support.
>
> Changes in v2:
> - Preserve the RTS pin's manual setting in
* Pali Rohár [130918 01:41]:
>
> I'm not very happy. I sent this patch 6 months ago and only now
> you commented that needs rework again. This patch is needed
> because all thumb-2 userspace binaries crashing. I want to have
> working support for Nokia N900 and not always rebasing and
>
On Wednesday 18 September 2013 13:16:27 Linus Walleij wrote:
> On Tue, Sep 17, 2013 at 9:07 PM, Felipe Balbi wrote:
> > has anyone ever successfully using gpio-pcf857x.c driver with 16-bit
> > gpio expanders ? We're having some issues here where toggling the last
> > gpio pin (gpio 15) on a
Dmitry Torokhov wrote:
>On Wed, Sep 18, 2013 at 05:12:02PM +0100, Jonathan Cameron wrote:
>>
>>
>> Dmitry Torokhov wrote:
>> >On Wed, Sep 18, 2013 at 10:39:42AM +0100, Jonathan Cameron wrote:
>> >>
>> >>
>> >> "Zubair Lutfullah :" wrote:
>> >> >On Tue, Sep 17, 2013 at 09:27:27PM -0700,
Hi,
On Wed, Sep 18, 2013 at 05:46:10PM +0100, Mark Rutland wrote:
> > > > I even wrote a patch making USB3 PHY optional, but didn't push it
> > > > exactly because it broke some other systems and I can't guarantee users
> > > > won't mess up their DTS/pdata.
> > >
> > > Does that mean that their
On Wednesday 18 September 2013 18:36:49 Felipe Balbi wrote:
> On Wed, Sep 18, 2013 at 05:56:12PM +0200, Pali Rohár wrote:
> > On Wednesday 18 September 2013 15:57:13 Javier Martinez
> > Canillas
> >
> > wrote:
> > > to split the patch in two since the patch was solving
> > > two separate issues
>
On Wed, Sep 18, 2013 at 09:22:31AM -0500, Tejun Heo wrote:
> > > We have a small number of MSIs available, limited by hardware &
> > > firmware, if we don't impose a quota then the first device that probes
> > > will get most/all of the MSIs and other devices miss out.
> >
> > Out of curiosity -
On Wed, Sep 18, 2013 at 03:21:18PM +0100, Felipe Balbi wrote:
> Hi,
>
> On Wed, Aug 28, 2013 at 05:01:51PM +0100, Mark Rutland wrote:
> > > > So it's not physically possible for someone to just wire up a single phy
> > > > to the device, either USB2-only or USB3?
> > >
> > > of course it is :-)
Dear Jean Pihet,
On Wed, 18 Sep 2013 17:53:44 +0200, Jean Pihet wrote:
> This commit:
> 573145f08c2b92c45498468afbbba909f6ce6135
> clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE
>
> replaced a call to the driver's timer initialization by a call to
> clocksource_of_init(). However, it
On Wed, Sep 18, 2013 at 05:12:02PM +0100, Jonathan Cameron wrote:
>
>
> Dmitry Torokhov wrote:
> >On Wed, Sep 18, 2013 at 10:39:42AM +0100, Jonathan Cameron wrote:
> >>
> >>
> >> "Zubair Lutfullah :" wrote:
> >> >On Tue, Sep 17, 2013 at 09:27:27PM -0700, Dmitry Torokhov wrote:
> >> >> Hi
This patch introduces a device tree bindings for
describing the hardware thermal behavior and limits.
Also a parser to read and interpret the data and feed
it in the thermal framework is presented.
This patch introduces a thermal data parser for device
tree. The parsed data is used to build
Resent due to Thunderbird completely mangling it the first time around:
(Apologies if this is a third copy, gmail told me it didn't send)
On 09/07/2013 05:32 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest
> -next kernel, I've
> stumbled
From: Thierry Reding
Date: Wed, 18 Sep 2013 14:49:55 +0200
> The dump_eth_one() function is only used if DEBUG is enabled, so protect
> it by a corresponding #ifdef DEBUG block.
>
> Signed-off-by: Thierry Reding
I would prefer that this function and the one call site is simply
removed
On Wed, Sep 18, 2013 at 05:56:12PM +0200, Pali Rohár wrote:
> On Wednesday 18 September 2013 15:57:13 Javier Martinez Canillas
> wrote:
> > to split the patch in two since the patch was solving
> > two separate issues
>
> My patch does not solving *two* issues. It is *one* regression
> and both
Hi All,
this is the first attempt to introduce new Linux FPGA subsystem which
can help us to unify all fpga drivers which in general do the same
things.
Xilinx has hwicap in the kernel as char driver (drivers/char/xilinx_hwicap/)
and I would like to base Zynq devcfg driver based on this interface
From: Sudeep KarkadaNagesha
This implementation maintains the hierarchy of cache objects which reflects
the system's cache topology. Cache objects are instantiated as needed as
CPUs come online. The cache objects are replicated per-cpu even if they are
shared(similar to x86 implementation, for
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 7 of 7
>
> Update the help text and description for farsync configuration in the Kernel.
> Build farsync and fsflex when the farsync driver is selected.
fsflex seems to be an entirely
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
HEAD: a8e0108cac181a7b141dacaa99ea52efaf9b5f07 perf: Fix UAPI export of
PERF_EVENT_IOC_ID
Two small fixes.
Thanks,
Ingo
On 09/07/2013 05:32 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest
> -next kernel, I've
> stumbled on the following:
>
> The disassembly is:
>
> /* Check the cache first. */
> /* (Cache hit rate is typically around 35%.)
From: Sudeep KarkadaNagesha
In order to support outer cache in the cacheinfo infrastructure, a new
function 'get_info' is added to outer_cache_fns. This function is used
to get the outer cache information namely: line size, number of ways of
associativity and number of sets.
This patch adds
On Wednesday 18 September 2013 15:16:44 Pavel Machek wrote:
> On Sun 2013-09-08 02:02:52, Aaro Koskinen wrote:
> > Hi,
> >
> > On Fri, Sep 06, 2013 at 10:34:05PM +0200, Pali Rohár wrote:
> > > > --- /dev/null
> > > > +++ b/arch/arm/mach-omap2/board-rx51-camera.c
> >
> > [...]
> >
> > > Ping,
Dmitry Torokhov wrote:
>On Wed, Sep 18, 2013 at 10:39:42AM +0100, Jonathan Cameron wrote:
>>
>>
>> "Zubair Lutfullah :" wrote:
>> >On Tue, Sep 17, 2013 at 09:27:27PM -0700, Dmitry Torokhov wrote:
>> >> Hi Zubair,
>> >>
>> >> On Tue, Sep 17, 2013 at 09:44:07AM +0500, Zubair Lutfullah wrote:
On Wed, Sep 18, 2013 at 5:12 AM, Matt Fleming wrote:
> On Mon, 16 Sep, at 09:11:24PM, Roy Franz wrote:
>> Rename relocate_kernel() to efi_relocate_kernel(), and take
>> parameters rather than x86 specific structure. Add max_addr
>> argument as for ARM we have some address constraints that we
>>
On 09/17/2013 03:15 PM, Olof Johansson wrote:
> On Tue, Sep 17, 2013 at 2:08 PM, Frank Rowand wrote:
>> On 9/17/2013 9:43 AM, Olof Johansson wrote:
>>> On Tue, Sep 17, 2013 at 09:56:39AM +0200, Tomasz Figa wrote:
I'm afraid that I must disagree. For consistency I'd rather go with what
Hi,
On Wed, Sep 18, 2013 at 04:35:37PM +0200, Pavel Machek wrote:
> Hi!
>
> > > gave feedback. If the sender doesn't want to take his feedback into
> > > account and prefer to send pretty insulting emails instead that is his
> > > choice but I would say that is this not the greatest approach to
Resent due to Thunderbird completely mangling it the first time around:
On 09/07/2013 05:32 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest
> -next kernel, I've
> stumbled on the following:
>
> The disassembly is:
>
> /* Check
On Wed, Sep 18, 2013 at 05:53:44PM +0200, Jean Pihet wrote:
> This commit:
> 573145f08c2b92c45498468afbbba909f6ce6135
> clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE
>
> replaced a call to the driver's timer initialization by a call to
> clocksource_of_init(). However, it failed to
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
HEAD: 7bd36014460f793c19e7d6c94dab67b0afcfcb7f timekeeping: Fix HRTICK
related deadlock from ntp lock changes
An NTP related lockup
This patch adds to lm75 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the lm75 DT node. Otherwise, the driver
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
HEAD: 0f531431d3de88efb4234d6c0ce22089ec035a38 x86/intel/lpss: Add pin
control support to Intel low power subsystem
Misc fixes.
Thanks,
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
HEAD: 13b62e46d5407c7d619aea1dc9c3e0991b631b57 sched: Fix comment for
sched_info_depart
Misc fixes.
Thanks,
Ingo
This patch adds to tmp102 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the tmp102 DT node. Otherwise, the driver
From: Sudeep KarkadaNagesha
Hi,
This series adds cacheinfo support for ARM. The implementation is based on
x86. However it depends on device tree for cache hierarcy. On non-DT
platforms, first level caches are per-cpu while higher level caches are
assumed system-wide.
Few things I would like
From: Sudeep KarkadaNagesha
This patch adds initial support for providing processor cache information
to userspace through sysfs interface. This is based on x86 implementation
and hence the interface is intended to be fully compatible.
A per-cpu array of cache information maintained is used
On Wednesday 18 September 2013 08:58 PM, Stephen Warren wrote:
On 09/18/2013 07:22 AM, Laxman Dewangan wrote:
In place of hardcoding the key code in DTS file and comment the
key code as side notes, use the key code macro defines in the
dt-bindings/input/input.h directly.
I can apply this, but
The Samsung serial driver currently does not support setting the
RTS pin with an ioctl(TIOCMSET) call. This patch adds this support.
Changes in v2:
- Preserve the RTS pin's manual setting in set_termios() also when
enabling CRTSCTS.
Signed-off-by: José Miguel Gonçalves
---
This commit:
573145f08c2b92c45498468afbbba909f6ce6135
clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE
replaced a call to the driver's timer initialization by a call to
clocksource_of_init(). However, it failed to select CONFIG_CLKSRC_OF.
Fix this by selecting CONFIG_CLKSRC_OF for
On Wednesday 18 September 2013 15:57:13 Javier Martinez Canillas
wrote:
> to split the patch in two since the patch was solving
> two separate issues
My patch does not solving *two* issues. It is *one* regression
and both parts of patch are needed for fixing it. Read commit
message again. It
Hi,
I haven't got a reply in the past 2 weeks, so I would like to bump the
patch, just to make sure it haven't fell off the radar.
Zoli
On 04/09/13 21:11, Zoltan Kiss wrote:
Ftrace is currently not able to detect when SWIOTLB has to do double buffering.
Under Xen you can only see it
Hi Arnaldo,
Thanks for your work! I'm gonna be offline this week as it's one of
the biggest holyday in Korea (and other Asian countries). I'll catch
up next week.
--
Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Sep 18, 2013 at 06:18:02PM +0530, Laxman Dewangan wrote:
> The turn-on time of the regulator depends on the regulator device's
> electrical characteristics. Sometimes regulator turn-on time also
> depends on the capacitive load on the given platform and it can be
> more than the datasheet
The domain of Matt Mooneey's email doesn't exist anymore.
Setting usbip to Oprhan.
Signed-off-by: Tobias Polzer
Signed-off-by: Dominik Paulus
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index e61c2e8..5eb35c3 100644
---
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 6 of 7
>
> Introduce the fsflex driver.
> This driver is functionally equivalent to the farsync driver, and so
> can be used with the Generic HDLC, and ppp daemon.
>
> Signed-off-by:
This new subsystem should unify all fpga drivers which
do the same things. Load configuration data to fpga
or another programmable logic through common interface.
It doesn't matter if it is MMIO device, gpio bitbanging,
etc. connection. The point is to have the same
inteface for these drivers.
Em Wed, Sep 18, 2013 at 12:12:53PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
> > > On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > > >
On Tue, 2013-09-17 at 05:21 +0200, Michael Opdenacker wrote:
> This patch proposes to remove the TMS320C6X_CACHES_ON kernel configuration
> parameter defined in arch/c6x/Kconfig, but used nowhere
> in the makefiles and source code.
>
> Signed-off-by: Michael Opdenacker
> Acked by: Mark Salter
On Wed, 2013-09-18 at 17:56 +0200, Michal Simek wrote:
> This new subsystem should unify all fpga drivers which
> do the same things. Load configuration data to fpga
> or another programmable logic through common interface.
> It doesn't matter if it is MMIO device, gpio bitbanging,
> etc.
New version, now with excessive comments.
I found a deadlock (where both reader and writer would go to sleep);
identified below as case 1b.
The implementation without patch is reader biased, this implementation,
as Mel pointed out, is writer biased. I should try and fix this but I'm
stepping
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 5 of 7
> Note that this patch must be applied with patch 4 (farsync_include_patch)
>
> Update the current farsync driver to support all of the PCI and PCI X
> cards manufactured by
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 5 of 7
Please run your patches through checkpatch
total: 4178 errors, 6155 warnings, 9910 lines checked
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, Sep 18, 2013 at 10:19:32AM -0400, Vince Weaver wrote:
> Can you point to any code that is fixed by the commit?
I have some, but I don't think a lot of people use it.
Would you be ok with something like the below? It should preserve
functionality for code that only cares about
Clock source changes are never applied to the CMR register.
This may lead to wrong period/duty cycle configuration.
Signed-off-by: Boris BREZILLON
---
drivers/pwm/pwm-atmel-tcb.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pwm/pwm-atmel-tcb.c b/drivers/pwm/pwm-atmel-tcb.c
Hi Stan,
Thank you for the detailed review on this patch.
On 09/17/2013 05:55 PM, Stanimir Varbanov wrote:
Hi Georgi,
Thanks for the patch.
I have some commnets below.
On 09/16/2013 05:23 PM, Georgi Djakov wrote:
This platform driver adds the support of Secure Digital Host Controller
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 4 of 7
> Note that this patch must be applied with patch 5 (farsync_driver_patch)
Then don't make them separate patches.
> Update the existing farsync.h file for the new features of
On Mon, Sep 16, 2013 at 04:19:53PM +0100, Guenter Roeck wrote:
> On Mon, Sep 16, 2013 at 03:21:47PM +0100, Mark Rutland wrote:
> > On Thu, Sep 12, 2013 at 05:53:04PM +0100, Guenter Roeck wrote:
> > > On Thu, Sep 12, 2013 at 05:41:00PM +0100, Mark Rutland wrote:
> > > > On Fri, Aug 30, 2013 at
Hi Randy,
I've tried to download the .config file from the link on the forum,
but it tries to install something in my browser and the file is not
downloadable for me. Can you provide it over an simpler interface such
as pastebin.com?
Thanks
On Wed, Sep 18, 2013 at 4:59 PM, Randy Dunlap wrote:
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 3 of 7
>
> Introduce a new include file required by the fsflex driver.
>
> Signed-off-by: Kevin Curtis
>
> ---
>
> diff -uprN -X linux-3.10.1/Documentation/dontdiff
>
On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
> diff -uprN -X linux-3.10.1/Documentation/dontdiff
> linux-3.10.1/drivers/net/wan/fscmn.h linux-3.10.1_new/drivers/net/wan/fscmn.h
[]
> +#ifdef UINT32
> +#define u32 UINT32
> +#define u16
Use the the tcb counter width to compute the maximum time that can be
represented using the slow clock source instead of the static 16 bit width.
Signed-off-by: Boris BREZILLON
---
drivers/pwm/pwm-atmel-tcb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, 2013-09-18 at 11:11 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 2 of 7
>
> Introduce a new include file required by the fsflex driver.
>
> Signed-off-by: Kevin Curtis
>
> ---
>
> diff -uprN -X linux-3.10.1/Documentation/dontdiff
>
On 09/18/2013 07:22 AM, Laxman Dewangan wrote:
> In place of hardcoding the key code in DTS file and comment the
> key code as side notes, use the key code macro defines in the
> dt-bindings/input/input.h directly.
I can apply this, but aren't there many other Tegra DT files that need
conversion
Do you want me to merge this via my tree (cifs-2.6.git) or another?
On Mon, Sep 16, 2013 at 7:51 AM, Miklos Szeredi wrote:
> From: Miklos Szeredi
>
> If an error occurs after having called finish_open() then fput() needs to
> be called on the already opened file.
>
> Signed-off-by: Miklos
On Wednesday 18 September 2013 07:22 PM, Sricharan R wrote:
> Hi Thomas,
>
> On Tuesday 17 September 2013 05:56 PM, Linus Walleij wrote:
>> On Fri, Sep 13, 2013 at 4:24 PM, Thomas Gleixner wrote:
>>
>>> So why can't you make use of irq domains and have the whole routing
>>> business implemented
On 09/18/2013 06:48 AM, Laxman Dewangan wrote:
> The turn-on time of the regulator depends on the regulator device's
> electrical characteristics. Sometimes regulator turn-on time also
> depends on the capacitive load on the given platform and it can be
> more than the datasheet value.
>
> The
On Wed, 2013-09-18 at 11:11 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
[]
> diff -uprN -X linux-3.10.1/Documentation/dontdiff
> linux-3.10.1/drivers/net/wan/uss_cmn.h
> linux-3.10.1_new/drivers/net/wan/uss_cmn.h
> +typedef enum _USS_COMMANDS {
I think this code
> +#define printk(fmt, ...) do { \
> + compiletime_assert(__builtin_constant_p(fmt), \
> +"Non-constant format string"); \
> + printk(fmt, ##__VA_ARGS__); \
> +} while (0)
May I recommend
Don't use the same subject line for all your patches. This will be the
summary of the change in git and it needs to say what the individual
change does.
On Wed, 2013-09-18 at 11:11 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 1 of 7
>
> Add new FarSite PCI
On Wed, Sep 18, 2013 at 10:19:20AM -0500, Steve French wrote:
> Do you want me to merge this via my tree (cifs-2.6.git) or another?
It's in vfs.git#for-linus. I'll send a pull request later today...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Thomas,
On Friday 13 September 2013 10:55 AM, Santosh Shilimkar wrote:
> On Friday 13 September 2013 10:24 AM, Thomas Gleixner wrote:
[...]
>> Before you dig into MSI, lets talk about irq domains first.
>>
>> GIC implements a legacy irq domain, i.e. a linear domain of all
>> possible GIC
On Wed, 2013-09-18 at 13:00 +0400, Igor Gnatenko wrote:
> Since 136d8f377e1575463b47840bc5f1b22d94bf8f63 commit we have kernel
> panic on:
[...]
At a first glance, it looks like this bit is wrong:
> @@ -3058,13 +3090,17 @@ static struct sk_buff *skge_rx_get(struct net_device
> *dev,
>
A newline was accidentally added during session ID helper refactorization in
commit 4d3fb709. This needlessly uses up buffer space, messes up syslog
formatting and makes userspace processing less efficient. Remove it.
Signed-off-by: Richard Guy Briggs
---
kernel/audit.c |2 +-
1 files
Merged into cifs-2.6.git
On Mon, Sep 16, 2013 at 12:56 PM, Steve French wrote:
> On Mon, Sep 16, 2013 at 8:34 AM, David Howells wrote:
>>
>> Hi Steve,
>>
>> Could you pull a CIFS bugfix from my fscache branch?
>>
>> David
>
> Sounds fine. May have to wait a day or so though due to pending
Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
> > On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > > * Frederic Weisbecker wrote:
> > >> My patches and Namhyung's should improve the comm
Hello,
This patch series fix 2 bugs regarding the pwm configuration:
- the clock source of the timer channel is never applied
- the maximum time that can be represented when using the slow clock may be
wrong if the tc block provide a 32 bits width counter
Best Regards,
Boris
Boris
Nice. That should be of no interest for the outside world how much
junk 8042 contained, so that's better.
On Wed, Sep 18, 2013 at 6:44 PM, Dmitry Torokhov
wrote:
> Hi Andrey,
>
> On Wed, Sep 18, 2013 at 04:35:56PM +0400, Andrey Moiseev wrote:
>> When 8042 internal data buffer is full, the driver
On Wed, Sep 18, 2013 at 02:52:39PM +0100, Al Viro wrote:
> On Tue, Aug 27, 2013 at 07:48:43AM +0400, Andrew Savchenko wrote:
> > > Additional (but probably useless) information on this bug may be found
> > > here: https://forums.gentoo.org/viewtopic-p-7371120.html
>
> Something's very fishy
Hello Thomas,
On Wed, Sep 18, 2013 at 11:38:07AM +0200, Thomas Gleixner wrote:
> On Wed, 18 Sep 2013, Uwe Kleine-König wrote:
> > > Now we can easily verify whether the whole equation fits into the
> > > 64bit boundary. Shifting the "clc" result back by evt->shift MUST
> > > result in "latch". If
201 - 300 of 1160 matches
Mail list logo
