Commit-ID: ed7940731ac89616b8a516c560a76dca44a152a8
Gitweb: http://git.kernel.org/tip/ed7940731ac89616b8a516c560a76dca44a152a8
Author: Joe Stringer
AuthorDate: Sun, 22 Jan 2017 17:11:23 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan
Commit-ID: cd4ceb63438e9e28299f4352ae7b75d2967a772d
Gitweb: http://git.kernel.org/tip/cd4ceb63438e9e28299f4352ae7b75d2967a772d
Author: Namhyung Kim
AuthorDate: Thu, 11 Apr 2013 17:25:04 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26
Commit-ID: ed7940731ac89616b8a516c560a76dca44a152a8
Gitweb: http://git.kernel.org/tip/ed7940731ac89616b8a516c560a76dca44a152a8
Author: Joe Stringer
AuthorDate: Sun, 22 Jan 2017 17:11:23 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan 2017 11:42:57 -0300
tools lib
Commit-ID: cd4ceb63438e9e28299f4352ae7b75d2967a772d
Gitweb: http://git.kernel.org/tip/cd4ceb63438e9e28299f4352ae7b75d2967a772d
Author: Namhyung Kim
AuthorDate: Thu, 11 Apr 2013 17:25:04 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan 2017 11:42:59 -0300
perf util:
Commit-ID: e28ff1a8382ee02b10cf11cf3b48541dc3d14a58
Gitweb: http://git.kernel.org/tip/e28ff1a8382ee02b10cf11cf3b48541dc3d14a58
Author: Joe Stringer
AuthorDate: Sun, 22 Jan 2017 17:11:25 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan
Commit-ID: 0a87e7bc6c55dd248270ee0ab4212cd0ef8ea04a
Gitweb: http://git.kernel.org/tip/0a87e7bc6c55dd248270ee0ab4212cd0ef8ea04a
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 24 Jan 2017 13:19:06 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: e28ff1a8382ee02b10cf11cf3b48541dc3d14a58
Gitweb: http://git.kernel.org/tip/e28ff1a8382ee02b10cf11cf3b48541dc3d14a58
Author: Joe Stringer
AuthorDate: Sun, 22 Jan 2017 17:11:25 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan 2017 11:42:58 -0300
tools lib
Commit-ID: 0a87e7bc6c55dd248270ee0ab4212cd0ef8ea04a
Gitweb: http://git.kernel.org/tip/0a87e7bc6c55dd248270ee0ab4212cd0ef8ea04a
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 24 Jan 2017 13:19:06 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan 2017 11:42:59 -0300
This bug appears to have existed for a long time:
https://www.spinics.net/lists/netdev/msg222459.html
http://www.kernelhub.org/?p=2=823752
Though possibly with different things not setting the "input" function
pointer in the "struct dst_entry".
include/net/dst.h:
496 static
This bug appears to have existed for a long time:
https://www.spinics.net/lists/netdev/msg222459.html
http://www.kernelhub.org/?p=2=823752
Though possibly with different things not setting the "input" function
pointer in the "struct dst_entry".
include/net/dst.h:
496 static
On Thu, Jan 26, 2017 at 04:05:25PM +0100, Ingo Molnar wrote:
> diff --git a/arch/x86/include/asm/switch_to.h
> b/arch/x86/include/asm/switch_to.h
> index a7146dadb31d..7a4915dd0547 100644
> --- a/arch/x86/include/asm/switch_to.h
> +++ b/arch/x86/include/asm/switch_to.h
> @@ -78,7 +78,7 @@ do {
On Thu, Jan 26, 2017 at 04:05:25PM +0100, Ingo Molnar wrote:
> diff --git a/arch/x86/include/asm/switch_to.h
> b/arch/x86/include/asm/switch_to.h
> index a7146dadb31d..7a4915dd0547 100644
> --- a/arch/x86/include/asm/switch_to.h
> +++ b/arch/x86/include/asm/switch_to.h
> @@ -78,7 +78,7 @@ do {
Add the fb->offset[] value to the plane's physical start address
registe. Without that, packed formats are rendered incorrectly.
Signed-off-by: Liviu Dudau
---
drivers/gpu/drm/arm/malidp_planes.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Add the fb->offset[] value to the plane's physical start address
registe. Without that, packed formats are rendered incorrectly.
Signed-off-by: Liviu Dudau
---
drivers/gpu/drm/arm/malidp_planes.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/arm/malidp_planes.c
Commit-ID: d1d0e29cb7d03a6019caa125e4c0288366a4f359
Gitweb: http://git.kernel.org/tip/d1d0e29cb7d03a6019caa125e4c0288366a4f359
Author: Markus Elfring
AuthorDate: Mon, 23 Jan 2017 15:10:19 +0100
Committer: Arnaldo Carvalho de Melo
Commit-ID: d1d0e29cb7d03a6019caa125e4c0288366a4f359
Gitweb: http://git.kernel.org/tip/d1d0e29cb7d03a6019caa125e4c0288366a4f359
Author: Markus Elfring
AuthorDate: Mon, 23 Jan 2017 15:10:19 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 26 Jan 2017 11:42:56 -0300
perf probe:
Commit-ID: 190bacca16d0627dce1d4ceb873f041ebbaef69a
Gitweb: http://git.kernel.org/tip/190bacca16d0627dce1d4ceb873f041ebbaef69a
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:32 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan
Commit-ID: 190bacca16d0627dce1d4ceb873f041ebbaef69a
Gitweb: http://git.kernel.org/tip/190bacca16d0627dce1d4ceb873f041ebbaef69a
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:32 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan 2017 16:52:56 -0300
perf c2c report:
Commit-ID: 8763e6ac2d368ac9d650df35b00c3af2a7c1878b
Gitweb: http://git.kernel.org/tip/8763e6ac2d368ac9d650df35b00c3af2a7c1878b
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:31 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan
Commit-ID: 8763e6ac2d368ac9d650df35b00c3af2a7c1878b
Gitweb: http://git.kernel.org/tip/8763e6ac2d368ac9d650df35b00c3af2a7c1878b
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:31 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan 2017 16:52:43 -0300
perf c2c report:
Commit-ID: 0e3fa7a7acdd5f6ec89b3692276e35006c06fb92
Gitweb: http://git.kernel.org/tip/0e3fa7a7acdd5f6ec89b3692276e35006c06fb92
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:30 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan
Commit-ID: 0e3fa7a7acdd5f6ec89b3692276e35006c06fb92
Gitweb: http://git.kernel.org/tip/0e3fa7a7acdd5f6ec89b3692276e35006c06fb92
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:30 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan 2017 13:37:26 -0300
perf hists
Commit-ID: b33f922651011effafec4508474e8591569a3e98
Gitweb: http://git.kernel.org/tip/b33f922651011effafec4508474e8591569a3e98
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:29 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan
Commit-ID: b33f922651011effafec4508474e8591569a3e98
Gitweb: http://git.kernel.org/tip/b33f922651011effafec4508474e8591569a3e98
Author: Jiri Olsa
AuthorDate: Fri, 20 Jan 2017 10:20:29 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 20 Jan 2017 10:04:45 -0300
perf hists
Commit-ID: 9343e45bf6cc4a05f6e271e9f8d06bc87875c604
Gitweb: http://git.kernel.org/tip/9343e45bf6cc4a05f6e271e9f8d06bc87875c604
Author: Matija Glavinic Pecotic
AuthorDate: Tue, 17 Jan 2017 15:50:35 +0100
Committer: Arnaldo Carvalho de Melo
Commit-ID: 9343e45bf6cc4a05f6e271e9f8d06bc87875c604
Gitweb: http://git.kernel.org/tip/9343e45bf6cc4a05f6e271e9f8d06bc87875c604
Author: Matija Glavinic Pecotic
AuthorDate: Tue, 17 Jan 2017 15:50:35 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 18 Jan 2017 12:29:52 -0300
On Monday 23 January 2017 02:47 AM, Bjorn Andersson wrote:
> The error paths of the common qcom-ufs functions for registering the
> phy, acquiring clocks and acquiring regulators all print specific error
> messages before returning an error, so there is no value in printing yet
> another - more
On Monday 23 January 2017 02:47 AM, Bjorn Andersson wrote:
> The error paths of the common qcom-ufs functions for registering the
> phy, acquiring clocks and acquiring regulators all print specific error
> messages before returning an error, so there is no value in printing yet
> another - more
On Thu, 26 Jan 2017, Borislav Petkov wrote:
> On Thu, Jan 26, 2017 at 03:51:25PM +0200, Jani Nikula wrote:
>> On Thu, 26 Jan 2017, Borislav Petkov wrote:
>> > Hi all,
>> >
>> > I see this brand new warning when booting here.
>> >
>> > Top commit is
On Thu, 26 Jan 2017, Borislav Petkov wrote:
> On Thu, Jan 26, 2017 at 03:51:25PM +0200, Jani Nikula wrote:
>> On Thu, 26 Jan 2017, Borislav Petkov wrote:
>> > Hi all,
>> >
>> > I see this brand new warning when booting here.
>> >
>> > Top commit is v4.10-rc5-107-g883af14e67e8 from Linus' master.
On Thursday 26 January 2017 04:02 AM, Stephen Boyd wrote:
> This patch series continues the usb chipidea rewrite for
> Qualcommm platforms. I've dropped the patches that were applied
> to Peter's tree for chipidea. Now the phy drivers are left,
> along with the patch to call phy_set_mode() at
On Thursday 26 January 2017 04:02 AM, Stephen Boyd wrote:
> This patch series continues the usb chipidea rewrite for
> Qualcommm platforms. I've dropped the patches that were applied
> to Peter's tree for chipidea. Now the phy drivers are left,
> along with the patch to call phy_set_mode() at
nvmf_create_ctrl() relys on the presence of a create_crtl callback in the
registered nvmf_transport_ops, so make nvmf_register_transport require one.
Update the available call-sites as well to reflect these changes.
Signed-off-by: Johannes Thumshirn
---
nvmf_create_ctrl() relys on the presence of a create_crtl callback in the
registered nvmf_transport_ops, so make nvmf_register_transport require one.
Update the available call-sites as well to reflect these changes.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/fabrics.c | 7 ++-
On Wed, Jan 25, 2017 at 1:06 AM, Furquan Shaikh wrote:
> Sometimes (as the case with fixed regulator) we only want to look up,
> but not necessarily reserve right away, GPIO. gpiod_lookup() and
> gpiod_lookup_by_index() allow us doing just that.
>
> Signed-off-by: Dmitry
On Wed, Jan 25, 2017 at 1:06 AM, Furquan Shaikh wrote:
> Sometimes (as the case with fixed regulator) we only want to look up,
> but not necessarily reserve right away, GPIO. gpiod_lookup() and
> gpiod_lookup_by_index() allow us doing just that.
>
> Signed-off-by: Dmitry Torokhov
>
This patch adds support for 32 bit GEM in
64 bit system. It checks capability at runtime
and uses appropriate buffer descriptor.
Signed-off-by: Rafal Ozieblo
---
drivers/net/ethernet/cadence/macb.c | 183 +---
This patch adds support for 32 bit GEM in
64 bit system. It checks capability at runtime
and uses appropriate buffer descriptor.
Signed-off-by: Rafal Ozieblo
---
drivers/net/ethernet/cadence/macb.c | 183 +---
drivers/net/ethernet/cadence/macb.h | 20 +++-
2
On Thu, Jan 26, 2017 at 03:51:25PM +0200, Jani Nikula wrote:
> On Thu, 26 Jan 2017, Borislav Petkov wrote:
> > Hi all,
> >
> > I see this brand new warning when booting here.
> >
> > Top commit is v4.10-rc5-107-g883af14e67e8 from Linus' master.
>
> Please try [1].
Maybe I should
On Thu, Jan 26, 2017 at 03:51:25PM +0200, Jani Nikula wrote:
> On Thu, 26 Jan 2017, Borislav Petkov wrote:
> > Hi all,
> >
> > I see this brand new warning when booting here.
> >
> > Top commit is v4.10-rc5-107-g883af14e67e8 from Linus' master.
>
> Please try [1].
Maybe I should wait until Dave
On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote:
> On Mon, Jan 23, 2017 at 09:37:11PM -0800, James Bottomley wrote:
> > sessions are different from transient objects in that their handles
> > may not be virtualized (because they're used for some hmac
> > calculations). Additionally when
On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote:
> On Mon, Jan 23, 2017 at 09:37:11PM -0800, James Bottomley wrote:
> > sessions are different from transient objects in that their handles
> > may not be virtualized (because they're used for some hmac
> > calculations). Additionally when
Hi Chris,
On ven., janv. 13 2017, Chris Packham
wrote:
> The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with
> integrated CPUs. They CPU block is common within these product lines and
> (as far as I can tell/have been told) is based on the
Hi Chris,
On ven., janv. 13 2017, Chris Packham
wrote:
> The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with
> integrated CPUs. They CPU block is common within these product lines and
> (as far as I can tell/have been told) is based on the Armada XP. There
> are a few
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> > We want to simplify the FPU state machine by eliminating fpu-
> > >fpregs_active,
> > and we can do that because the two state flags (::fpregs_active and
> > ::fpstate_active) are set essentially
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> > We want to simplify the FPU state machine by eliminating fpu-
> > >fpregs_active,
> > and we can do that because the two state flags (::fpregs_active and
> > ::fpstate_active) are set essentially together.
> >
>
> -Original Message-
> From: Andrei Pistirica [mailto:andrei.pistir...@microchip.com]
> Sent: 19 stycznia 2017 16:56
> Subject: [PATCH net-next v2] macb: Common code to enable ptp support for
> MACB/GEM
>
>
> +static inline bool gem_has_ptp(struct macb *bp)
> +{
> + return
> -Original Message-
> From: Andrei Pistirica [mailto:andrei.pistir...@microchip.com]
> Sent: 19 stycznia 2017 16:56
> Subject: [PATCH net-next v2] macb: Common code to enable ptp support for
> MACB/GEM
>
>
> +static inline bool gem_has_ptp(struct macb *bp)
> +{
> + return
Hi Chris,
On ven., janv. 06 2017, Chris Packham
wrote:
> These boards are Marvell's evaluation boards for the 98DX4251 and
> 98DX3336 SoCs.
>
> Signed-off-by: Chris Packham
> ---
> Change in v2/v3:
> - None
>
>
Hi Chris,
On ven., janv. 06 2017, Chris Packham
wrote:
> These boards are Marvell's evaluation boards for the 98DX4251 and
> 98DX3336 SoCs.
>
> Signed-off-by: Chris Packham
> ---
> Change in v2/v3:
> - None
>
> arch/arm/boot/dts/db-dxbc2.dts | 159
>
On Thu, 2017-01-26 at 11:17 +, Augusto Mecking Caringi wrote:
> In a 64bit system (where long is 64bit wide), even dividing LONG_MAX by
> HZ will always be bigger than the max value that an int variable can
> hold.
>
> This has been detected by building the driver with W=1:
>
>
On Thu, 2017-01-26 at 11:17 +, Augusto Mecking Caringi wrote:
> In a 64bit system (where long is 64bit wide), even dividing LONG_MAX by
> HZ will always be bigger than the max value that an int variable can
> hold.
>
> This has been detected by building the driver with W=1:
>
>
On 01/25/2017 04:32 PM, Rob Herring wrote:
On Wed, Jan 25, 2017 at 10:59 AM, Dave Gerlach wrote:
On 01/24/2017 04:03 AM, Ulf Hansson wrote:
On 23 January 2017 at 21:11, Dave Gerlach wrote:
On 01/20/2017 10:52 AM, Ulf Hansson wrote:
[...]
Another
On 01/25/2017 04:32 PM, Rob Herring wrote:
On Wed, Jan 25, 2017 at 10:59 AM, Dave Gerlach wrote:
On 01/24/2017 04:03 AM, Ulf Hansson wrote:
On 23 January 2017 at 21:11, Dave Gerlach wrote:
On 01/20/2017 10:52 AM, Ulf Hansson wrote:
[...]
Another option is create something new either
Hi Chris,
On ven., janv. 06 2017, Chris Packham
wrote:
> The Marvell 98DX3236, 98DX3336, 98DX4521 and variants are switch ASICs
> with integrated CPUs. They are similar to the Armada XP SoCs but have
> different I/O interfaces.
Before sending a new version
Hi Chris,
On ven., janv. 06 2017, Chris Packham
wrote:
> The Marvell 98DX3236, 98DX3336, 98DX4521 and variants are switch ASICs
> with integrated CPUs. They are similar to the Armada XP SoCs but have
> different I/O interfaces.
Before sending a new version I have a few remarks:
> diff
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
>
> > index c56fb57f2991..7eb2f3041fde 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -1253,6 +1253,8 @@ void set_task_cpu(struct task_struct *p,
> > unsigned int new_cpu)
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
>
> > index c56fb57f2991..7eb2f3041fde 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -1253,6 +1253,8 @@ void set_task_cpu(struct task_struct *p,
> > unsigned int new_cpu)
> >
On Thu, 26 Jan 2017 15:53:29 +0100,
Bhumika Goyal wrote:
>
> Declare snd_pcm_ops structures as const as they are either stored in the
> ops field of a snd_pcm_substream structure or passed as an argument to the
> function snd_pcm_set_ops. The function argument and the ops field
> are of type
On Thu, 26 Jan 2017 15:53:29 +0100,
Bhumika Goyal wrote:
>
> Declare snd_pcm_ops structures as const as they are either stored in the
> ops field of a snd_pcm_substream structure or passed as an argument to the
> function snd_pcm_set_ops. The function argument and the ops field
> are of type
On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne
> > wrote:
> >
> > [...]
> >
> > >
> > > Are all of these builds using the tests from
On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne
> > wrote:
> >
> > [...]
> >
> > >
> > > Are all of these builds using the tests from
Am Donnerstag, 26. Januar 2017, 14:29:17 CET schrieb Linus Walleij:
> On Sun, Jan 22, 2017 at 9:38 AM, David Wu wrote:
> > From: "david.wu"
> >
> > This patch supports 3bit width iomux type.
> > Note, the iomux of following pins are special,
Am Donnerstag, 26. Januar 2017, 14:29:17 CET schrieb Linus Walleij:
> On Sun, Jan 22, 2017 at 9:38 AM, David Wu wrote:
> > From: "david.wu"
> >
> > This patch supports 3bit width iomux type.
> > Note, the iomux of following pins are special, need to
> > be handled specially.
> >
> > -
* Ingo Molnar wrote:
> What we could do is to unify the naming to explain all this a bit better -
> right
> now there's very little indication that ->fpregs_cached is closely related to
> fpu_fpregs_owner_ctx.
>
> For example we could rename them to:
>
>
* Ingo Molnar wrote:
> What we could do is to unify the naming to explain all this a bit better -
> right
> now there's very little indication that ->fpregs_cached is closely related to
> fpu_fpregs_owner_ctx.
>
> For example we could rename them to:
>
> ->fpregs_cached =>
On 01/25/2017 05:57 PM, r...@redhat.com wrote:
> /*
> + * Restoring SSE/YMM state requires that MXCSR & MXCSR_MASK are saved.
> + * Those fields are part of the legacy FP state, and only get saved
> + * above if XFEATURES_MASK_FP is set.
> + *
> + * Copy out those
On 01/25/2017 05:57 PM, r...@redhat.com wrote:
> /*
> + * Restoring SSE/YMM state requires that MXCSR & MXCSR_MASK are saved.
> + * Those fields are part of the legacy FP state, and only get saved
> + * above if XFEATURES_MASK_FP is set.
> + *
> + * Copy out those
Le 23/01/2017 à 15:45, cristian.bir...@microchip.com a écrit :
> From: Cristian Birsan
>
> Update atmel udc driver with a new enpoint allocation scheme. The data
> sheet requires that all endpoints are allocated in order.
Pieces of information from the cover
Le 23/01/2017 à 15:45, cristian.bir...@microchip.com a écrit :
> From: Cristian Birsan
>
> Update atmel udc driver with a new enpoint allocation scheme. The data
> sheet requires that all endpoints are allocated in order.
Pieces of information from the cover letter could have been added here.
On Wed, 2016-06-29 at 19:28 +1000, Peter Hutterer wrote:
> If the 0x1000 Unified Battery Level Status feature exists, expose the battery
> level.
>
> The main drawback is that while a device is plugged in its battery level is 0.
> To avoid exposing that as 0% charge we make up a number based on
On Wed, 2016-06-29 at 19:28 +1000, Peter Hutterer wrote:
> If the 0x1000 Unified Battery Level Status feature exists, expose the battery
> level.
>
> The main drawback is that while a device is plugged in its battery level is 0.
> To avoid exposing that as 0% charge we make up a number based on
As stated in the commit message, different machines can use different values to
represent LED ON/OFF, and this commit makes sure we use the correct value pair
for each _HID.
I don't know if there is a better way to store these pairs than in a structure
matching the device_ids[] indexing that
As stated in the commit message, different machines can use different values to
represent LED ON/OFF, and this commit makes sure we use the correct value pair
for each _HID.
I don't know if there is a better way to store these pairs than in a structure
matching the device_ids[] indexing that
Some Asus machines use 0x4/0x5 as their LED on/off values, while others use
0x0/0x1, as shown in the DSDT exerpts below (note "Arg0 == 0x02", used to get
the LED status). Luckly it seems this behavior is tied to different HIDs, after
looking at 44 DSDTs from different Asus models.
Another small
Some Asus machines use 0x4/0x5 as their LED on/off values, while others use
0x0/0x1, as shown in the DSDT exerpts below (note "Arg0 == 0x02", used to get
the LED status). Luckly it seems this behavior is tied to different HIDs, after
looking at 44 DSDTs from different Asus models.
Another small
/commits/Michal-Hocko/net-bpf-use-kvzalloc-helper/20170126-221904
config: x86_64-randconfig-x014-201704 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed
/commits/Michal-Hocko/net-bpf-use-kvzalloc-helper/20170126-221904
config: x86_64-randconfig-x014-201704 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed
Hi Randy,
2017-01-25 1:40 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Fix build errors in phy-rockchip-inno-usb2.c. The driver uses
> extcon interfaces so it should depend on EXTCON.
>
> Fixes these build errors:
>
> drivers/built-in.o: In
Hi Randy,
2017-01-25 1:40 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Fix build errors in phy-rockchip-inno-usb2.c. The driver uses
> extcon interfaces so it should depend on EXTCON.
>
> Fixes these build errors:
>
> drivers/built-in.o: In function `rockchip_usb2phy_otg_sm_work':
>
On Tue, Jan 24, 2017 at 9:01 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data
On Tue, Jan 24, 2017 at 9:01 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data call and
> request_irq
On Tue, Jan 24, 2017 at 9:01 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data
On Tue, Jan 24, 2017 at 9:01 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data call with
> the
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data call and
> request_irq
On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> index c56fb57f2991..7eb2f3041fde 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1253,6 +1253,8 @@ void set_task_cpu(struct task_struct *p,
> unsigned int new_cpu)
>
On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> index c56fb57f2991..7eb2f3041fde 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1253,6 +1253,8 @@ void set_task_cpu(struct task_struct *p,
> unsigned int new_cpu)
>
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> >
> > @@ -322,6 +308,16 @@ struct fpu {
> > unsigned char fpregs_active;
> >
> > /*
> > + * @fpregs_cached:
> > + *
> > + * This flag tells us whether this
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data call and
> request_irq
* Rik van Riel wrote:
> On Thu, 2017-01-26 at 12:26 +0100, Ingo Molnar wrote:
> >
> > @@ -322,6 +308,16 @@ struct fpu {
> > unsigned char fpregs_active;
> >
> > /*
> > + * @fpregs_cached:
> > + *
> > + * This flag tells us whether this context is loaded
[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote:
> On 01/25/2017 09:38 PM, Stafford Horne wrote:
> >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> >>>[Re: linux-next: Tree for Jan 19] On 23/01/2017
Declare snd_pcm_ops structures as const as they are either stored in the
ops field of a snd_pcm_substream structure or passed as an argument to the
function snd_pcm_set_ops. The function argument and the ops field
are of type const, so snd_pcm_ops structures having this property
can be made
Declare snd_pcm_ops structures as const as they are either stored in the
ops field of a snd_pcm_substream structure or passed as an argument to the
function snd_pcm_set_ops. The function argument and the ops field
are of type const, so snd_pcm_ops structures having this property
can be made
[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote:
> On 01/25/2017 09:38 PM, Stafford Horne wrote:
> >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> >>>[Re: linux-next: Tree for Jan 19] On 23/01/2017
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data
On Tue, Jan 24, 2017 at 9:00 PM, William Breathitt Gray
wrote:
> The devm_ resource manager functions allow memory to be automatically
> released when a device is unbound. This patch takes advantage of the
> resource manager functions and replaces the gpiochip_add_data call and
> request_irq
On Thu, Jan 26, 2017 at 08:38:58AM -0500, Cathy Avery wrote:
> Included in the current storvsc driver for Hyper-V is the ability
> to access luns on an FC fabric via a virtualized fiber channel
> adapter exposed by the Hyper-V host. This was done to provide an
> interface for existing customer
On Thu, Jan 26, 2017 at 08:38:58AM -0500, Cathy Avery wrote:
> Included in the current storvsc driver for Hyper-V is the ability
> to access luns on an FC fabric via a virtualized fiber channel
> adapter exposed by the Hyper-V host. This was done to provide an
> interface for existing customer
801 - 900 of 1558 matches
Mail list logo