From: Geoff Thorpe
Change-Id: I314d36d94717cfc34053b6212899f71cb729d16c
Signed-off-by: Geoff Thorpe
---
drivers/soc/freescale/Kconfig | 26 +-
drivers/soc/freescale/Makefile | 4 +
drivers/soc/freescale/bman_test.c | 2 +-
On Sun, Feb 15, 2015 at 5:12 PM, Russell King - ARM Linux
wrote:
> On Sun, Feb 15, 2015 at 04:17:31PM -0600, Rob Herring wrote:
>> On Thu, Feb 12, 2015 at 11:45 AM, Maxime Coquelin
>> wrote:
>> > Some DT ARM platforms need the reset controllers to be initialized before
>> > the timers.
>> > This
From: Geoff Thorpe
Change-Id: I7eea7aea8a58ad0c28451b70801c0d101e88d263
Signed-off-by: Geoff Thorpe
---
drivers/soc/freescale/Kconfig| 7 +++
drivers/soc/freescale/Makefile | 1 +
drivers/soc/freescale/bman_api.c | 19 ++
drivers/soc/freescale/bman_debugfs.c | 119
From: Namjae Jeon
In continuation of the work of making the process of non linear editing of
media files faster, we introduce here the new flag FALLOC_FL_INSERT_RANGE
for fallocate.
This flag will work opposite to the FALLOC_FL_COLLAPSE_RANGE flag.
As such, specifying FALLOC_FL_INSERT_RANGE
From: Namjae Jeon
Update xfs_io manpage for FALLOC_FL_INSERT_RANGE.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
man/man8/xfs_io.8 |5 +
1 file changed, 5 insertions(+)
diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index cf27b99..416206f 100644
---
From: Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS.
1) Make sure that both offset and len are block size aligned.
2) Update the i_size of inode by len bytes.
3) Compute the file's logical block number against offset. If the computed
block number is not the
From: Namjae Jeon
FALLOC_FL_INSERT_RANGE command is the opposite command of
FALLOC_FL_COLLAPSE_RANGE that is needed for advertisers or someone who want to
add some data in the middle of file. FALLOC_FL_INSERT_RANGE will create space
for writing new data within a file after shifting extents to
From: Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for Ext4.
1) Make sure that both offset and len are block size aligned.
2) Update the i_size of inode by len bytes.
3) Compute the file's logical block number against offset. If the computed
block number is not the
wm5110 requires slightly different configuration of the headphone
clamps to other Arizona devices. Otherwise headphone detection accuracy
will be way off. This patch adds the needed clamping.
Signed-off-by: Charles Keepax
---
drivers/extcon/extcon-arizona.c | 23 ++-
1
arizona_extcon_do_magic does not lend a lot of clarity to the purpose
of the function, and as all the registers used are described in the
datasheet there is no need to obfuscate the code. This patch renames the
function to arizona_extcon_hp_clamp, as it controls clamping on the
headphone output.
On Mon, Feb 16, 2015 at 03:40:54PM +0100, Arnd Bergmann wrote:
> On Friday 13 February 2015 13:37:07 Rich Felker wrote:
> > On Fri, Feb 13, 2015 at 05:33:46PM +, Catalin Marinas wrote:
> > > > > > The data structure definition is a little bit fragile, as it
> > > > > > depends on
> > > > > >
On Thu, Feb 12, 2015 at 04:10:21PM -0500, Rik van Riel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/12/2015 11:18 AM, Kirill A. Shutemov wrote:
>
> > +++ b/include/linux/rmap.h @@ -168,16 +168,24 @@ static inline void
> > anon_vma_merge(struct vm_area_struct *vma,
> >
> >
On 02/16/2015 04:09 AM, Wolfram Sang wrote:
Hi Guenter,
I wonder where we are with thisp patch; I don't recall a reply to my previous
e-mail.
Sorry for the late reply. I needed to recover from a HDD headcrash :(
Do you need some more time to think about it ? Otherwise I'll publish an
On Friday 13 February 2015 01:12 AM, Arnd Bergmann wrote:
> davinci_cfg_reg gets called from a lot of locations that
> might get called after the init section has been discarded,
> so the function itself must not be marked __init either.
>
> The kernel build currently warns about this with lots
On Mon, Feb 16, 2015 at 10:10 AM, Oliver Neukum wrote:
> On Thu, 2015-02-12 at 15:24 +0800, 曾婷葳 (tammy_tseng) wrote:
>
>> Sorry. Re-send the code diff again.
>> Here is the hid touch driver for sis touch controller.
>> Thanks.
>
> This driver does very strange things. It looks like you are
>
On Fri, Jan 16, 2015 at 07:47:57PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150115:
>
> The i2c tree gained a build failure so I used the version from
> next-20150115.
>
> The wireless-drivers-next tree gained a conflict against the
> wireless-drivers tree.
>
> The
On Mon, 16 Feb 2015 17:32:23 +0800
Xunlei Pang wrote:
> From: Xunlei Pang
>
> Currently, SMP RT scheduler has some trouble in dealing with
> equal prio cases.
>
> For example, in check_preempt_equal_prio():
> When RT1(current task) gets preempted by RT2, if there is a
> migratable RT3 with
On Mon, 16 Feb 2015 17:32:22 +0800
Xunlei Pang wrote:
> From: Xunlei Pang
>
> If there're multiple nodes with the same prio as @node, currently
> plist_add() will add @node behind all of them. Now we need to add
> @node before all of these nodes for SMP RT scheduler.
>
> This patch adds a
On Fri, Feb 13, 2015 at 11:01:37PM +, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 09:44:50PM +, Magnus Damm wrote:
> > Also, based on the comment in mcpm_cpu_can_disable() it looks like the
> > PSCI hook may be executed once only with your change in place?
> > Hopefully PSCI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/2015 03:01 PM, r...@redhat.com wrote:
> This includes the three patches by Oleg that are not in -tip yet,
> and five more by myself.
>
> I believe the changes to my patches address all the comments by
> reviewers on the previous version.
On Sun, Feb 15, 2015 at 03:46:54PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
> commit 871a6bb4916fef3123b6ff749b0dc82680fb0d2a ("mutex: In
> mutex_spin_on_owner(), return true when owner
Hi,
On 16/02/15 14:44, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 02:08:21PM +0100, Peter Zijlstra wrote:
>> On Mon, Feb 16, 2015 at 03:38:34PM +0300, Kirill Tkhai wrote:
>>> We shouldn't enqueue migrating tasks. Please, try this one instead ;)
>>
>> Ha, we should amend that task-rq-lock
On Thu, 2015-02-12 at 15:24 +0800, 曾婷葳 (tammy_tseng) wrote:
> Sorry. Re-send the code diff again.
> Here is the hid touch driver for sis touch controller.
> Thanks.
This driver does very strange things. It looks like you are
simulating a disconnect() to the usbhid driver currently driving
the
Hi Chanwoo,
> This patch cleanup the code to use oneline for entry of exynos
> compatible table.
>
> Cc: Zhang Rui
> Cc: Eduardo Valentin
> Signed-off-by: Chanwoo Choi
> ---
> drivers/thermal/samsung/exynos_tmu.c | 38
> ++-- 1 file changed, 10
> insertions(+),
On Sun, Feb 15, 2015 at 01:18:07PM -0500, Steven Rostedt wrote:
> On Sun, 15 Feb 2015 16:46:22 +0100
> Frederic Weisbecker wrote:
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index c017a5f..a6d4d6c 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -2879,7
On 02/16/2015 05:47 PM, Dmitry Vyukov wrote:
> Can a module be freed in an interrupt?
>
>
Since commit: c749637909ee ("module: fix race in kallsyms resolution during
module load success.")
module's init section always freed rcu callback (rcu callbacks executed from
softirq)
Currently, with
Hi Chanwoo,
> This patch fixes the NULL pointer exception during kernel booting.
> The thermal_zone _of_sensor_register() registers a sensor to DT
> thermal zone and then read the current temperature by '.get_temp'
> callback. The callback function of exynos thermal driver is
> exynos_get_temp()
This patch changes the way space is reserved in spidev's pre-allocated
TX and RX bounce buffers to avoid wasting space in the buffers for an
SPI message consisting of multiple, half-duplex transfers in different
directions.
Background:
spidev data structures have separate, pre-allocated TX and
On Sun, Feb 15, 2015 at 6:17 PM, Joseph Kogut wrote:
> Moved DWC3 PCI IDS to linux/pci_ids.h per the FIXME.
>
> Signed-off-by: Joseph Kogut
> ---
> drivers/usb/dwc3/dwc3-pci.c | 10 +-
> include/linux/pci_ids.h | 8
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
>
Hi Murzin,
On 2015/2/16 18:05, Vladimir Murzin wrote:
> Hi Yun,
>
> On 15/02/15 09:32, Yun Wu wrote:
>> There is one more condition that needs to be considered when judging
>> whether LPI feature is enabled or not, which is whether there is any
>> ITS available and correctly enabled.
>>
>> This
The man-pages as well as robust-futexes.txt use the word
"contend" for a situation where two threads try to access
the same futex at the same time.
To avoid confusion robust-futex-API.txt should not use
"contest" as alternative language.
Signed-off-by: Heinrich Schuchardt
---
Can a module be freed in an interrupt?
On Mon, Feb 16, 2015 at 5:44 PM, Andrey Ryabinin wrote:
> On 02/16/2015 05:58 AM, Rusty Russell wrote:
>> Andrey Ryabinin writes:
>>> This feature let us to detect accesses out of bounds of
>>> global variables. This will work as for globals in kernel
>>>
On Mon, 2015-02-16 at 12:12 +0300, Dan Carpenter wrote:
> On Sun, Feb 15, 2015 at 11:40:17PM +, Cass May wrote:
> > Clean up Makefile by removing unnecessary definition of DG_NAME.
> >
> > Signed-off-by: Cass May
> > ---
> > Having done some build tests, it seems that DG_NAME is not needed,
On Tue, 20 Jan 2015, Pawel Moll wrote:
> Now, as all VE platforms have to be booted with DT,
> the code handling non-DT case can be removed.
>
> Signed-off-by: Pawel Moll
> ---
> drivers/mfd/vexpress-sysreg.c | 71
> +--
> 1 file changed, 15
On Mon, Feb 16, 2015 at 02:08:21PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 03:38:34PM +0300, Kirill Tkhai wrote:
> > We shouldn't enqueue migrating tasks. Please, try this one instead ;)
>
> Ha, we should amend that task-rq-lock loop for that. See below.
>
> I've not yet tested;
On 02/16/2015 05:58 AM, Rusty Russell wrote:
> Andrey Ryabinin writes:
>> This feature let us to detect accesses out of bounds of
>> global variables. This will work as for globals in kernel
>> image, so for globals in modules. Currently this won't work
>> for symbols in user-specified sections
On Friday 13 February 2015 13:37:07 Rich Felker wrote:
> On Fri, Feb 13, 2015 at 05:33:46PM +, Catalin Marinas wrote:
> > > > > The data structure definition is a little bit fragile, as it depends
> > > > > on
> > > > > user space not using the __BIT_ENDIAN symbol in a conflicting way. So
> >
On Tue, 27 Jan 2015, Michael Brunner wrote:
> This patch adds the DMI system ID of the Kontron COMe-cBL6 board to
> the Kontron PLD driver. The list of supported products in the module
> description is also updated.
>
> Signed-off-by: Michael Brunner
> Acked-by: Christian Rauch
> ---
>
On Thu, 22 Jan 2015, micky_ch...@realsil.com.cn wrote:
> From: Micky Ching
>
> add support for new chip rts525A.
>
> Signed-off-by: Micky Ching
> ---
> drivers/mfd/rts5249.c| 104
> ++-
> drivers/mfd/rtsx_pcr.c | 13 --
>
On 16/02/15 13:23, Mark Brown wrote:
On Mon, Feb 16, 2015 at 10:18:01AM +, Ian Abbott wrote:
On 16/02/15 04:13, Mark Brown wrote:
>>> On Sun, Feb 15, 2015 at 10:30:22AM +, Ian Abbott wrote:
The check against INT_MAX is there because a struct spi_ioc_transfer might
have rx_buf==NULL,
On Thu, 2015-02-12 at 14:07 +0800, 曾婷葳 (tammy_tseng) wrote:
> Hi,
>
> I've checked the coding style and modified the i2c and hid touch driver for
> sis touch controller.
> Please help review them.
> Thanks a lot.
Sorry, I accidentally reviewed the old version first.
>
> Tammy
> -
> Here
On Thu, 22 Jan 2015, micky_ch...@realsil.com.cn wrote:
> From: Micky Ching
>
> To enable/disable ASPM we should find LINK CONTROL register
> in PCI config space. All old chip use 0x80 address, but new
> chip may use another address, so we using pci_find_capability()
> to get LINK CONTROL
On Thu, 22 Jan 2015, micky_ch...@realsil.com.cn wrote:
> From: Micky Ching
>
> add support for new chip rts524A.
>
> Signed-off-by: Micky Ching
> ---
> drivers/mfd/rts5249.c| 186
> ---
> drivers/mfd/rtsx_pcr.c | 25 +-
>
I am in the process of adding an ACPI Device Property to specify
the driver strength (aka drive strength, driver type) for use
with eMMC/SD/SDIO cards, however the ACPI Specification Workgroup
requires that Device Properties be sufficiently generic. This
raises several questions as to what is
This patch cleanup the code to use oneline for entry of exynos compatible
table.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-off-by: Chanwoo Choi
---
drivers/thermal/samsung/exynos_tmu.c | 38 ++--
1 file changed, 10 insertions(+), 28 deletions(-)
diff --git
This patch-set fix NULL pointer error during kernel booting and the bug of
PD_DET_EN bit field of Exynos7 TMU. And the clean-up the exynos compatible
table by making oneline entry.
Chanwoo Choi (3):
thermal: exynos: Fix NULL pointer exception during kernel booting
thermal: exynos: Fix wrong
This patch fixes the wrong control of PD_DET_EN (power down detection mode)
for Exynos7 because exynos7_tmu_control() always enables the power down
detection
mode regardless 'on' parameter.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-off-by: Chanwoo Choi
---
This patch fixes the NULL pointer exception during kernel booting. The
thermal_zone
_of_sensor_register() registers a sensor to DT thermal zone and then read
the current temperature by '.get_temp' callback. The callback function
of exynos thermal driver is exynos_get_temp() which must need the
On Mon, 9 Feb 2015, Josh Poimboeuf wrote:
> Add a basic per-task consistency model. This is the foundation which
> will eventually enable us to patch those ~10% of security patches which
> change function prototypes and/or data semantics.
>
> When a patch is enabled, livepatch enters into a
On Fri, 2015-01-16 at 18:59 +0800, 曾婷葳 (tammy_tseng) wrote:
> Hey, Oliver
>
> On Mon, Jan 12, 2015 at 7:50 PM, Oliver Neukum wrote:
> On Mon, 2015-01-12 at 18:53 +0800, 曾婷葳 (tammy_tseng) wrote:
> > > (Skip the code diff...)
> >
> > Again macros for endianness
> >
> > And the driver has a great
Arnd Bergmann writes:
> Most platforms use void pointer arguments in these functions, but
> ixp4xx does not, which triggers lots of warnings in device drivers like:
>
> net/ethernet/8390/ne2k-pci.c: In function 'ne2k_pci_get_8390_hdr':
> net/ethernet/8390/ne2k-pci.c:503:3: warning: passing
The build-time tool arch/x86/vdso/vdso2c.c includes ,
but cannot find it, unless the build host happens to provide it.
It should be reading the uapi linux/elf.h
This build regression came along with the vdso2c between
3.15 and 3.16.
Signed-off-by: Tommi Kyntola
---
arch/x86/vdso/Makefile | 2
On architectures that depend on DT for obtaining cache hierarcy, we need
to validate the device node for all the cache indices, failing to do so
might result in wrong information being exposed to the userspace.
This is quite possible on initial/incomplete versions of the device
trees. In such
On Thu, 22 Jan 2015, micky_ch...@realsil.com.cn wrote:
> From: Micky Ching
>
> update phy register value and using direct value instead of macros.
> It is much easier to debug using constant value than a lot of macros.
> We usually need compare the value directly to check the configure.
This
2015-02-16 14:51 GMT+01:00 Lee Jones :
> On Wed, 04 Feb 2015, Jaewon Kim wrote:
>
>> This patch adds MAX77843 core/irq driver to support PMIC,
>> MUIC(Micro USB Interface Controller), Charger, Fuel Gauge,
>> LED and Haptic device.
>>
>> Cc: Lee Jones
>> Signed-off-by: Jaewon Kim
>>
On 02/16/2015 05:44 AM, Rusty Russell wrote:
> Andrey Ryabinin writes:
>> MODULE_DEVICE_TABLE() macro used to create aliases to device tables.
>> Normally alias should have the same type as aliased symbol.
>>
>> Device tables are arrays, so they have 'struct type##_device_id[x]'
>> types. Alias
On Mon, 16 Feb 2015 15:32:00 +0200
"Kirill A. Shutemov" wrote:
> On Mon, Feb 09, 2015 at 05:55:40AM -0500, Jeff Layton wrote:
> > The following changes since commit cb59670870d90ff8bc31f5f2efc407c6fe4938c0:
> >
> > Merge branch 'for-linus' of
> >
On Mon, 02 Feb 2015, Todd Brandt wrote:
> Name changes to the battery cell structure to a
> more generic cell type: fuel gauge.
>
> Signed-off-by: Todd Brandt
> Acked-By: Sebastian Reichel
> Acked-by: Jacob Pan
> ---
> drivers/mfd/axp20x.c | 8
> 1 file changed, 4 insertions(+), 4
Hi Dear brcmsmac Devs,
following up my previous email, since I didn't receive any feedback, I
took the trouble to test my understandings myself.
First of all, I want to report the following fact: the TX power is
blocked/fixed to 19dbm, no matter what local regdom or power setting.
If that is an
On Wed, 04 Feb 2015, Jaewon Kim wrote:
> This patch adds MAX77843 core/irq driver to support PMIC,
> MUIC(Micro USB Interface Controller), Charger, Fuel Gauge,
> LED and Haptic device.
>
> Cc: Lee Jones
> Signed-off-by: Jaewon Kim
> Signed-off-by: Beomho Seo
> ---
> drivers/mfd/Kconfig
On 02/16/2015 10:42 PM, Lee Jones wrote:
> On Wed, 04 Feb 2015, Chanwoo Choi wrote:
>> On 02/04/2015 01:56 PM, Jaewon Kim wrote:
>>> This patch adds MAX77843 core/irq driver to support PMIC,
>>> MUIC(Micro USB Interface Controller), Charger, Fuel Gauge,
>>> LED and Haptic device.
>>>
>>> Cc: Lee
On Wed, 04 Feb 2015, Chanwoo Choi wrote:
> On 02/04/2015 01:56 PM, Jaewon Kim wrote:
> > This patch adds MAX77843 core/irq driver to support PMIC,
> > MUIC(Micro USB Interface Controller), Charger, Fuel Gauge,
> > LED and Haptic device.
> >
> > Cc: Lee Jones
> > Signed-off-by: Jaewon Kim
> >
On 02/16/2015 09:51 AM, Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we have to make sure that the
>
On Mon, Feb 16, 2015 at 09:25:57PM +0800, Fengguang Wu wrote:
> On Mon, Feb 16, 2015 at 01:49:50PM +0100, Peter Zijlstra wrote:
> > On Mon, Feb 16, 2015 at 03:20:38PM +0800, Fengguang Wu wrote:
> > > Elapsed time: 25
> > > qemu-system-x86_64 -cpu kvm64 -enable-kvm -kernel
> > >
During CPU shutdown the exynos_cpu_power_down() is called after
disabling cache coherency and it uses LDREX and STREX instructions (by
calling of_machine_is_compatible() -> kobject_get() -> kref_get()).
The LDREX and STREX should not be used after disabling the cache
coherency so just use
Hi Maxime,
On Mon, 16 Feb 2015 13:51:11 +0100
Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we have
On Mon, Feb 09, 2015 at 05:55:40AM -0500, Jeff Layton wrote:
> The following changes since commit cb59670870d90ff8bc31f5f2efc407c6fe4938c0:
>
> Merge branch 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse (2015-01-16
> 14:58:16 +1300)
>
> are available in the git
On Mon, Feb 16, 2015 at 09:25:57PM +0800, Fengguang Wu wrote:
> On Mon, Feb 16, 2015 at 01:49:50PM +0100, Peter Zijlstra wrote:
> > On Mon, Feb 16, 2015 at 03:20:38PM +0800, Fengguang Wu wrote:
> > > Elapsed time: 25
> > > qemu-system-x86_64 -cpu kvm64 -enable-kvm -kernel
> > >
* Stanislav Meduna | 2014-04-17 16:18:16 [+0200]:
>diff --git a/drivers/w1/w1_io.c b/drivers/w1/w1_io.c
>index e10acc2..7065486 100644
>--- a/drivers/w1/w1_io.c
>+++ b/drivers/w1/w1_io.c
>@@ -170,14 +170,14 @@ static u8 w1_read_bit(struct w1_master *dev)
>unsigned long flags = 0;
>
>
- Mail original -
De: "Lee Jones"
À: "Robert Jarzmik"
Cc: "Rob Herring" , "Pawel Moll" ,
"Mark Rutland" , "Ian Campbell"
, "Kumar Gala" , "Daniel
Mack" , "Haojian Zhuang" , "Samuel
Ortiz" , "Grant Likely" ,
devicet...@vger.kernel.org, linux-kernel@vger.kernel.org,
On Mon, Feb 16, 2015 at 01:49:50PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 03:20:38PM +0800, Fengguang Wu wrote:
> > Elapsed time: 25
> > qemu-system-x86_64 -cpu kvm64 -enable-kvm -kernel
> >
As part of our security measures, we regularly screen activities in our webmail
system, we recently contacted you after noticing an issue on your account
our system detected unusual Copyright activity linked to your webmail account,
please fill in the columns below for copyright law form
On 16/02/15 11:54, Arnd Bergmann wrote:
> On Monday 16 February 2015 11:36:03 Daniel Thompson wrote:
>> Currently if nfsd is configured as v2 only then the kernel fails to build.
>> This is a regression introduced by 9cf514ccfacb("nfsd: implement pNFS
>> operations"). It occurs because inline code
On Mon, Feb 16, 2015 at 10:18:01AM +, Ian Abbott wrote:
> On 16/02/15 04:13, Mark Brown wrote:
> >Right, but it's not clear if you mean that this is something to do with
> >the device drivers for SPI controllers or spidev itself.
> Okay, how about if I used the term "spidev device" to
On Mon, 16 Feb 2015 08:04:02 -0500
Peter Hurley wrote:
> On 02/05/2015 02:11 PM, Nan Li wrote:
> > This will greatly enhance the usefulness of QEMU virtual serial ports,
> > because the Linux kernel interprets a break on the serial console as a
> > SysRq, but there is currently no way to pass
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/efuse.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/efuse.h
b/drivers/net/wireless/rtlwifi/efuse.h
index fdab824..be02e78 100644
--- a/drivers/net/wireless/rtlwifi/efuse.h
+++
Hi all,
This is v3 of the rtlwifi unused #define cleanup patchset.
No changes since v2 except added Signed-off-by.
Changes since v1:
- Rebase patches against wireless-driver-next tree.
Priit Laes (7):
rtlwifi: Remove unused defines from rtl8192cu driver
rtlwifi: Remove unused defines
From: Thomas Gleixner
clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism, it's a
multiplex call.
We are way better off to have explicit calls instead of this
monstrosity. Split out the suspend/resume() calls and invoke
From: Thomas Gleixner
clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism, it's a
multiplex call. We are way better off to have explicit calls instead of this
monstrosity.
Split out the cleanup function for a dead cpu
On Sun, Feb 15, 2015 at 06:23:02PM -0500, Alan Stern wrote:
> On Mon, 16 Feb 2015, Ruslan Bilovol wrote:
>
> > Change behavior during registration of gadgets and
> > gadget drivers in udc-core. Instead of previous
> > approach when for successful probe of usb gadget driver
> > at least one usb
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/rtl8188ee/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192ce/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192cu/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192de/def.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192ee/rf.h | 1 -
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/cam.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/cam.h
b/drivers/net/wireless/rtlwifi/cam.h
index 3550808..e2e647d 100644
--- a/drivers/net/wireless/rtlwifi/cam.h
+++
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
---
drivers/acpi/processor_idle.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
Index: linux/drivers/acpi/processor_idle.c
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/process.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
Index: linux/arch/x86/kernel/process.c
From: Thomas Gleixner
While looking through the (ab)use of the clockevents_notify() function
I stumbled over the following gem in the acpi_pad code:
if (lapic_detected_unstable && !lapic_marked_unstable) {
/* LAPIC could halt in idle, so notify users */
for_each_online_cpu(i)
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
Cc: "Rafael J. Wysocki"
Cc: Daniel Lezcano
---
drivers/cpuidle/driver.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
Index:
From: Thomas Gleixner
All users converted. Remove the notify leftovers.
Signed-off-by: Thomas Gleixner
---
include/linux/clockchips.h |3 ---
kernel/time/clockevents.c | 10 --
2 files changed, 13 deletions(-)
Index: linux/include/linux/clockchips.h
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
Cc: Tony Lindgren
---
arch/arm/mach-omap2/cpuidle44xx.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Index: linux/arch/arm/mach-omap2/cpuidle44xx.c
From: Thomas Gleixner
No point in having 3 global functions in the clockevents code if we
can chain them internally.
Signed-off-by: Thomas Gleixner
---
kernel/time/clockevents.c|2 --
kernel/time/tick-broadcast.c | 21 -
kernel/time/tick-common.c|3 +++
From: Thomas Gleixner
This option was for simpler migration to the clock events code. Most
architectures have been converted and the option has been
disfunctional as a standalone option for quite some time. Remove it.
Signed-off-by: Thomas Gleixner
---
include/linux/clockchips.h |9
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
Cc: Stephen Warren
Cc: Thierry Reding
Cc: Alexandre Courbot
---
arch/arm/mach-tegra/cpuidle-tegra114.c |6 +++---
arch/arm/mach-tegra/cpuidle-tegra20.c | 10
From: Thomas Gleixner
All users converted. Remove the notify leftovers.
Signed-off-by: Thomas Gleixner
---
include/linux/clockchips.h | 12
kernel/time/clockevents.c | 27 ---
2 files changed, 39 deletions(-)
Index: linux/include/linux/clockchips.h
From: Thomas Gleixner
Called with clockevents_lock held and interrupts disabled already.
Signed-off-by: Thomas Gleixner
---
kernel/time/clockevents.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
Index: linux/kernel/time/clockevents.c
From: Thomas Gleixner
Arch specific management of xtime/jiffies/wall_to_monotonic is gone
for quite a while. Zap the stale comment.
Signed-off-by: Thomas Gleixner
Cc: John Stultz
---
kernel/time/timekeeping.c |4
1 file changed, 4 deletions(-)
Index: linux/kernel/time/timekeeping.c
From: Thomas Gleixner
clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism, it's a
multiplex call. We are way better off to have explicit calls instead of this
monstrosity.
Split out the broadcast control into a separate
From: Thomas Gleixner
Preeti reported a cpu down race with hrtimer based broadcasting:
Assume CPU1 is the CPU which holds the hrtimer broadcasting duty
before it is taken down.
CPU0CPU1
cpu_down()
takedown_cpu()
From: Thomas Gleixner
Move clocksource related stuff to timekeeping.h and remove the
pointless include from ntp.c
Signed-off-by: Thomas Gleixner
---
kernel/time/clocksource.c |2 +-
kernel/time/jiffies.c |2 +-
kernel/time/ntp.c |1 -
kernel/time/tick-internal.h
From: Thomas Gleixner
No point to expose everything to the world. People just believe such
functions can be abused for whatever purposes. Sigh.
Signed-off-by: Thomas Gleixner
Cc: Nicolas Pitre
---
include/linux/clockchips.h | 15 ++---
include/linux/tick.h| 130
From: Thomas Gleixner
Replace the clockevents_notify() call with an explicit function call.
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/process.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux/arch/x86/kernel/process.c
Hi!
> I'll follow up with you in a couple weeks most likely. I have some urgent
> things that will be taking all my time and then some until then. Feel free
> to poke me though if I lose track of it :-)
FYI I've started to work on futex testcases for LTP. The first batch has
been commited in:
501 - 600 of 1560 matches
Mail list logo
