On Mon, Apr 17, 2017 at 03:03:29PM -0700, Andy Lutomirski wrote:
> On Fri, Apr 14, 2017 at 4:05 PM, Darren Hart wrote:
> > On Sat, Apr 15, 2017 at 12:45:30AM +0200, Rafael Wysocki wrote:
> >> On Wednesday, April 12, 2017 04:08:54 PM Darren Hart wrote:
> >> > Hi All,
> >> >
>
On Mon, Apr 17, 2017 at 03:03:29PM -0700, Andy Lutomirski wrote:
> On Fri, Apr 14, 2017 at 4:05 PM, Darren Hart wrote:
> > On Sat, Apr 15, 2017 at 12:45:30AM +0200, Rafael Wysocki wrote:
> >> On Wednesday, April 12, 2017 04:08:54 PM Darren Hart wrote:
> >> > Hi All,
> >> >
> >> > There are a few
By pressing 'a' in the hists browser, the user gets an annotated view of
the code of the selected symbols.
This patch adds the case 'A'; if this key is pressed (and if the
call-graph option was enabled at record time), perf will build
the callchain from the top frame until the selected symbol and
The per-callchain histograms must be fed at some points with the
profiling samples. A solution is to fill them right after having filled
the per-symbol ones: in the callback hist_iter__report_callback.
Signed-off-by: Alexis Berlemont
---
tools/perf/builtin-report.c |
By pressing 'a' in the hists browser, the user gets an annotated view of
the code of the selected symbols.
This patch adds the case 'A'; if this key is pressed (and if the
call-graph option was enabled at record time), perf will build
the callchain from the top frame until the selected symbol and
The per-callchain histograms must be fed at some points with the
profiling samples. A solution is to fill them right after having filled
the per-symbol ones: in the callback hist_iter__report_callback.
Signed-off-by: Alexis Berlemont
---
tools/perf/builtin-report.c | 8
1 file changed,
A symbol can be called from various points and according to its calling
context, it can provide different results.
This patch creates one histogram for every different callchain recorded
and accumulates profiling samples into the appropriate one. Samples
recorded with the same callchain are not
A symbol can be called from various points and according to its calling
context, it can provide different results.
This patch creates one histogram for every different callchain recorded
and accumulates profiling samples into the appropriate one. Samples
recorded with the same callchain are not
Hi,
These patches are a proposal to fulfill the following point of perf's TODO list
(https://perf.wiki.kernel.org/index.php/Todo):
* What I want is that if I am on bar*(), it annotates bar*(), no samples just
the call site (obtained from the callchain) dissassembly. This is useful
because in
Hi,
These patches are a proposal to fulfill the following point of perf's TODO list
(https://perf.wiki.kernel.org/index.php/Todo):
* What I want is that if I am on bar*(), it annotates bar*(), no samples just
the call site (obtained from the callchain) dissassembly. This is useful
because in
rate_flg is of type 'enum nl80211_attrs', however it is assigned with
'enum nl80211_rate_info' values. Change the type of rate_flg accordingly.
Signed-off-by: Matthias Kaehlcke
---
net/wireless/nl80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
rate_flg is of type 'enum nl80211_attrs', however it is assigned with
'enum nl80211_rate_info' values. Change the type of rate_flg accordingly.
Signed-off-by: Matthias Kaehlcke
---
net/wireless/nl80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/wireless/nl80211.c
On Wed, Apr 12 2017, Jeff Layton wrote:
> On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote:
>>
>> I suspect that the filemap_check_wb_error() will need to be moved
>> into some parent of the current call site, which is essentially what you
>> suggest below. It would be nice if we could do
On Tue, Apr 18, 2017 at 12:32 AM, Guenter Roeck wrote:
> On Mon, Apr 17, 2017 at 11:29:38PM +0200, Rafael J. Wysocki wrote:
>> On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
>> > On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>> >>
On Wed, Apr 12 2017, Jeff Layton wrote:
> On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote:
>>
>> I suspect that the filemap_check_wb_error() will need to be moved
>> into some parent of the current call site, which is essentially what you
>> suggest below. It would be nice if we could do
On Tue, Apr 18, 2017 at 12:32 AM, Guenter Roeck wrote:
> On Mon, Apr 17, 2017 at 11:29:38PM +0200, Rafael J. Wysocki wrote:
>> On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
>> > On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>> >>
[cut]
>> >> [Moore, Robert]
>> >>
>>
On Wed, Apr 12 2017, Jeff Layton wrote:
> On Thu, 2017-04-13 at 07:55 +1000, NeilBrown wrote:
>> On Wed, Apr 12 2017, Jeff Layton wrote:
>>
>>
>> > +void __filemap_set_wb_error(struct address_space *mapping, int err)
>>
>> I was really hoping that this would be
>>
>> void
On Wed, Apr 12 2017, Jeff Layton wrote:
> On Thu, 2017-04-13 at 07:55 +1000, NeilBrown wrote:
>> On Wed, Apr 12 2017, Jeff Layton wrote:
>>
>>
>> > +void __filemap_set_wb_error(struct address_space *mapping, int err)
>>
>> I was really hoping that this would be
>>
>> void
On Fri, Apr 14, 2017 at 03:10:30PM -0300, Helen Koike wrote:
> + Add missing maintainers from scripts/get_maintainer.pl in the email thread
>
> Hi,
>
> I would like to know if it would be possible to get this patch for kernel
> 4.12.
> Should I send a pull request? Or do you usually get the
On Fri, Apr 14, 2017 at 03:10:30PM -0300, Helen Koike wrote:
> + Add missing maintainers from scripts/get_maintainer.pl in the email thread
>
> Hi,
>
> I would like to know if it would be possible to get this patch for kernel
> 4.12.
> Should I send a pull request? Or do you usually get the
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.hotplug
commit 6362ef376aacbc309022ad12f08693d201cdda08
Author: Thomas Gleixner
AuthorDate: Thu Apr 13 10:50:55 2017
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.hotplug
commit 6362ef376aacbc309022ad12f08693d201cdda08
Author: Thomas Gleixner
AuthorDate: Thu Apr 13 10:50:55 2017 +0200
Commit: Thomas
Make sure the start adderess is aligned to PMD_SIZE
boundary when freeing page table backing a hugepage
region. The issue was causing segfaults when a region
backed by 64K pages was unmapped since such a region
is in general not PMD_SIZE aligned.
Signed-off-by: Nitin Gupta
Make sure the start adderess is aligned to PMD_SIZE
boundary when freeing page table backing a hugepage
region. The issue was causing segfaults when a region
backed by 64K pages was unmapped since such a region
is in general not PMD_SIZE aligned.
Signed-off-by: Nitin Gupta
---
vfio_pin_pages_remote() is typically called to iterate over a range
of memory. Testing CAP_IPC_LOCK is relatively expensive, so it makes
sense to push it up to the caller, which can then repeatedly call
vfio_pin_pages_remote() using that value. This can show nearly a 20%
improvement on the worst
vfio_pin_pages_remote() is typically called to iterate over a range
of memory. Testing CAP_IPC_LOCK is relatively expensive, so it makes
sense to push it up to the caller, which can then repeatedly call
vfio_pin_pages_remote() using that value. This can show nearly a 20%
improvement on the worst
If the mmap_sem is contented then the vfio type1 IOMMU backend will
defer locked page accounting updates to a workqueue task. This has a
few problems and depending on which side the user tries to play, they
might be over-penalized for unmaps that haven't yet been accounted or
race the workqueue
v5:
- patch 1/ Use bool* to cleanup vfio_lock_acct() callers; sorry
we cannot re-test CAP_IPC_LOCK for all callers
- patch 2/ Re-add pr_warn, add Kirti's R-b
- patch 3/ NEW, analyzing impact of vfio_lock_acct() testing
CAP_IPC_LOCK for all callers revealed a long
v5:
- patch 1/ Use bool* to cleanup vfio_lock_acct() callers; sorry
we cannot re-test CAP_IPC_LOCK for all callers
- patch 2/ Re-add pr_warn, add Kirti's R-b
- patch 3/ NEW, analyzing impact of vfio_lock_acct() testing
CAP_IPC_LOCK for all callers revealed a long
If the mmap_sem is contented then the vfio type1 IOMMU backend will
defer locked page accounting updates to a workqueue task. This has a
few problems and depending on which side the user tries to play, they
might be over-penalized for unmaps that haven't yet been accounted or
race the workqueue
With vfio_lock_acct() testing the locked memory limit under mmap_sem,
it's redundant to do it here for a single page. We can also reorder
our tests such that we can avoid testing for reserved pages if we're
not doing accounting and let vfio_lock_acct() test the process
CAP_IPC_LOCK. Finally,
With vfio_lock_acct() testing the locked memory limit under mmap_sem,
it's redundant to do it here for a single page. We can also reorder
our tests such that we can avoid testing for reserved pages if we're
not doing accounting and let vfio_lock_acct() test the process
CAP_IPC_LOCK. Finally,
On Fri, Feb 24, 2017 at 2:46 PM, John Stultz wrote:
> Hey John,
> So after the USB tree landed in 4.11-rc, I've been seeing the
> following warning at bootup.
>
> It seems the fifo_mem/total_fifo_size value on hikey is 1920, but I'm
> seeing the addresses zip upward
On Fri, Feb 24, 2017 at 2:46 PM, John Stultz wrote:
> Hey John,
> So after the USB tree landed in 4.11-rc, I've been seeing the
> following warning at bootup.
>
> It seems the fifo_mem/total_fifo_size value on hikey is 1920, but I'm
> seeing the addresses zip upward quickly as the txfsz values
On Mon, Apr 17, 2017 at 11:29:38PM +0200, Rafael J. Wysocki wrote:
> On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
> > On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
> >>
> >>
> >> > -Original Message-
> >> > From: Guenter Roeck
On Mon, Apr 17, 2017 at 11:29:38PM +0200, Rafael J. Wysocki wrote:
> On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
> > On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
> >>
> >>
> >> > -Original Message-
> >> > From: Guenter Roeck [mailto:li...@roeck-us.net]
> >> >
On Sun, 16 Apr 2017, Greg Thelen wrote:
> Each slab kmem cache has per cpu array caches. The array caches are
> created when the kmem_cache is created, either via kmem_cache_create()
> or lazily when the first object is allocated in context of a kmem
> enabled memcg. Array caches are replaced
On Sun, 16 Apr 2017, Greg Thelen wrote:
> Each slab kmem cache has per cpu array caches. The array caches are
> created when the kmem_cache is created, either via kmem_cache_create()
> or lazily when the first object is allocated in context of a kmem
> enabled memcg. Array caches are replaced
On 4/17/2017 4:55 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 17 Apr 2017 22:42:40 +0200
>
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the
On 4/17/2017 4:55 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 17 Apr 2017 22:42:40 +0200
>
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function
On Freitag, 14. April 2017 17:12:03 CEST Jonathan Cameron wrote:
> On 12/04/17 04:01, Stefan Brüns wrote:
> > Reducing shunt and bus voltage range improves the accuracy, so allow
> > altering the default settings.
> >
> > Signed-off-by: Stefan Brüns
>
> Hi Stefan,
On Freitag, 14. April 2017 17:12:03 CEST Jonathan Cameron wrote:
> On 12/04/17 04:01, Stefan Brüns wrote:
> > Reducing shunt and bus voltage range improves the accuracy, so allow
> > altering the default settings.
> >
> > Signed-off-by: Stefan Brüns
>
> Hi Stefan,
>
> There is new userspace
On Fri, Apr 14, 2017 at 4:05 PM, Darren Hart wrote:
> On Sat, Apr 15, 2017 at 12:45:30AM +0200, Rafael Wysocki wrote:
>> On Wednesday, April 12, 2017 04:08:54 PM Darren Hart wrote:
>> > Hi All,
>> >
>> > There are a few parallel efforts involving the Windows Management
>> >
On Fri, Apr 14, 2017 at 4:05 PM, Darren Hart wrote:
> On Sat, Apr 15, 2017 at 12:45:30AM +0200, Rafael Wysocki wrote:
>> On Wednesday, April 12, 2017 04:08:54 PM Darren Hart wrote:
>> > Hi All,
>> >
>> > There are a few parallel efforts involving the Windows Management
>> > Instrumentation
On 4/17/2017 5:44 PM, Sinan Kaya wrote:
> Any idea what happened to the change in this function during merge?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ae7c18380495ac5c14a614fdb6c452c3bf9148ac
>
I realized that there is a V9 out there. I'm catching up
On 4/17/2017 5:44 PM, Sinan Kaya wrote:
> Any idea what happened to the change in this function during merge?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ae7c18380495ac5c14a614fdb6c452c3bf9148ac
>
I realized that there is a V9 out there. I'm catching up
On Tue, Apr 11, 2017 at 10:03 AM, Michal Hocko wrote:
> All the reported issue seem to be fixed and pushed to my git tree
> attempts/rewrite-mem_hotplug branch. I will wait a day or two for more
> feedback and then repost for the inclusion. I would really appreaciate
> more
On Tue, Apr 11, 2017 at 10:03 AM, Michal Hocko wrote:
> All the reported issue seem to be fixed and pushed to my git tree
> attempts/rewrite-mem_hotplug branch. I will wait a day or two for more
> feedback and then repost for the inclusion. I would really appreaciate
> more testing/review!
This
Sean Paul writes:
> On Mon, Apr 17, 2017 at 09:26:03AM -0700, Eric Anholt wrote:
>> We were returning without decrementing if the error happened, meaning
>> that at the next submit we wouldn't try to bring up the power domain.
>>
>> Signed-off-by: Eric Anholt
Sean Paul writes:
> On Mon, Apr 17, 2017 at 09:26:03AM -0700, Eric Anholt wrote:
>> We were returning without decrementing if the error happened, meaning
>> that at the next submit we wouldn't try to bring up the power domain.
>>
>> Signed-off-by: Eric Anholt
>
> This change looks good to me.
On 1/18/2017 7:55 AM, Hanjun Guo wrote:
> --- a/drivers/irqchip/irq-gic-v3-its-platform-msi.c
> +++ b/drivers/irqchip/irq-gic-v3-its-platform-msi.c
> @@ -57,7 +57,8 @@ static int its_pmsi_prepare(struct irq_domain *domain,
> struct device *dev,
>
> msi_info =
On 1/18/2017 7:55 AM, Hanjun Guo wrote:
> --- a/drivers/irqchip/irq-gic-v3-its-platform-msi.c
> +++ b/drivers/irqchip/irq-gic-v3-its-platform-msi.c
> @@ -57,7 +57,8 @@ static int its_pmsi_prepare(struct irq_domain *domain,
> struct device *dev,
>
> msi_info =
On Wed, 12 Apr 2017, David Howells wrote:
>
> Hi James,
>
> Could you pull these changes into security/next please:
>
> (1) Provide a blacklist keyring and a blacklist key type such that X.509
> keys and PKCS#7 certs can be blacklisted. It is possible to load the
> blacklist from a
On Wed, 12 Apr 2017, David Howells wrote:
>
> Hi James,
>
> Could you pull these changes into security/next please:
>
> (1) Provide a blacklist keyring and a blacklist key type such that X.509
> keys and PKCS#7 certs can be blacklisted. It is possible to load the
> blacklist from a
On Tue, 18 Apr 2017 01:02:12 +0530
Kirti Wankhede wrote:
> On 4/18/2017 12:49 AM, Alex Williamson wrote:
> > On Tue, 18 Apr 2017 00:35:06 +0530
> > Kirti Wankhede wrote:
> >
> >> On 4/17/2017 8:02 PM, Alex Williamson wrote:
> >>> On Mon, 17 Apr
On Tue, 18 Apr 2017 01:02:12 +0530
Kirti Wankhede wrote:
> On 4/18/2017 12:49 AM, Alex Williamson wrote:
> > On Tue, 18 Apr 2017 00:35:06 +0530
> > Kirti Wankhede wrote:
> >
> >> On 4/17/2017 8:02 PM, Alex Williamson wrote:
> >>> On Mon, 17 Apr 2017 14:47:54 +0800
> >>> Peter Xu wrote:
>
On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
> On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>>
>>
>> > -Original Message-
>> > From: Guenter Roeck [mailto:li...@roeck-us.net]
>> > Sent: Monday, April 17, 2017 12:45 PM
>> > To: Moore, Robert
On Mon, Apr 17, 2017 at 11:03 PM, Guenter Roeck wrote:
> On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>>
>>
>> > -Original Message-
>> > From: Guenter Roeck [mailto:li...@roeck-us.net]
>> > Sent: Monday, April 17, 2017 12:45 PM
>> > To: Moore, Robert
>> > Cc: Zheng, Lv
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.timers
head: c0b7a5dbb870d1660aa5e566c5ce9972290a2bed
commit: 6a3164fa4cd35a587b5bb2e4bd86b75900af8286 [8/10] timer: Implement the
hierarchical pull model
config: i386-randconfig-r0-201716 (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.timers
head: c0b7a5dbb870d1660aa5e566c5ce9972290a2bed
commit: 6a3164fa4cd35a587b5bb2e4bd86b75900af8286 [8/10] timer: Implement the
hierarchical pull model
config: i386-randconfig-r0-201716 (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.timers
head: c0b7a5dbb870d1660aa5e566c5ce9972290a2bed
commit: 6a3164fa4cd35a587b5bb2e4bd86b75900af8286 [8/10] timer: Implement the
hierarchical pull model
config: x86_64-randconfig-x012-201716 (attached as .config)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.timers
head: c0b7a5dbb870d1660aa5e566c5ce9972290a2bed
commit: 6a3164fa4cd35a587b5bb2e4bd86b75900af8286 [8/10] timer: Implement the
hierarchical pull model
config: x86_64-randconfig-x012-201716 (attached as .config)
On Mon, 2017-04-17 at 10:52 -0600, Logan Gunthorpe wrote:
>
> On 17/04/17 01:20 AM, Benjamin Herrenschmidt wrote:
> > But is it ? For example take a GPU, does it, in your scheme, need an
> > additional "p2pmem" child ? Why can't the GPU driver just use some
> > helper to instantiate the necessary
On Mon, 2017-04-17 at 10:52 -0600, Logan Gunthorpe wrote:
>
> On 17/04/17 01:20 AM, Benjamin Herrenschmidt wrote:
> > But is it ? For example take a GPU, does it, in your scheme, need an
> > additional "p2pmem" child ? Why can't the GPU driver just use some
> > helper to instantiate the necessary
On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>
>
> > -Original Message-
> > From: Guenter Roeck [mailto:li...@roeck-us.net]
> > Sent: Monday, April 17, 2017 12:45 PM
> > To: Moore, Robert
> > Cc: Zheng, Lv ; Wysocki, Rafael J
On Mon, Apr 17, 2017 at 08:40:38PM +, Moore, Robert wrote:
>
>
> > -Original Message-
> > From: Guenter Roeck [mailto:li...@roeck-us.net]
> > Sent: Monday, April 17, 2017 12:45 PM
> > To: Moore, Robert
> > Cc: Zheng, Lv ; Wysocki, Rafael J
> > ; 'Len Brown' ; 'linux-
> >
Hi Joe,
[auto build test ERROR on v4.9-rc8]
[also build test ERROR on next-20170413]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Joe,
[auto build test ERROR on v4.9-rc8]
[also build test ERROR on next-20170413]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
cfg80211_chandef_create() expects an 'enum nl80211_channel_type' as
channel type however in ieee80211_sta_join_ibss()
NL80211_CHAN_WIDTH_20_NOHT is passed in two occasions, which is of
the enum type 'nl80211_chan_width'. Change the value to NL80211_CHAN_NO_HT
(20 MHz, non-HT channel) of the
cfg80211_chandef_create() expects an 'enum nl80211_channel_type' as
channel type however in ieee80211_sta_join_ibss()
NL80211_CHAN_WIDTH_20_NOHT is passed in two occasions, which is of
the enum type 'nl80211_chan_width'. Change the value to NL80211_CHAN_NO_HT
(20 MHz, non-HT channel) of the
With CONFIG_RT_GROUP_SCHED defined, do_sched_rt_period_timer() sequentially
takes each cpu's rq->lock. On a large, busy system, the cumulative time it
takes to acquire each lock can be excessive, even triggering a watchdog
timeout.
If rt_rq_rt_time and rt_rq->rt_nr_running are both zero, this
With CONFIG_RT_GROUP_SCHED defined, do_sched_rt_period_timer() sequentially
takes each cpu's rq->lock. On a large, busy system, the cumulative time it
takes to acquire each lock can be excessive, even triggering a watchdog
timeout.
If rt_rq_rt_time and rt_rq->rt_nr_running are both zero, this
From: Markus Elfring
Date: Mon, 17 Apr 2017 22:42:40 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "devm_kmalloc_array".
This issue
From: Markus Elfring
Date: Mon, 17 Apr 2017 22:42:40 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "devm_kmalloc_array".
This issue was detected by using the
Work for Congestion State Notifications (CSCN) and Message Ring (MR)
handling is handled via the workqueue mechanism. This requires the
driver to disable those IRQs before scheduling the work and re-enabling
it once the work is completed so that the interrupt doesn't continually
fire.
Work for Congestion State Notifications (CSCN) and Message Ring (MR)
handling is handled via the workqueue mechanism. This requires the
driver to disable those IRQs before scheduling the work and re-enabling
it once the work is completed so that the interrupt doesn't continually
fire.
The attribute declaration is typically before the definition. Move
the __maybe_unused attribute declaration before the struct keyword.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Move __maybe_unused after the complete type
drivers/net/ethernet/cirrus/cs89x0.c | 2 +-
1
The attribute declaration is typically before the definition. Move
the __maybe_unused attribute declaration before the struct keyword.
Signed-off-by: Stefan Agner
---
Changes in v2:
- Move __maybe_unused after the complete type
drivers/net/ethernet/cirrus/cs89x0.c | 2 +-
1 file changed, 1
From: Stefan Agner
Date: Mon, 17 Apr 2017 13:31:28 -0700
> Given that, can you reconsider?
Please put the attribute after the compete type.
Thanks.
From: Stefan Agner
Date: Mon, 17 Apr 2017 13:31:28 -0700
> Given that, can you reconsider?
Please put the attribute after the compete type.
Thanks.
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Monday, April 17, 2017 12:45 PM
> To: Moore, Robert
> Cc: Zheng, Lv ; Wysocki, Rafael J
> ; 'Len Brown' ; 'linux-
>
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Monday, April 17, 2017 12:45 PM
> To: Moore, Robert
> Cc: Zheng, Lv ; Wysocki, Rafael J
> ; 'Len Brown' ; 'linux-
> a...@vger.kernel.org' ; 'de...@acpica.org'
> ; 'linux-kernel@vger.kernel.org'
El Mon, Apr 03, 2017 at 12:54:58PM -0700 Matthias Kaehlcke ha dit:
> Signed-off-by: Matthias Kaehlcke
> ---
> arch/x86/um/shared/sysdep/kernel-offsets.h | 9 +
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git
El Mon, Apr 03, 2017 at 12:54:58PM -0700 Matthias Kaehlcke ha dit:
> Signed-off-by: Matthias Kaehlcke
> ---
> arch/x86/um/shared/sysdep/kernel-offsets.h | 9 +
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/arch/x86/um/shared/sysdep/kernel-offsets.h
>
This adds support for watchdog part of Fintek F71868 Super I/O chip to
f71808e_wdt driver.
The F71868 chip is, in general, very similar to a F71869, however it has
slightly different set of available reset pulse widths.
Tested on MSI A55M-P33 motherboard.
Signed-off-by: Maciej S. Szmigiero
This adds support for watchdog part of Fintek F71868 Super I/O chip to
f71808e_wdt driver.
The F71868 chip is, in general, very similar to a F71869, however it has
slightly different set of available reset pulse widths.
Tested on MSI A55M-P33 motherboard.
Signed-off-by: Maciej S. Szmigiero
---
El Mon, Apr 03, 2017 at 12:46:36PM -0700 Matthias Kaehlcke ha dit:
> Avoid code duplication by using OFFSET() in DEF_*REG() instead of
> replicating the macro.
>
> Signed-off-by: Matthias Kaehlcke
Ping, any feedback on this patch?
Thanks
Matthias
El Mon, Apr 03, 2017 at 12:46:36PM -0700 Matthias Kaehlcke ha dit:
> Avoid code duplication by using OFFSET() in DEF_*REG() instead of
> replicating the macro.
>
> Signed-off-by: Matthias Kaehlcke
Ping, any feedback on this patch?
Thanks
Matthias
Hi!
> v4.10 works quite nicely on N900, but I still have problems with
> audio. Even GSM calls would be usable, if I had reasonable volume on
> microphone and speaker... but I don't.
>
> Both speaker and microphone are too quiet. I can get louder output by
> plugging
Hi!
> v4.10 works quite nicely on N900, but I still have problems with
> audio. Even GSM calls would be usable, if I had reasonable volume on
> microphone and speaker... but I don't.
>
> Both speaker and microphone are too quiet. I can get louder output by
> plugging
On 2017-04-17 13:09, David Miller wrote:
> From: Stefan Agner
> Date: Sun, 16 Apr 2017 23:20:32 -0700
>
>> The attribute declaration is typically before the definition. Move
>> the __maybe_unused attribute declaration before the struct keyword.
>>
>> Signed-off-by: Stefan Agner
On 2017-04-17 13:09, David Miller wrote:
> From: Stefan Agner
> Date: Sun, 16 Apr 2017 23:20:32 -0700
>
>> The attribute declaration is typically before the definition. Move
>> the __maybe_unused attribute declaration before the struct keyword.
>>
>> Signed-off-by: Stefan Agner
>
I did catch
Hi Linus,
please pull one important fix for the parisc architecture for kernel 4.11 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.11-5
One patch which fixes get_user() for 64-bit values on 32-bit kernels. Up
to now we lost the upper 32-bits of the
Hi Linus,
please pull one important fix for the parisc architecture for kernel 4.11 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.11-5
One patch which fixes get_user() for 64-bit values on 32-bit kernels. Up
to now we lost the upper 32-bits of the
On Mon, Apr 10, 2017 at 01:03:46PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> device memory hotplug hooks into regular memory hotplug only half way.
> It needs memory sections to track struct pages but there is no
> need/desire to associate those sections with memory
On Mon, Apr 10, 2017 at 01:03:46PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> device memory hotplug hooks into regular memory hotplug only half way.
> It needs memory sections to track struct pages but there is no
> need/desire to associate those sections with memory blocks and export
>
From: Stefan Agner
Date: Sun, 16 Apr 2017 23:20:32 -0700
> The attribute declaration is typically before the definition. Move
> the __maybe_unused attribute declaration before the struct keyword.
>
> Signed-off-by: Stefan Agner
Well, I see if just as often
From: Stefan Agner
Date: Sun, 16 Apr 2017 23:20:32 -0700
> The attribute declaration is typically before the definition. Move
> the __maybe_unused attribute declaration before the struct keyword.
>
> Signed-off-by: Stefan Agner
Well, I see if just as often after the variable name too:
Em 16-04-2017 07:48, Greg Kroah-Hartman escreveu:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Ricardo Leitner
[ Upstream commit 2dcab598484185dea7ec22219c76dcdd59e3cb90 ]
Hi Greg. Are you also
Em 16-04-2017 07:48, Greg Kroah-Hartman escreveu:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Ricardo Leitner
[ Upstream commit 2dcab598484185dea7ec22219c76dcdd59e3cb90 ]
Hi Greg. Are you also including dfcb9f4f99f1
301 - 400 of 1040 matches
Mail list logo