在 2015年06月07日 11:43, Doug Anderson 写道:
Caesar,
On Sat, Jun 6, 2015 at 7:51 PM, Caesar Wang wrote:
@@ -150,13 +159,15 @@ static int __cpuinit rockchip_boot_secondary(unsigned
int cpu,
* sram_base_addr + 4: 0xdeadbeaf
* sram_base_addr + 8: start address for
2015-06-07 11:50 GMT+09:00 Anand Moon :
>
> Hi Krzysztof
>
> Do you want me to resend this. Along with above.
>
> https://patchwork.kernel.org/patch/4420061/
> https://patchwork.kernel.org/patch/4420071/
If Vivek is not planning to continue to work on them then sure, please
take care of them and
Caesar,
On Sat, Jun 6, 2015 at 7:51 PM, Caesar Wang wrote:
> @@ -150,13 +159,15 @@ static int __cpuinit rockchip_boot_secondary(unsigned
> int cpu,
> * sram_base_addr + 4: 0xdeadbeaf
> * sram_base_addr + 8: start address for pc
> * */
> -
all,
On all my machines with Intel graphics I get the following warning
in the logs when the machine is suspended. Apparently some part of
the graphics system is busy when it should be idle. This is present
on the latest linux-next 20150604.
...
[ 33.141747] Suspending console(s) (use
在 2015年06月06日 04:55, Doug Anderson 写道:
Caesar,
On Fri, Jun 5, 2015 at 10:05 AM, Caesar Wang wrote:
+ if (!on)
+ reset_control_assert(rstc);
+
+ ret = regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), val);
+ if (ret < 0) {
+
On 30 May 2015 at 19:23, Anand Moon wrote:
> On 28 May 2015 at 14:49, Krzysztof Kozlowski wrote:
>> On 28.05.2015 17:58, Anand Moon wrote:
>>> Enable regulator for usbdrd3_0 and usbdrd3_1
From the schematic pin diagram USB3_0 and USB3_1
>>> is regulated by LDO9 and LD011.
>>
>> Please
On 7 June 2015 at 08:02, Krzysztof Kozlowski wrote:
> W dniu 29.05.2015 o 23:30, Anand Moon pisze:
>> Enable regulator for usbdrd3_0 and usbdrd3_1.
>> Looking at the schematic pin diagram for MAX77802
>> USB3_0 and USB3_1 is regulated by LDO9 and LD011.
>>
>> Fix the boot message of failed.
>> [
Hi
On 2015-06-07, Ville Syrjälä wrote:
> On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-04-20, Dave Airlie wrote:
> > [...]
> > > The following changes since commit
> > > 09d51602cf84a1264946711dd4ea0dddbac599a1:
> > >
> > > Merge branch
W dniu 29.05.2015 o 23:30, Anand Moon pisze:
> Enable regulator for usbdrd3_0 and usbdrd3_1.
> Looking at the schematic pin diagram for MAX77802
> USB3_0 and USB3_1 is regulated by LDO9 and LD011.
>
> Fix the boot message of failed.
> [3.503539] exynos-dwc3 usb@1200: Looking up
您好:
您还在用ali平台开发外贸客户?
还在使用展会宣传企业和产品?
你out了!!!
当前外贸客户开发难，您是否也在寻找展会，B2B之外好的渠道？
行业全球十几万客户，平时最多也就联系了三千家，您是否想把剩下的也开发到？
加QQ2821117472给您演示下主动开发客户的方法，先用先受益，已经有近万家企业领先您使用！！。
广东省商业联合会推荐，主动开发客户第一品牌，近万家企业正在获益。您可以没有使用，但是不能没有了解。
--
To unsubscribe from this list: send the line
Hello, Urgent Help/assistance needed Best Regards, Alanoud Alfayeza
--
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 read the FAQ at
Miklos Szeredi writes:
> On Fri, Jun 05, 2015 at 01:07:15AM +0100, Al Viro wrote:
>
>> Umm... Cosmetical point is that this
>>
>> > +static bool ovl_remote(struct dentry *root)
>> > +{
>> > + const struct dentry_operations *dop = root->d_op;
>> > +
>> > + return dop && (dop->d_revalidate ||
On 05/22/2015 05:13 PM, Tejun Heo wrote:
> Currently, a bdi (backing_dev_info) embeds single wb (bdi_writeback)
> and the role of the separation is unclear. For cgroup support for
> writeback IOs, a bdi will be updated to host multiple wb's where each
> wb serves writeback IOs of a different
This fixes bitwise arithmetic performed on the host on a variable
previously converted to little-endian, and subsequently converted
again to little-endian:
- issue_action_BA23a() called with "status" crafted in host byte order
- "status" converted to LE
- bitwise arithmetic on the (LE)
Source and destination have the same little-endian annotation: this
patch removes forced conversion from host byte order to little-endian.
This addresses the following sparse warning:
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:3911:56: warning: incorrect type
in argument 1 (different base
The code shows a couple inconsistencies (described in commit
descriptions) which would not be an issue on little-endian cpus, but
could cause breakage on non-LE cpus. Note: I could not test on real
hardware, these patches created based on sparse reports.
Клиентские базы тел +79133913837 Email: lidiaakse...@gmail.com
Klientskie bazi tel +79133913837 Email: lidiaakse...@gmail.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 Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-04-20, Dave Airlie wrote:
> [...]
> > The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
> >
> > Merge branch 'turbostat' of
> >
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-4.1-rc7
for you to fetch changes up to
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.1-rc7
for you to fetch changes up to
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.1-rc7
for you to fetch changes up to
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.1-rc7
for you to fetch changes up to
On 14/08/2013 at 11:11:21 +0200, Julia Lawall wrote :
> From: Julia Lawall
>
> Remove unneeded error handling on the result of a call to
> platform_get_resource when the value is passed to devm_ioremap_resource.
>
> Move the call to platform_get_resource adjacent to the call to
>
Hi Linus,
Stupid type fix follows. Please pull.
g.
The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f3d:
Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/glikely/linux.git
I am experiencing a similar issue on another system (at91sam9n12) that
uses Redpine Signal Wireless Driver 1.1.0. I do not know the root
cause yet, but it may be related to the Redpine Signals driver. Will
update this mailing list if the problem is with the redpine driver.
thanks
On Thu, May
On 06/07, Jiri Kosina wrote:
>
> On Sun, 7 Jun 2015, Oleg Nesterov wrote:
>
> > > I personally don't see a huge principal difference between
> > > "kthread_signal_dequeue() + kthread_do_signal_{stop,...}" vs. generic
> > > "kthread_do_signal()" that's just basically completely general and
> > >
> This commit introduces a regression relative to v4.0 on an Intel
> D945GCLF2 mainboard[1] (Atom 330) with Intel 82945G/GZ onboard graphics
> using its (only-) VGA connector for me.
>
Jani any ideas/plans?
Dave.
> v4.1-rc6-52-gff25ea8:
> [ 13.265699] BUG: unable to handle kernel NULL pointer
On 20 February 2015 at 11:14, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel, I've stumbled on the following spew:
Sasha, can you test the patch titled "hfsplus: release bnode pages
after use, not before" I have just sent to
On Sun, 7 Jun 2015, Oleg Nesterov wrote:
> > > Still I personally dislike the new kthread_sigaction() API. I agree,
> > > a couple if signal helpers for kthreads make sense. Say,
> > >
> > > void kthread_do_signal_stop(void)
> > > {
> > > spin_lock_irq(>sighand->siglock);
> > >
On 06/06, Jiri Kosina wrote:
>
> On Sat, 6 Jun 2015, Oleg Nesterov wrote:
>
> > Still I personally dislike the new kthread_sigaction() API. I agree,
> > a couple if signal helpers for kthreads make sense. Say,
> >
> > void kthread_do_signal_stop(void)
> > {
> >
Currently, watchdog subsystem require the misc subsystem to
register a watchdog. This may not be the case in case of an
early registration of a watchdog, which can be required when
the watchdog cannot be disabled.
This patch introduces a deferral mechanism to remove this requirement.
In some situation, mainly when it's not possible to disable a
watchdog, you may want the watchdog driver to be started as soon
as possible.
Adding GPIO_WATCHDOG_ARCH_INITCALL to raise initcall from
module_init to arch_initcall.
This patch require watchdog registration deferral mechanism
Hello.
On 06/07/2015 12:09 AM, Robert Jarzmik wrote:
The pxa27x SoCs have an embedded camera host controller. Add the
description to the family description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 17 +
1 file changed, 17 insertions(+)
diff
Hi,
may I ask for review of the following patch. I would like particular feedback
to the initial threshold value, which the patch currently sets to 50 (requests
by a caller to the DRBG for random numbers). Thank you.
I am not sure about this value because there are two conflicting issues
On 06/05, Petr Mladek wrote:
>
> The main question is how much it should follow POSIX and the signal
> handling of user space processes. On one hand, we want to be as close
> as possible.
Why? Let the kthread decide what it should if it gets, say, SIGSTOP.
> Finally, kthread_do_signal() is
--
MONEY GRAM SENT THE SUM OF $2900 TO YOU.REF #:9257-8487 kindly contact MR.PAUL
HOWARD FOR MORE DETAILS.
--
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
And, for interest's sake, I went to a somewhat older machine: a 2008
MSI K9A2 platinum with DDR2, a Socket 939 AMD processor, SB600 south
bridge and (most importantly for this) a Fintek F71882FG super-IO
chip providing the PIT and RTC.
Anyway, the results are similar, again with the RTC being
On Sat, 6 Jun 2015, Oleg Nesterov wrote:
> Still I personally dislike the new kthread_sigaction() API. I agree,
> a couple if signal helpers for kthreads make sense. Say,
>
> void kthread_do_signal_stop(void)
> {
> spin_lock_irq(>sighand->siglock);
> if
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
>> Hi Guennadi,
>>
>> I've been cooking this since 2012. At that time, I thought the dmaengine API
>> was
>> not rich enough to support the pxa_camera subtleties (or complexity).
>>
>> I was wrong. I submitted a driver to Vinod for a dma pxa
On 06/05, Petr Mladek wrote:
>
> [*] In fact, there was a bug in the original code. It tried to process
> a non-existing signal when the system was freezing. See the common
> check for pending signal and freezing.
And another bug afaics:
> - case SIGSTOP:
> -
From: Daniel Mack
Switch over pxamci to dmaengine. This prepares the devicetree full
support of pxamci.
This was successfully tested on a PXA3xx board, as well as PXA27x.
Signed-off-by: Daniel Mack
[adapted to pxa-dma]
Signed-off-by: Robert Jarzmik
---
drivers/mmc/host/pxamci.c | 200
Add the correct address and size to the device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 9ebfd7f..94cf80f 100644
---
The pxa27x SoCs have an embedded camera host controller. Add the
description to the family description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi
Add the 3 possible mmc controllers on pxa3xx SoCs to the devicetree
description. Add the dma and clocks to the device-tree description of
pxa27x and pxa3xx at the same time.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 4
arch/arm/boot/dts/pxa3xx.dtsi | 33
Add the usb host controller to pxa27x and pxa3xx.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
arch/arm/boot/dts/pxa3xx.dtsi | 8
2 files changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index
In order to slowly transition pxa to dmaengine, the legacy code will now
rely on dmaengine to request a channel.
This implies that PXA architecture selects DMADEVICES and PXA_DMA,
which is not pretty. Yet it enables PXA drivers to be ported one by one,
with part of them using dmaengine, and the
Add the dma client description for pxa3xx-nand to use its dma through
device-tree.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa3xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa3xx.dtsi b/arch/arm/boot/dts/pxa3xx.dtsi
index 4eb1563..d90489b 100644
Add the SoC embedded DMA controller, shared with the mmp architecture.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
arch/arm/boot/dts/pxa3xx.dtsi | 9 +
2 files changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi
06.06.2015 20:25, Dmitry Tunin пишет:
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu added to
/lib/firmware/ar3k/ that are not included in linux-firmware yet.
T: Bus=03 Lev=01 Prnt=01 Port=09 Cnt=06
Add a GPIO driver for the General I/O block on Axis ETRAX FS SoCs.
Signed-off-by: Rabin Vincent
---
v3: Move port number to last cell and use of_gpio_simple_xlate().
.../devicetree/bindings/gpio/gpio-etraxfs.txt | 21 +++
drivers/gpio/Kconfig | 8 +
On 06/03/2015 09:56 AM, Daniel Baluta wrote:
On Thu, May 28, 2015 at 5:17 PM, Daniel Baluta wrote:
+static const struct iio_chan_spec rpr0521_channels[] = {
+ {
+ .type = IIO_INTENSITY,
+ .modified = 1,
+ .address = RPR0521_CHAN_ALS_DATA0,
+
In order to support multi ic type for i2c/smbus protocol, add get ic type
command and check fw vaild page count and signature address function.
Signed-off by: Duson Lin
---
drivers/input/mouse/elan_i2c.h |5 ++--
drivers/input/mouse/elan_i2c_core.c | 44
Congrats! Your Email has Won £1,000,000.00 in the Guinness 2015 Email
Award. For Claims,send #:GUI45856CS89 and the below details to the claims
agent via Email: gboar...@yahoo.com.hk
1). Legitimate Name:
2). Mobile Number:
3). Residential Address/Country:
4). Age:
5). Occupation:
--
To
CC-ing author of below reply
On Sat, Jun 6, 2015 at 8:53 PM, Belisko Marek wrote:
> On Sat, Jun 6, 2015 at 3:09 PM, Pavel Machek wrote:
>> Hi!
>>
>>> None was ?wonderful?. They were valid concerns about my proposal
>>> and I have replied to them how I see it.
>>>
>>> Generally, if you are not
On Sat, Jun 6, 2015 at 3:09 PM, Pavel Machek wrote:
> Hi!
>
>> None was ?wonderful?. They were valid concerns about my proposal
>> and I have replied to them how I see it.
>>
>> Generally, if you are not interested in people dedicated and committed to
>> fight for the better solution with
Le 06/06/2015 17:32, Rob Herring a écrit :
On Sat, Jun 6, 2015 at 6:20 AM, christophe leroy
wrote:
I've got a MPC8323 RDB evaluation platform from freescale
kernel 4.0 doesn't boot
kernel 3.16 doesn't boot
kernel 3.15 boots ok
I disected the issue down to your commit "of/fdt: Convert FDT
On Fri, Jun 5, 2015 at 11:27 AM, Valentin Rothberg
wrote:
> The CONFIG_ prefix is reserved for Kconfig options in Make and CPP
> syntax. Various static analysis tools rely on this naming convention
> and check if CONFIG_ prefixed symbols are defined Kconfig. Hence add
> yet another prefix AMD_
BugLink: https://bugs.launchpad.net/bugs/1427680
This device requires new firmware files
AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu added to
/lib/firmware/ar3k/ that are not included in linux-firmware yet.
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu added to
/lib/firmware/ar3k/ that are not included in linux-firmware yet.
T: Bus=03 Lev=01 Prnt=01 Port=09 Cnt=06 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 1.10
Bringing up my question one more time since it may be lost in the high
volume of messages.
Hope to receive an idea...
On 6/6/15, Mahmood Naderan wrote:
> Hi Guys,
> My first question is, does the version of kernel affects the perf
> functionality? I mean fixing bugs and ...
> Currently, the
On 06/06/2015 12:46 AM, Jean-Baptiste Theou wrote:
In some situation, mainly when it's not possible to disable a
watchdog, you may want the watchdog driver to be started as soon
as possible.
Adding GPIO_WATCHDOG_ARCH_INITCALL to raise initcall from
module_init to arch_initcall.
This patch
On Sat, Jun 06, 2015 at 09:13:39PM +0800, Wan ZongShun wrote:
> Change AMD CZ SMBUS device ID from 0x790b to
> use Macro definition
>
> Signed-off-by: Wan ZongShun
> Signed-off-by: Wan ZongShun
Same here, one SOB per person please.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails
On Sat, Jun 06, 2015 at 09:13:38PM +0800, Wan ZongShun wrote:
> The KERNCZ is new AMD SB/FCH generation name, like HUDSON2.
> We will adopt 0x790b as device ID since from this gereration.
>
> Signed-off-by: Wan ZongShun
> Signed-off-by: Wan ZongShun
You need to choose one email address, not
On 06/06/2015 12:46 AM, Jean-Baptiste Theou wrote:
Currently, watchdog subsystem require the misc subsystem to
register a watchdog. This may not be the case in case of an
early registration of a watchdog, which can be required when
the watchdog cannot be disabled.
This patch introduces a
I'm announcing the release of the 3.14.44 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index e26cb1e56266..067433219984 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 10
-SUBLEVEL = 79
+SUBLEVEL = 80
EXTRAVERSION =
NAME = TOSSUG Baby Fish
@@ -241,7 +241,7 @@ CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo
diff --git a/Makefile b/Makefile
index ae5f1e62812f..9f2471c6fbbe 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 14
-SUBLEVEL = 43
+SUBLEVEL = 44
EXTRAVERSION =
NAME = Remembering Coco
@@ -244,7 +244,7 @@ CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo
I'm announcing the release of the 4.0.5 kernel.
All users of the 4.0 kernel series must upgrade.
The updated 4.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.0.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.10.80 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
On Fri, Jun 5, 2015 at 11:58 PM, Dave Airlie wrote:
>
> i915 has a bunch of fixes [..]
.. but nof ix for the regression that Stefan Lippers-Hollmann
reported? An oops in intel_modeset_update_connector_atomic_state() due
to commit 08d9bc920d46 ("drm/i915: Allocate connector state together
with
Thanks for the feedback.
I tested a version before cleanup, and the mistake was introduce during it.
It's my mistake, sorry about that. Will fix it on v4.
On Sat, 6 Jun 2015 16:11:18 +0200
Paul Bolle wrote:
> On Sat, 2015-06-06 at 14:56 +0200, Valentin Rothberg wrote:
> > On Sat, Jun 06, 2015
On Fri, Jun 5, 2015 at 11:24 AM, Al Viro wrote:
>
> Yes, but... if we decrement that sucker at all, why do we need to play with
> i at all? We need exactly nr_compat_longs get_user(), so why not make _that_
> the condition in the single-level loop?
Yeah, I think that code could be clarified
2015-06-06 19:11 GMT+03:00 Richard Weinberger :
> On Sat, Jun 6, 2015 at 5:49 PM, Matwey V. Kornilov wrote:
>> mach-dependant stuff has been removed by
>>2eb2478d471e45e1d0c8bb3defbf82bf7204e13d
>>
>> There is no need to keep
>> depends on ARCH_DAVINCI_DA850
>
> The driver dependencies
On Thu, Jun 4, 2015 at 12:17 AM, H. Peter Anvin wrote:
> On 06/01/2015 05:45 PM, Len Brown wrote:
>>
>> BTW, it also begs the question if Linux could actually *repair* the BIOS
>> damage?
>>
>
> We may very well be able to by setting the TSC offset register to zero
> on all CPUs.
What TSC
On Sat, Jun 6, 2015 at 5:49 PM, Matwey V. Kornilov wrote:
> mach-dependant stuff has been removed by
>2eb2478d471e45e1d0c8bb3defbf82bf7204e13d
>
> There is no need to keep
> depends on ARCH_DAVINCI_DA850
The driver dependencies are still broken.
It needs ioremap(), hence make it depend
On Thu, Jun 4, 2015 at 11:52 PM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> On Thu, Jun 4, 2015 at 4:32 PM, Andy Lutomirski wrote:
>>
>> > AFAICT the sole purpose for the hideous x86_64 idle_notifier mess is to
>> > support i7300_idle. IMO this junk does not belong in IRQ handling,
On Sat 2015-06-06 15:42:28, Pali Rohár wrote:
> Signed-off-by: Pali Rohár
Acked-by: Pavel Machek
And thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
uio_pruss references SZ_16K and SZ_256K defines, but linux/sizes.h is not
included.
Signed-off-by: Matwey V. Kornilov
---
Changes from v1:
- Add uio: pruss: Include patch to allow build on all
architectures
drivers/uio/uio_pruss.c | 1 +
1 file changed, 1 insertion(+)
diff --git
mach-dependant stuff has been removed by
2eb2478d471e45e1d0c8bb3defbf82bf7204e13d
There is no need to keep
depends on ARCH_DAVINCI_DA850
Signed-off-by: Matwey V. Kornilov
---
drivers/uio/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/uio/Kconfig b/drivers/uio/Kconfig
On Sat, Jun 6, 2015 at 6:20 AM, christophe leroy
wrote:
> I've got a MPC8323 RDB evaluation platform from freescale
> kernel 4.0 doesn't boot
> kernel 3.16 doesn't boot
> kernel 3.15 boots ok
>
> I disected the issue down to your commit "of/fdt: Convert FDT functions to
> use libfdt"
On Sat, Jun 6, 2015 at 8:29 AM, Stefan Agner wrote:
> On 2015-06-06 14:48, Russell King - ARM Linux wrote:
>> On Sat, Jun 06, 2015 at 02:31:28PM +0200, Stefan Agner wrote:
>
>>> --- a/arch/arm/include/asm/fixmap.h
>>> +++ b/arch/arm/include/asm/fixmap.h
>>> @@ -6,9 +6,13 @@
>>> #define
On Fri, 2015-06-05 at 14:38 +0200, Thomas Gleixner wrote:
> On Tue, 19 May 2015, Davidlohr Bueso wrote:
>
> > Avoid unnecessary cmpxchg calls, all of our other locks
> > use it as well.
> >
> > Signed-off-by: Davidlohr Bueso
> > ---
> > kernel/locking/rtmutex.c | 4 +++-
> > 1 file changed, 3
My understanding is that this patch is trying to fix bugs in this commit:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.10.y=5f03ac13d87590b0ee879c77e68df63a3d9b3e07
The 3.10.y branch applied the original patch to three different places.
Quote from
This patch fix a spelling typo in ja_JP/HOWTO.
Signed-off-by: Masanari Iida
---
Documentation/ja_JP/HOWTO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ja_JP/HOWTO b/Documentation/ja_JP/HOWTO
index b61885c..5a0f2bd 100644
--- a/Documentation/ja_JP/HOWTO
+++
On Fri, Jun 05, 2015 at 04:27:48PM -0700, Dennis Chen wrote:
> >From 843d038eec5ac2c59d3138f19ae52828098c7d50 Mon Sep 17 00:00:00 2001
> From: Dennis Chen
> Date: Fri, 5 Jun 2015 15:42:37 -0700
> Subject: [PATCH] Staging: comedi: daqboard2000: fixed whitespace coding style
> issue
Sudip is
Send the patch to yourself. Apply it with git am. Review the git log
and then send it to the list.
But actually this change is not correct at all. The prefered style in
staging is that multi-line indent blocks get curly braces for
readability even when they are not required by the compiler.
On Sat, 2015-06-06 at 14:56 +0200, Valentin Rothberg wrote:
> On Sat, Jun 06, 2015 at 12:03:06PM +0200, Paul Bolle wrote:
> > On Sat, 2015-06-06 at 00:46 -0700, Jean-Baptiste Theou wrote:
> > > +#ifdef GPIO_WATCHDOG_ARCH_INITCALL
> >
> > You meant
> > #ifdef CONFIG_GPIO_WATCHDOG_ARCH_INITCALL
kmemleak reported memory leak in kasan_module_alloc() like following
log, even through kasan_free_shadow() frees that address.
unreferenced object 0xfbfff40ac000 (size 118784):
comm "modprobe", pid 196, jiffies 4294878847 (age 87.590s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00
Signed-off-by: Pali Rohár
---
Documentation/laptops/.gitignore |1 -
Documentation/laptops/00-INDEX |2 --
Documentation/laptops/Makefile |2 +-
tools/Makefile | 14 --
... to ipc_obtain_object_idr, which is more meaningful
and makes the code slightly easier to follow.
Signed-off-by: Davidlohr Bueso
---
ipc/msg.c | 2 +-
ipc/sem.c | 4 ++--
ipc/shm.c | 2 +-
ipc/util.c | 8
ipc/util.h | 2 +-
5 files changed, 9 insertions(+), 9 deletions(-)
diff
The ipc_lock helper is used by all forms of sysv ipc to acquire
the ipc object's spinlock. Upon error (bogus identifier), we
always return -EINVAL, whether the problem be in the idr path or
because we raced with a task performing RMID. For the later,
however, all ipc related manpages, state the
We currently use a full barrier on the sender side to
to avoid receiver tasks disappearing on us while still
performing on the sender side wakeup. We lack however,
the proper CPU-CPU interactions pairing on the receiver
side which busy-waits for the message. Similarly, we do
not need a full
Upon every shm_lock call, we BUG_ON if an error was returned,
indicating racing either in idr or in shm_destroy. Move this logic
into the locking.
Signed-off-by: Davidlohr Bueso
---
ipc/shm.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/ipc/shm.c b/ipc/shm.c
In ipc_obtain_object_check we return -EIDRM when a bogus
sequence number is detected via ipc_checkid, while the ipc
manpages state the following return codes for such errors:
EIDRM points to a removed identifier.
EINVAL Invalid value, or unaligned, etc.
EIDRM should only be returned
Hello,
Patches 1,2: Are a resend, I've incorporated them to the set,
based on Manfred's comments.
Patch 3: is a trivial function rename.
Patches 4,5: are attempts to order how Linux ipc deals with EIDRM
and EINVAL return error codes. By looking at corresponding manpages
two possible inverted
On Fri 2015-06-05 08:07:38, Joe Perches wrote:
> On Fri, 2015-06-05 at 12:37 +0200, Pavel Machek wrote:
> > On Thu 2015-06-04 11:36:48, Joe Perches wrote:
> > > Instead of a two individual printks that would generally be
> > > emitted on a single line, emit 2 lines to make the start
> > > and end
On Fri, Jun 5, 2015 at 9:40 PM, Fabian Frederick wrote:
> All filesystems use Opt_ prefix for match_table_t enums
And needs hfsplus this patch?
It should not matter whether a filesystem is using opt_ or Opt_.
--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe
On 2015-06-06 14:48, Russell King - ARM Linux wrote:
> On Sat, Jun 06, 2015 at 02:31:28PM +0200, Stefan Agner wrote:
>> --- a/arch/arm/include/asm/fixmap.h
>> +++ b/arch/arm/include/asm/fixmap.h
>> @@ -6,9 +6,13 @@
>> #define FIXADDR_TOP (FIXADDR_END - PAGE_SIZE)
>>
>> #include
>>
On Sat, Jun 6, 2015 at 12:24 AM, Jarod Wilson wrote:
> Its possible for users to specify their own MAC address for a bonded link,
> and this used to work, until sometime in 2013...
>
> First, commit 409cc1f8a changed a condition to set the bond's mac to a
> slave device's, dropping the
The KERNCZ is new AMD SB/FCH generation name, like HUDSON2.
We will adopt 0x790b as device ID since from this gereration.
Signed-off-by: Wan ZongShun
Signed-off-by: Wan ZongShun
---
include/linux/pci_ids.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/pci_ids.h
1 - 100 of 326 matches
Mail list logo
