On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
> Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
> Most modesetting drivers enable provide fbdev emulation by default by
> selecting
> KMS FB helpers. A few provide a separate Kconfig option for the user to
On Sun, Mar 08, 2015 at 07:49:58PM +0100, Stephan Mueller wrote:
> The RFC4106 GCM decryption operation tries to overwrite cryptlen memory
> in req->dst. As the destination buffer for decryption only needs to hold
> the plaintext memory but cryptlen references the input buffer holding
>
When using the user mode helper to load firmwares the function _request_firmware
gets a positive return value from fw_load_from_user_helper and because of this
the firmware buffer is not assigned. This happens only when the return value
is zero. This patch fixes this problem in
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
> Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
> Most modesetting drivers enable provide fbdev emulation by default by
> selecting
> KMS FB helpers. A few provide a separate Kconfig option for the user to
removed some functions which were not being used anywhere.
build tested and also verified by git grep that there is no other
reference to these functions.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/rtl8192e/rtl819x_HTProc.c | 154 --
DRM_MSM_FBDEV config is used to enable/disable fbdev emulation for the msm kms
driver.
Replace this with the top level DRM_FBDEV_EMULATION config option where
applicable. This also prevents build breaks caused by undefined drm_fb_helper_*
functions when legacy fbdev support was disabled.
Hi Philipp,
Am Dienstag, 10. März 2015, 10:16:53 schrieb Philipp Zabel:
[cut the obvious stuff I need to fix]
> Am Dienstag, den 10.03.2015, 00:22 +0100 schrieb Heiko Stuebner:
> > @@ -879,6 +883,12 @@ static int dw_hdmi_phy_init(struct dw_hdmi *hdmi)
> >
> > int i, ret;
> > bool cscon
+Cc James Liao
On Mon, Mar 09, 2015 at 02:35:03PM -0700, Kevin Hilman wrote:
> Sascha Hauer writes:
>
> > Signed-off-by: Sascha Hauer
>
> A bit of a changelog here would be useful describing this driver, that
> it's only covering part of the device (e.g. power controller) with more
> to
DRM_STI_FBDEV config is currently used to enable/disable fbdev emulation for
the sti kms driver.
Remove this local config option and use the top level DRM_FBDEV_EMULATION config
option instead where applicable.
We replace the #ifdef in sti_drm_load with CONFIG_DRM_FBDEV_EMULATION. It's
probably
DRM_TEGRA_FBDEV config is currently used to enable/disable fbdev emulation for
the tegra kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config lets us also prevent wrapping around drm_fb_helper_* calls with #ifdefs
in certain places.
The #ifdef in
DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
the i915 kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config lets us also prevent wrapping around drm_fb_helper_* calls with #ifdefs
in certain places.
The #ifdef in
On 10/03/2015 at 10:02:15 +0100, Arnd Bergmann wrote :
> On Monday 09 March 2015 23:59:58 Brian Norris wrote:
> > @@ -114,6 +114,12 @@ config SOC_AT91SAM9
> > AT91SAM9XE
> > endif # SOC_SAM_V4_V5
> >
> > +config MACH_AT91_AUTO
> > + def_bool y
> > + depends on
DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation for
the imx kms driver.
Remove this local config option and use the top level DRM_FBDEV_EMULATION config
option where applicable. Using this config lets us also prevent wrapping around
drm_fb_helper_* calls with #ifdefs
This provides a uniform interface to enable/disable legacy fbdev support for
modesetting drivers, based on the discussion here:
http://lists.freedesktop.org/archives/dri-devel/2015-March/078729.html
This has only been build-tested for a few devices. Mainly looking for comments
for now.
The
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide a separate Kconfig option for the user to enable
or disbale fbdev emulation.
Enabling fbdev emulation is finally
If I plug in my USB DVB-T stick I get the following in dmesg:
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
On Tue, Mar 10, 2015 at 10:34:31AM +0100, Jiri Kosina wrote:
> Thanks a lot for fixing my oversight.
Bah, it was my suggestion to use setup_data in the first place, sorry
about that.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list:
Final patch:
---
From: Yinghai Lu
Date: Sat, 7 Mar 2015 14:07:17 -0800
Subject: [PATCH] x86/setup: Don't overlap vmlinux's brk with compressed
kernel's data
We already do move the compressed kernel close to the end of the buffer.
However, there's still overlapping beween kernel proper's
On Mon, 2015-03-09 at 15:36 +0100, Mike Galbraith wrote:
> On Mon, 2015-03-09 at 14:45 +0100, Sebastian Andrzej Siewior wrote:
> > * Mike Galbraith | 2015-02-18 12:21:54 [+0100]:
> >
> > >On Mon, 2015-02-16 at 12:18 +0100, Sebastian Andrzej Siewior wrote:
> > >
> > >> Known issues:
> > >>
> > >>
On 2015年03月09日 23:01, Liviu Dudau wrote:
On Wed, Feb 25, 2015 at 08:39:48AM +, Hanjun Guo wrote:
CONFIG_ACPI depends CONFIG_PCI on x86 and ia64, in ARM64 server
world we will have PCIe in most cases, but some of them may not,
make CONFIG_ACPI depend CONFIG_PCI on ARM64 will satisfy both.
On Tue, 10 Mar 2015, Borislav Petkov wrote:
> Final patch:
>
> ---
> From: Yinghai Lu
> Date: Sat, 7 Mar 2015 14:07:16 -0800
> Subject: [PATCH] x86/setup: Move compressed kernel to the end of the buffer
[ ... ]
> Signed-off-by: Yinghai Lu
> Cc: "H. Peter Anvin"
> Cc: Matt Fleming
> Cc: Kees
Hi Mark,
I got a device which registers are arranged in 'books' and pages:
book0
page0
page1
...
page127
book1
page0
page1
...
page127
...
book255
page0
page1
...
page127
The pages can be selected via register0 of each page (in a standard way),
however the book switching can only be
On Tue, Mar 10, 2015 at 08:01:16AM +, Hanjun Guo wrote:
[...]
> >> diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h
> >> new file mode 100644
> >> index 000..8b837ab
> >> --- /dev/null
> >> +++ b/arch/arm64/include/asm/acpi.h
> >> @@ -0,0 +1,45 @@
> >> +/*
> >>
Hi Arnd,
Am Montag, den 09.03.2015, 22:56 +0100 schrieb Arnd Bergmann:
> On Monday 09 March 2015 11:26:52 Yingjoe Chen wrote:
> > On Fri, 2015-03-06 at 18:48 +0800, yong...@mediatek.com wrote:
> > > From: Yong Wu
> > >
> > > This patch add SMI(Smart Multimedia Interface) driver. This driver
On 2015年03月07日 02:31, Lorenzo Pieralisi wrote:
On Wed, Feb 25, 2015 at 08:39:48AM +, Hanjun Guo wrote:
[...]
diff --git a/arch/arm64/kernel/pci.c b/arch/arm64/kernel/pci.c
index 6f93c24..4095379 100644
--- a/arch/arm64/kernel/pci.c
+++ b/arch/arm64/kernel/pci.c
@@ -10,6 +10,7 @@
*
My wife and I have awarded you with a donation of $ 1.5 million Dollars from
part of our Jackpot Lottery of 161,653,000 Million Pounds, send your
name,address, phone for claims.
View http://www.bbc.co.uk/news/uk-scotland-glasgow-west-18801698
We await your earliest response and God Bless you.
On Tue, Mar 10, 2015 at 09:31:09AM +0100, Uwe Kleine-König wrote:
> ---
> drivers/tty/serial/imx.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Same errors as your other patch :(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Tue, Mar 10, 2015 at 09:23:18AM +0100, Uwe Kleine-König wrote:
> Hello Greg,
>
> On Tue, Mar 10, 2015 at 04:28:16PM +1100, Stephen Rothwell wrote:
> > After merging the tty tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> >
> > drivers/tty/serial/imx.c: In
On Tue, Mar 10, 2015 at 09:29:51AM +0100, Uwe Kleine-König wrote:
> ---
> drivers/tty/serial/serial_mctrl_gpio.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
No changelog comment, no signed-off-by: and some odd "fixup!" in the
subject line :(
Please fix and resend so that I can
Hi Heiko,
Am Dienstag, den 10.03.2015, 00:22 +0100 schrieb Heiko Stuebner:
> diff --git a/Documentation/devicetree/bindings/drm/bridge/dw_hdmi.txt
> b/Documentation/devicetree/bindings/drm/bridge/dw_hdmi.txt
> index a905c14..bb74640 100644
> ---
On 10 March 2015 at 08:59, Dan Carpenter wrote:
>
> The patch is:
>
> [patch] cleanup the type of mmio750
>
> silencing a Sparse warning is just a side benifit of using correct
> data types. The "one thing per patch" rule also means that you should
> fix a whole problem instead of half a thing
Hi Ivan,
Sorry for the late reply. I think I addressed some points in other
replies already, but for completeness let me reply to this post too.
Le Wednesday 04 March 2015 à 14:30 +0200, Ivan.khoronzhuk a écrit :
> On 02/26/2015 11:36 AM, Jean Delvare wrote:
> > On Wed, 4 Feb 2015 19:06:03
Am Dienstag, den 10.03.2015, 00:21 +0100 schrieb Heiko Stuebner:
> At least the Rockchip variant of the dw_hdmi should control its supplying
> regulators. A cursory glance at the imx manual didn't any equivalent there,
> so I'm not sure if there are similar controllable regulators present.
On
On Tuesday 10 March 2015 14:27:04 Yingjoe Chen wrote:
> On Mon, 2015-03-09 at 22:56 +0100, Arnd Bergmann wrote:
> > On Monday 09 March 2015 11:26:52 Yingjoe Chen wrote:
> > > On Fri, 2015-03-06 at 18:48 +0800, yong...@mediatek.com wrote:
> > > > From: Yong Wu
> > > >
> > > > This patch add
At the context where we have pointer to struct phy, it's useful to call
phy_get_drvdata() to get the address of priv. With this change, we can
remove the to_phy_berlin_usb_priv() macro and remove *phy from struct
phy_berlin_usb_priv.
Signed-off-by: Axel Lin
---
drivers/phy/phy-berlin-usb.c | 14
On Monday 09 March 2015 23:59:58 Brian Norris wrote:
> @@ -114,6 +114,12 @@ config SOC_AT91SAM9
> AT91SAM9XE
> endif # SOC_SAM_V4_V5
>
> +config MACH_AT91_AUTO
> + def_bool y
> + depends on !SOC_AT91SAM9 && !SOC_SAMA5D4
> + select SOC_SAMA5D3 if SOC_SAM_V7
> +
Allow prefetch settings overriding by device tree, in case
l2x0_cache_size_of_parse() returns value, prefetch tuning
properties are silently ignored. E.g. arm,double-linefill* and
arm,prefetch*.
This happens for example, when "cache-size" or "cache-sets"
properties haven't been filled in l2c dt
On Tue, Mar 10, 2015 at 08:47:47AM +, Lorenzo Stoakes wrote:
> On 10 March 2015 at 07:00, Dan Carpenter wrote:
>
> > No need for the volatile.
>
> Will remove.
>
> > Really mmio750 should be a "void __iomem *"
> > it is declared as "unsigned char __iomem *" but it's not a char pointer
> >
On 12-01-15 04:04, Mike Turquette wrote:
On Thu, Jan 8, 2015 at 11:01 PM, Mike Looijmans wrote:
Just a ping to inform if you've had had time to look at this?
Its in the queue for review this week. A lot to catch up on after the
holidays. Thanks for the ping.
Just another ping, you haven't
On 03/10/2015 07:11 AM, joeyli wrote:
<>
>
> Per my understand...
>
> With EFI Boot Stub, there have setup_e820() codes in
> arch/x86/boot/compressed/eboot.c
> that used to transfer EFI memmap to e820 entries. Currently doesn't have any
> EFI_MEMORY_TYPE reflects to NvDIMM that will map to
This patch fixes the following sparse warning:-
drivers/staging/sm750fb/ddk750_help.c: warning: incorrect type in assignment
(different address spaces)
In addition it eliminates an unnecessary volatile.
Signed-off-by: Lorenzo Stoakes
---
drivers/staging/sm750fb/ddk750_chip.h | 4 +++-
On 10 March 2015 at 07:00, Dan Carpenter wrote:
> No need for the volatile.
Will remove.
> Really mmio750 should be a "void __iomem *"
> it is declared as "unsigned char __iomem *" but it's not a char pointer
> that's only to make the pointer math work. It would work just as well
> as a void
On 03/09/2015 05:17 PM, Dan Williams wrote:
> On Mon, Mar 9, 2015 at 11:14 AM, Andy Lutomirski wrote:
>> On Mon, Mar 9, 2015 at 7:44 AM, Dan Williams
>> wrote:
>>> On Mon, Mar 9, 2015 at 7:19 AM, Boaz Harrosh wrote:
On 03/05/2015 10:56 PM, Dan Williams wrote:
>>> [..]
> It's not
remove use of #pragma optimize which will usually be ignored by the
compiler.
Signed-off-by: Sudip Mukherjee
---
v3: no change
v2: no change
drivers/staging/sm750fb/ddk750_swi2c.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
mention correct format specifier while printing.
fixes all the build warnings about incorrect argument type while
printing.
since this is a framebuffer device and it should follow what the
framebuffer layer is suggesting in struct fb_fix_screeninfo at
smem_start and mmio_start, so accordingly
kbuild test robot reported that for microblaze-allyesconfig
chan_to_field() and lynxfb_ops_set_par() were not defined. These two
functions were defined under CONFIG_PM, so for any archtecture if
CONFIG_PM is not defined we will have this error.
while moving the lynxfb_suspend() function some very
check if it is already defined before defining SM750LE_REVISION_ID
again and at the same time mention correct data type.
Signed-off-by: Sudip Mukherjee
---
v3: no change
v2: removed the redundant cast in sm750_hw.c
SM750LE_REVISION_ID is defined also in ddk750_chip.h.
for powerpc-allyesconfig build failed with an error of g_option
undeclared. we will get this error on all architecture if MODULE is
not defined. fixed the declaration of g_option.
Reported-by: Stephen Rothwell
Signed-off-by: Sudip Mukherjee
---
v3: new entry in the series, it was not there
On 10 March 2015 at 07:42, Sudip Mukherjee wrote:
> only one concern - if Greg first applies the patches i sent yesterday then
> this patch will not apply, and if this one is applied first then my series
> will not apply ...
Indeed, I am more than happy to adapt the patch as required if your
Add new structure 'power_supply_config' for holding run-time
initialization data like of_node, supplies and private driver data.
The power_supply_register() function is changed so all power supply
drivers need updating.
When registering the power supply this new 'power_supply_config' should be
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
Signed-off-by: Krzysztof
Add simple wrappers for accessing power supply's function attributes:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
- property_is_writeable -> power_supply_property_is_writeable
- external_power_changed -> power_supply_external_power_changed
This API
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by:
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by:
Hi,
The patchset fixes invalid memory accesses in certain race scenarios by
moving ownership of struct power_supply to the core. All drivers are
modified.
TLDR for driver and subsystem maintainers
=
Two patches of patchset change power_supply_register()
Le 09/03/2015 17:14, Linus Walleij a écrit :
> On Sun, Feb 8, 2015 at 7:23 PM, Boris Brezillon
> wrote:
>
>> The gpiochip_lock_as_irq call can fail and return an error, while the
>> irq_startup is not expected to fail (returns an unsigned int which is not
>> checked by irq core code).
>>
>>
The commit c2be45f09bb0 ("compal-laptop: Use
devm_hwmon_device_register_with_groups") wanted to change the
registering of hwmon device to resource-managed version. It mostly did
it except the main thing - it forgot to use devm-like function so the
hwmon device leaked after device removal or probe
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
- property_is_writeable
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by:
The power_supply_get_by_phandle() and power_supply_get_by_name() use
function class_find_device() for obtaining the reference to power
supply. Each use of class_find_device() increases the power supply's
device reference counter.
However the reference counter was not decreased by users of this
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by:
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/power/charger-manager.c | 70 +++--
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
Acked-by: Robert Jarzmik
Acked-by: Pavel Machek
---
arch/arm/mach-pxa/raumfeld.c | 4 +++-
1 file
---
drivers/tty/serial/imx.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
index ddfb672d0152..e9102eba49c4 100644
--- a/drivers/tty/serial/imx.c
+++ b/drivers/tty/serial/imx.c
@@ -1298,7 +1298,7 @@
Replace direct usage of put_device() with new API: power_supply_put().
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
arch/x86/platform/olpc/olpc-xo1-sci.c | 4 ++--
1 file changed, 2 insertions(+), 2
Hi,
On Mon, 2015-03-09 at 11:53 -0700, Stephen Boyd wrote:
> On 03/09/15 01:20, Ivan T. Ivanov wrote:
> > Hi Stephen,
> >
> > > On Mar 6, 2015, at 8:34 PM, Stephen Boyd wrote:
> > > On 03/06/15 07:26, Ivan T. Ivanov wrote:
> > > > Ensure that driver is owner of the GPIO's used for CS signals.
The return value of power_supply_register() call was not checked and
even on error probe() function returned 0. If registering failed then
during unbind the driver tried to unregister power supply which was not
actually registered.
This could lead to memory corruption because
Allow drivers to store private data inside power_supply structure for
later usage in power supply operations.
Usage of driver private data is necessary to access driver's state
container object from power supply calls (like get_property()) if struct
'power_supply' is a stored there as a pointer,
Use power_supply_put() to decrement the power supply's device reference
counter (increased by power_supply_get_by_name() or
power_supply_get_by_phandle()).
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
---
drivers/tty/serial/serial_mctrl_gpio.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/tty/serial/serial_mctrl_gpio.c
b/drivers/tty/serial/serial_mctrl_gpio.c
index 5027db7b5814..0ec756c62bcf 100644
--- a/drivers/tty/serial/serial_mctrl_gpio.c
+++
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by:
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Acked-by: Linus Walleij
Acked-by: Lee Jones
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/mfd/ab8500-sysctrl.c | 2
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/power/88pm860x_charger.c | 11 +--
1 file changed, 9
Increment the power_supply.use_cnt usage counter on:
- power_supply_get_by_phandle()
- power_supply_get_by_name()
and decrement it on power_supply_put() call.
This helps tracking of valid usage of power supply instance by
consumers. The usage counter itself also allows safe calling of
Replace direct usage of put_device() with new API: power_supply_put().
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
arch/x86/platform/olpc/olpc-xo15-sci.c | 4 ++--
1 file changed, 2 insertions(+), 2
Hello Greg,
On Tue, Mar 10, 2015 at 04:28:16PM +1100, Stephen Rothwell wrote:
> After merging the tty tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/tty/serial/imx.c: In function 'imx_set_termios':
> drivers/tty/serial/imx.c:1301:7: warning: suggest
Hi,
On 03/07/2015 03:00 PM, Jeff Layton wrote:
> On Fri, 6 Mar 2015 08:53:30 +0100
> Daniel Wagner wrote:
>
>> Hi,
>>
>> Finally, I got a bigger machine and did a quick test round. I expected
>> to see some improvements but the resutls do not show any real gain. So
>> they are merely
Hi Tejun,
>> The reason is that when cgroup_can_fork() is called, the css_set doesn't
>> contain the pids cgroup it's forking to. You can verify this by moving that
>> segment of code back to it's original position and
>> compiling/rebooting/testing
>> the pids cgroup. You will get a WARN each
* Jason Low wrote:
> This patch applies on top of tip.
>
> ---
> Similar to what Linus suggested for rwsem_spin_on_owner(), in
> mutex_spin_on_owner(), instead of having while (true) and breaking
> out of the spin loop on
Hi Austin,
>> Does pids limit make sense in the root cgroup?
>>
> I would say it kind of does, although I would just expect it to track
> /proc/sys/kernel/pid_max (either as a read-only value, or as an alternative
> way to set it).
Personally, that seems unintuitive. /proc/sys/kernel/pid_max and
On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
> On Mon, Mar 09, 2015 at 10:23:35AM +0200, Ivan T. Ivanov wrote:
> > Hi,
>
> Don't reply off list unless there's a good reason...
Sorry, it was not intentional. Wrong button.
>
> > > Any new GPIO users should really be using the gpiod API,
At Mon, 9 Mar 2015 22:55:22 -0700,
Guenter Roeck wrote:
Thanks comment.
>
> On Mon, Mar 09, 2015 at 05:46:54PM +0900, Yoshinori Sato wrote:
> > Hello.
> >
> > I rewriting h8300 support.
> >
> It might possibly be better to use the term "re-introduce" instead of
> rewrite or revert (as in the
+
+/* Altera EPCQ/EPCS Flashes */
+{ "epcq16" , EPCQ_INFO(2, 0x15, 0x1, 32, 0x100) },
+{ "epcq32" , EPCQ_INFO(2, 0x16, 0x1, 64, 0x100) },
+{ "epcq64" , EPCQ_INFO(2, 0x17, 0x1, 128, 0x100) },
+{ "epcq128" , EPCQ_INFO(2, 0x18,
* Li, Aubrey wrote:
> >> - in x86_reduced_hw_init() set 'legacy_pic' to 'null_legacy_pic'
> >>
> >> - clean up 'global_clock_event' handling: instead of a global
> >>variable, move its management into x86_platform_ops::get_clockevent()
> >>and set the method to hpet/pit/abp/etc.
On Mon 2015-03-09 11:50:56, Måns Rullgård wrote:
> Geert Uytterhoeven writes:
>
> > Hi Pavel,
> >
> > On Sun, Mar 8, 2015 at 9:57 PM, Pavel Machek wrote:
> >> Ok, so I played with RGB LED a bit, and we have quite a gap in
> >> documentation: what 50% brightness means is non-trivial and very
>
On Mon, Mar 09, 2015 at 01:46:25PM -0700, Kevin Hilman wrote:
> Sascha Hauer writes:
>
> > This adds documentation for the MediaTek SCPSYS unit found in MT8173 SoCs.
>
> Curious if this IP unique to the 8173? or maybe also used on 8135? ...
This is indeed found on the MT8135 aswell, but I
Final patch:
---
From: Yinghai Lu
Date: Sat, 7 Mar 2015 14:07:16 -0800
Subject: [PATCH] x86/setup: Move compressed kernel to the end of the buffer
Boris found that passing KASLR status through setup_data from the boot
stage cannot be used later in the kernel stage, see commit
f47233c2d34f
On 2015年03月06日 02:51, Lorenzo Pieralisi wrote:
On Wed, Feb 25, 2015 at 08:39:45AM +, Hanjun Guo wrote:
From: Al Stone
As we want to get ACPI tables to parse and then use the information
for system initialization, we should get the RSDP (Root System
Description Pointer) first, it then
Hi!
> > Here is a new trigger. It would allow userspace to make an LED
> > blink with a pattern to show a status (or error) code to a human.
> > This is useful for embedded systems without screen or network
> > access. Obviously, the LED will keep on blinking even if userspace
> > crashes.
>
>
* Denys Vlasenko wrote:
> Old code was trying to avoid having three branch insns,
> but instead it has a chain of six insns where each insn
> depends on previos one.
>
> And it was touching PT_OLDSS(%esp) unconditionally, even when it may
> contain bogus data. Elsewhere we have to jump thru
On Tue, Mar 10, 2015 at 09:53:19AM +0800, Pi-Cheng Chen wrote:
> On 5 March 2015 at 15:42, Sascha Hauer wrote:
> >
> > My suggestion is to take another approach. Implement clk_set_rate for
> > these muxes and in the set_rate hook:
> >
> > - switch mux to intermediate PLL parent
> > - call
* Linus Torvalds wrote:
> On Mon, Mar 9, 2015 at 9:55 AM, Borislav Petkov wrote:
> > On Mon, Mar 09, 2015 at 09:49:42AM -0700, Linus Torvalds wrote:
> >>
> >> I don't remember when it was open-coded, and I never created a git
> >> archive of all the old tar-files from before BK, so it's not
On 03/10/2015 04:48 AM, Florian Westphal wrote:
> It is identical to the can destructor.
>
> Signed-off-by: Florian Westphal
Thanks, applied to can-next.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions| Phone: +49-231-2826-924
On Tue, Mar 10, 2015 at 12:14 AM, Brian Norris
wrote:
> On Tue, Mar 03, 2015 at 10:39:45PM +0100, Frans Klaver wrote:
>> add_mtd_device() has a comment suggesting that the caller should have
>> set dev.parent. This is required to have the device show up in sysfs,
>
> What do you mean "have the
At Mon, 09 Mar 2015 02:13:31 -0700,
Jeff Kirsher wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 03/09/2015 01:47 AM, Yoshinori Sato wrote:
> > Signed-off-by: Yoshinori Sato ---
> > drivers/clk/Makefile| 1 + drivers/clk/h8300/Makefile
> > | 2 +
At Mon, 09 Mar 2015 02:10:57 -0700,
Jeff Kirsher wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 03/09/2015 01:47 AM, Yoshinori Sato wrote:
> > Signed-off-by: Yoshinori Sato ---
> > include/uapi/linux/elf-em.h | 1 + 1 file changed, 1 insertion(+)
>
> Where is the patch
On Tue, Mar 10, 2015 at 7:28 AM, Brian Norris
wrote:
> On Tue, Mar 03, 2015 at 10:40:14PM +0100, Frans Klaver wrote:
>> Fix a bug where devices aren't shown in sysfs.
>>
>> While at it, make use of the default owner value set by mtdcore.
>>
>> Signed-off-by: Frans Klaver
>> ---
>>
On Mon, Mar 09, 2015 at 08:57:08PM +, Lorenzo Stoakes wrote:
>
> +#include
> +
apart from what Dan Carpenter has said,
this is introducing one checkpatch warning, better to use #include
checkpatch is also giving warning about your patch subject
only one concern - if Greg first applies the
On Fri, Mar 06, 2015 at 11:04:28PM -0800, K. Y. Srinivasan wrote:
> Export the vmbus_sendpacket_pagebuffer_ctl() interface.
Why? Nothing in this patch needs it. Please include this in the patch
that needs the symbol, or at least give a hint as to what is going on.
As it is, this just looks
On Tue, Mar 10, 2015 at 03:31:44AM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: KY Srinivasan
> > Sent: Friday, March 6, 2015 9:20 PM
> > To: KY Srinivasan; gre...@linuxfoundation.org; linux-
> > ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
>
801 - 900 of 1866 matches
Mail list logo
