On 2017-06-27 07:47, Stephen Boyd wrote:
After commit 7f1d4e58dabb ("spmi: pmic-arb: optimize table
lookups") we always need the ppid_to_apid table regardless of the
version of pmic arbiter we have. Otherwise, we will try to deref
the array when we don't allocate it on v2 hardware like the
msm897
On Fri, Jun 23, 2017 at 04:49:23PM -0500, Rob Herring wrote:
> On Tue, Jun 20, 2017 at 02:40:57PM +0530, Varadarajan Narayanan wrote:
> > Currently the QUP Version v1 does not work with DMA so added
> > the support for the same.
> >
> > 1. It uses ADM DMA which requires TX and RX CRCI
> > 2. DMA c
Nicholas Piggin writes:
> Current busy-wait loops are implemented by repeatedly calling cpu_relax()
> to give an arch option for a low-latency option to improve power and/or
> SMT resource contention.
>
> This poses some difficulties for powerpc, which has SMT priority setting
> instructions (pri
In case of error at init time, rollback iomapping and kfree.
Signed-off-by: Arvind Yadav
---
drivers/clocksource/timer-imx-gpt.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/clocksource/timer-imx-gpt.c
b/drivers/clocksource/timer-imx-gpt.c
ind
Hi Kees,
Today's linux-next merge of the kspp tree got a conflict in:
include/linux/fs.h
between commit:
c75b1d9421f8 ("fs: add fcntl() interface for setting/getting write life time
hints")
from the block tree and commit:
3abc2b3fcf5c ("randstruct: Mark various structs for randomizatio
__list_lru_walk_one() acquires nlru spin lock (nlru->lock) for
longer duration if there are more number of items in the lru list.
As per the current code, it can hold the spin lock for upto maximum
UINT_MAX entries at a time. So if there are more number of items in
the lru list, then "BUG: spinlock
list_lru_count_node() iterates over all memcgs to get
the total number of entries on the node but it can race with
memcg_drain_all_list_lrus(), which migrates the entries from
a dead cgroup to another. This can return incorrect number of
entries from list_lru_count_node().
Fix this by keeping trac
Hi all,
[Yes, top posted :-)]
With the merge window approaching, this is just a reminder that this
merge problem still exists. I assume that the sunxi tree will be
merged into the arm-soc tree before going to Linus.
On Sat, 10 Jun 2017 09:29:44 +1000 Stephen Rothwell
wrote:
>
> On Fri, 9 Jun
Hi Andrew,
[Yes, top posting :-)]
With the merge window approaching, just a reminder that this conflict
still exists.
On Thu, 8 Jun 2017 16:28:12 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/random.h
>
> between co
On Wed, Jun 28, 2017 at 7:35 AM, Frans Klaver wrote:
> On Wed, Jun 28, 2017 at 1:03 AM, Gustavo A. R. Silva
> wrote:
>>
>> Hello everybody,
>>
>> While looking into Coverity ID 1371643 I ran into the following piece of
>> code at kernel/sched/cputime.c:568:
>>
>> 568/*
>> 569 * Adjust tick based
Hi all,
On Fri, 9 Jun 2017 14:28:56 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kvms390 tree got a conflict in:
>
> arch/s390/include/asm/kvm_host.h
>
> between commit:
>
> 2387149eade2 ("KVM: improve arch vcpu request defining")
>
> from the kvm-arm tree and commit
Hi Martin,
After merging the scsi-mkp tree, today's linux-next build
(powerpc_ppc64_defconfig) produced these warnings:
In file included from include/linux/byteorder/big_endian.h:4:0,
from arch/powerpc/include/uapi/asm/byteorder.h:13,
from include/asm-generic/bit
In case of error at init time, rollback iomapping.
Signed-off-by: Arvind Yadav
---
drivers/clocksource/timer-ti-32k.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/timer-ti-32k.c
b/drivers/clocksource/timer-ti-32k.c
index 6240677..658d759 100644
--- a/drivers/clocksour
Hi,
On 2017/6/28 9:49, kbuild test robot wrote:
> Hi Shaokun,
>
> [auto build test ERROR on next-20170619]
> [also build test ERROR on v4.12-rc7]
> [cannot apply to linus/master linux/master arm64/for-next/core v4.12-rc6
> v4.12-rc5 v4.12-rc4]
> [if your patch is applied to the wrong git tree, p
Hi Tejun,
After merging the libata tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/ata/libata-scsi.c: In function 'ata_scsi_var_len_cdb_xlat':
drivers/ata/libata-scsi.c:4194:1: warning: label 'unspprt_sa' defined but not
used [-Wunused-label]
unspprt_sa:
On Tue, 27 Jun 2017, Kees Cook wrote:
> On Mon, Jun 26, 2017 at 8:33 PM, James Morris wrote:
> > On Mon, 26 Jun 2017, Kees Cook wrote:
> >
> >> >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using
> >> >> labels")
> >> >> Signed-off-by: Stephen Rothwell
> >> > Acked-by: John Joh
Hi all,
On Wed, 28 Jun 2017 15:40:59 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the target-updates tree got a conflict in:
>
> drivers/scsi/qla2xxx/qla_target.c
>
> between commits:
>
> f775bd14e44d ("scsi: qla2xxx: Convert 32-bit LUN usage to 64-bit")
> 82de802ad46e
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1496 592 02088 828 drivers/gpu/d
On Fri, Jun 23, 2017 at 10:01:46AM +0300, Amir Goldstein wrote:
> On Thu, Jun 22, 2017 at 9:59 PM, Stefan Berger
> wrote:
> > This series of patches primary goal is to enable file capabilities
> > in user namespaces without affecting the file capabilities that are
> > effective on the host. This i
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in:
drivers/scsi/qla2xxx/qla_target.c
between commits:
f775bd14e44d ("scsi: qla2xxx: Convert 32-bit LUN usage to 64-bit")
82de802ad46e ("scsi: qla2xxx: Preparation for Target MQ.")
from the scsi tree and comm
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1531 592 02123 84b drivers/gpu/d
> Il giorno 27 giu 2017, alle ore 20:29, Jens Axboe ha
> scritto:
>
> On 06/27/2017 12:27 PM, Paolo Valente wrote:
>>
>>> Il giorno 27 giu 2017, alle ore 16:41, Jens Axboe ha
>>> scritto:
>>>
>>> On 06/27/2017 12:09 AM, Paolo Valente wrote:
> Il giorno 19 giu 2017, alle ore 13:43,
Hi,
On Tue, Jun 27, 2017 at 9:38 PM, Jeffy Chen wrote:
> The rockchip spi still requires slave selection when using GPIO CS.
>
> Signed-off-by: Jeffy Chen
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> drivers/spi/spi-rockchip.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/
Hi Kyle,
I understand your requirement. Sorry I don't know the detail of rr
debugger, but I guess if it just uses counter overflow to deliver a
signal, could it set the counter without "exclude_kernel"?
Another consideration is, I'm not sure if the kernel can accurately
realize that if the i
On Wed, Jun 28, 2017 at 1:03 AM, Gustavo A. R. Silva
wrote:
>
> Hello everybody,
>
> While looking into Coverity ID 1371643 I ran into the following piece of
> code at kernel/sched/cputime.c:568:
>
> 568/*
> 569 * Adjust tick based cputime random precision against scheduler runtime
> 570 * account
On Tue, Jun 27, 2017 at 10:51 PM, Jeff Kirsher
wrote:
> This was submitted and accepted into David Miller's net-next tree. I can
> see if Dave can pull it into his net tree. DOes stable need to pick this
> up as well?
Nah if it landed somewhere at least I'm happy, we can carry the fixup
for a w
Jeffy,
On Tue, Jun 27, 2017 at 9:38 PM, Jeffy Chen wrote:
> The rockchip spi would stop driving pins when runtime suspended, which
> might break slave's xfer(for example cros_ec).
>
> Since we have pullups on those pins, we only need to care about this
> when the CS asserted.
>
> So let's keep th
> Please don't top post.
Sorry about that.
> Which function needs 1KB of stack space? That's quite a lot.
FSE_buildCTable_wksp(), FSE_compress_wksp(), and HUF_readDTableX4()
required over 1 KB of stack space.
> I can see in [1] that there are some on-stack buffers replaced by
> pointers to the
Hi,
On 28 June 2017 at 10:44, kbuild test robot wrote:
> Hi Baolin,
>
> [auto build test ERROR on balbi-usb/next]
> [also build test ERROR on next-20170627]
> [cannot apply to v4.12-rc7]
> [if your patch is applied to the wrong git tree, please drop us a note to
> he
I'm afraid I accidentally introduced a regression into v4 of this patch.
Ondrej, please test the patch below instead. Sorry for the inconvenience.
diff --git a/drivers/scsi/g_NCR5380.c b/drivers/scsi/g_NCR5380.c
index b1e0a08e49c1..98d5360b0c78 100644
--- a/drivers/scsi/g_NCR5380.c
+++ b/drivers/s
On Tue, 2017-06-27 at 22:30 +0200, Kamil Debski wrote:
> Hi,
>
> Please find my comments inline.
>
> On 19 June 2017 at 07:10, Smitha T Murthy wrote:
> > Aligning the luma_dpb_size, chroma_dpb_size, mv_size and me_buffer_size
> > for MFCv10.10.
> >
> > Signed-off-by: Smitha T Murthy
> > Reviewe
The last 'dev_dbg' call uses 'hr_qp->qpn'. However, 'hr_qp' may have been
freed a few lines above.
In order to fix it, take the value of 'hr_qp->qpn' earlier in the function
and use it instead.
Fixes: d838c481e025 ("IB/hns: Fix the bug when destroy qp")
Signed-off-by: Christophe JAILLET
---
dri
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1531 592 02123 84b drivers/gpu/d
On Wed, Jun 28, 2017 at 09:54:32AM +0800, Orson Zhai wrote:
> We found the device is "fm". We highly suspect that fm driver call
> misc_register twice and reinitialize list to make ->pre & ->next
> pointing to himself.
>
> Meanwhile, we checked fm driver and found nothing obviously wrong in the co
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1496 592 02088 828 drivers/gpu/d
merged into cifs-2.6.git for-next
On Tue, Jun 27, 2017 at 10:06 AM, Arnd Bergmann wrote:
> Some functions are only referenced under an #ifdef, causing a harmless
> warning:
>
> fs/cifs/smb2ops.c:1374:1: error: 'get_smb2_acl' defined but not used
> [-Werror=unused-function]
>
> We could mark them
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 6 +++---
1 file changed, 3 insertions(+), 3 de
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
Changes in v4:
Change log was missing.
Changes in v3:
Change log correction. Added change log below '---'.
Changes in v2:
Remove useless initialization
On Tue, Jun 27, 2017 at 7:09 PM, Jin, Yao wrote:
> Hi,
>
> In theory, the PMI interrupts in skid region should be dropped, right?
No, why would they be dropped?
My understanding of the situation is as follows:
There is some time, call it t_0, where the hardware counter overflows.
The PMU trigge
> > > > This is 4.12.0-rc5-00137-ga090bd4ff838 on a dual AthlonMP server tha
> > > > has
> > > > been running fine until 4.11.0 included. 4.12.0-rc5-00137-ga090bd4ff838
> > > > was the first kernel after 4.11 that I tried and the problem happened
> > > > while compiling next kernel from git.
>
This patch partially reverts 3df0e50 ("xen/blkfront: pseudo support for
multi hardware queues/rings"). The xen-blkfront queue/ring might hang due
to grants allocation failure in the situation when gnttab_free_head is
almost empty while many persistent grants are reserved for this queue/ring.
As pe
On Thu, Jun 22, 2017 at 3:14 AM, Arvind Yadav wrote:
> File size before:
>textdata bss dec hex filename
> 207921580 994 233665b46 drivers/acpi/nfit/core.o
>
> File size After adding 'const':
>textdata bss dec hex filename
> 209681388
Hi doug,
thanx for your comments.
On 06/28/2017 03:27 AM, Doug Anderson wrote:
Hi,
On Mon, Jun 26, 2017 at 7:20 PM, Jeffy Chen wrote:
The rockchip spi would stop driving pins when runtime suspended, which
might break slave's xfer(for example cros_ec).
Since we have pullups on those pins, we
The rockchip spi still requires slave selection when using GPIO CS.
Signed-off-by: Jeffy Chen
---
Changes in v3: None
Changes in v2: None
drivers/spi/spi-rockchip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index bab9b13..52ea16
The rockchip spi would stop driving pins when runtime suspended, which
might break slave's xfer(for example cros_ec).
Since we have pullups on those pins, we only need to care about this
when the CS asserted.
So let's keep the spi alive when chip select is asserted.
Also use pm_runtime_put inste
On Wed, 28 Jun 2017 06:46:49 +0530
Akshay Adiga wrote:
> pnv_wakeup_noloss expects R12 to contain SRR1 value to determine if
> the wakeup reason is an HMI in CHECK_HMI_INTERRUPT.
>
> When we wakeup with ESL=0, SRR1 will not contain the wakeup reason, so
> there is no point setting R12 to SRR1.
>
Hi, Ingo
Thank you for the comment.
On 2017/6/22 0:40, Ingo Molnar wrote:
> * zhong jiang wrote:
>
>> when shift expoment is negative, left shift alway zero. therefore, we
>> modify the logic to avoid the warining.
>>
>> Signed-off-by: zhong jiang
>> ---
>> arch/x86/include/asm/futex.h | 8 +++
On Tue, Jun 27, 2017 at 4:16 PM, Shuah Khan wrote:
> On 06/27/2017 09:16 AM, Greg KH wrote:
>> On Tue, Jun 27, 2017 at 05:13:59PM +0200, Greg KH wrote:
>>> On Tue, Jun 27, 2017 at 02:10:32PM +0530, Naresh Kamboju wrote:
selftest capabilities test failed on linux mainline and linux-next and
>>
> On Sat, Jun 24, 2017 at 02:25:46AM +0200, Rafael Wysocki wrote:
> > On Wednesday, June 21, 2017 11:15:43 AM Darren Hart wrote:
> > > On Fri, Jun 16, 2017 at 06:40:52AM +0200, Michał Kępień wrote:
> > > > All ACPI device notify callbacks are invoked using acpi_os_execute(),
> > > > which causes th
Hi jeffy,
On Wed, 28 Jun 2017 12:00:19 +0800 jeffy wrote:
>
> commit 50816c48997af857d4bab3dca1aba90339705e96
> Author: Ingo Molnar
> Date: Sun Mar 5 10:33:16 2017 +0100
>
> sched/wait: Standardize internal naming of wait-queue entries
>
>
> changed wait_queue_entry_t to struct wait_qu
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
drivers/xen/events/events_base.c
between commit:
ef1c2cc88531 ("xen/events: Add support for effective affinity mask")
from the tip tree and commit:
c48f64ab4723 ("xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to nex
[add linux-xfs to cc]
FYI this is a discussion of the patch "xfs: map KM_MAYFAIL to
__GFP_RETRY_MAYFAIL" which was last discussed on the xfs list in March
and now is in the -mm tree...
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-2
On 27-06-17, 18:08, Rafael J. Wysocki wrote:
> On Tue, Jun 27, 2017 at 6:20 AM, Viresh Kumar wrote:
> > @Rafael: Will it be fine to lower down the value of LATENCY_MULTIPLIER?
>
> We can do that, but then I think we need to compensate for the change
> in the old governors code or there may be sur
On Tue, 27 Jun 2017, Ondrej Zary wrote:
> On Tuesday 27 June 2017 14:42:29 Finn Thain wrote:
>
> > > ... it triggers sometimes: the value is 1 instead of 0. As we use
> > > only 16-bit writes, I don't see how the value could ever be odd.
> > > Looks like a bug in the chip. The index register co
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность Ваше
On Tue, 27 Jun 2017, Ondrej Zary wrote:
> On Tuesday 27 June 2017 03:49:16 Finn Thain wrote:
> >
> > ... As long as there's no gated IRQ, we poll for buffer readiness
> > until timeout. And when there is a gated IRQ, we break both the
> > polling loop and the transfer loop immediately. Your code
From: Ondrej Zary
When an IRQ arrives during PDMA transfer, pread() and pwrite() return
without waiting for the 53C80 registers to be ready and this ends up
messing up the chip state. This was observed with SONY CDU-55S which is
slow enough to disconnect during 4096-byte reads.
IRQ during PDMA i
From: Ondrej Zary
The corruption is always the same: one byte missing at the beginning of
a 128 B block. It happens only with slow Quantum LPS 240 drive, not with
faster IBM DORS-32160. It's not clear what causes this. Documentation
for the DTC436 chip has not been made available. Hence this work
From: Ondrej Zary
The polling loops in pread() and pwrite() can easily become infinite
loops and hang the machine.
On DTC chips, IRQ can arrive late and we miss it because we only check
once. Merge the IRQ check into host buffer wait and add polling limit.
Also place a limit on polling for 53C8
From: Ondrej Zary
generic_NCR5380_dma_xfer_len() incorrectly uses cmd->transfersize
which causes rescan-scsi-bus and CD-ROM access to hang the system.
Use cmd->SCp.this_residual instead, like other NCR5380 drivers.
Signed-off-by: Ondrej Zary
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR538
Ondrej, would you please test this new series?
Changed since v1:
- PDMA transfer residual is calculated earlier.
- End of DMA flag check is now polled (if there is any residual).
Changed since v2:
- Bail out of transfer loops when Gated IRQ gets asserted.
- Make udelay conditional on board type.
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.c | 61 ++--
1 file changed, 28 insertions(+), 33 deletions(-)
diff --git a/drivers/scsi/g_NCR5380.c b/drivers/scsi/g_NCR5380.c
index 911a4300ea51..9f18082415c4 100644
--- a/drivers/scsi/g_NCR5380.c
On Wed, Jun 28, 2017 at 11:40:30AM +0800, Jason Wang wrote:
>
>
> On 2017年06月28日 11:31, Michael S. Tsirkin wrote:
> > On Wed, Jun 28, 2017 at 10:45:18AM +0800, Jason Wang wrote:
> > > On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrot
Hi Stephen,
On 06/28/2017 11:43 AM, Stephen Rothwell wrote:
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
net/bluetooth/hidp/core.c:1241:39: error: unknown type name 'wait_queue_t'
static int hidp_session_wake_function(wait_queue_t *wait
After onlining a memory_block and then offline it, the valid_zones will not
come back to the original state.
For example:
$cat memory4?/valid_zones
Movable Normal
Movable Normal
Movable Normal
$echo online > memory40/state
$cat memory4?/valid_zones
Movable
Movable
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
net/bluetooth/hidp/core.c:1241:39: error: unknown type name 'wait_queue_t'
static int hidp_session_wake_function(wait_queue_t *wait,
^
In file included from
On 2017年06月28日 11:31, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 10:45:18AM +0800, Jason Wang wrote:
On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 09:
On Wed, Jun 28, 2017 at 10:45:18AM +0800, Jason Wang wrote:
>
>
> On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
> > On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
> > >
> > > On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wa
Additionally,
the code is available on 'annotate/src-only' branch at
git://github.com/taeung/linux-perf.git
Thanks,
Taeung
On 06/28/2017 12:18 PM, Taeung Song wrote:
Hi,
The --source-only option and new source code TUI view can show
the result of performance analysis based on full source co
Hi all,
Today's linux-next merge of the tip tree got conflicts in:
net/bluetooth/bnep/core.c
net/bluetooth/cmtp/core.c
net/bluetooth/hidp/core.c
between commits:
25717382c1dd ("Bluetooth: bnep: fix possible might sleep error in
bnep_session")
f06d977309d0 ("Bluetooth: cmtp: fix possi
PERHATIAN
Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak
Hi,
The --source-only option and new source code TUI view can show
the result of performance analysis based on full source code per
symbol(function).
(Namhyung Kim told me this idea and it was also requested by others some time
ago..)
If someone wants to see the cause, he/she will need to dig i
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
kernel/irq/affinity.c
between commit:
6f9a22bc5775 ("PCI/MSI: Ignore affinity if pre/post vector count is more than
min_vecs")
from the pci tree and commit:
9a0ef98e186d ("genirq/affinity: Assign vectors to all present
The option can show the result of performance analysis
based on full source code per symbol(function).
This view can be a precheck before assembly code level
and be the additional useful view point.
For example, if target symbol is 'hex2u64' of util/util.c,
the output is like below.
$ perf an
Unlike asm code level, the new source code view
provides a additional viewpoint based on source code level
for performance analysis.
Of course, current disassembly view can show itself with pieces of source code
but some users want to check the result of performance analysis
based on full source c
Cc: Namhyung Kim
Cc: Jiri Olsa
Signed-off-by: Taeung Song
---
tools/perf/ui/browsers/annotate.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/tools/perf/ui/browsers/annotate.c
b/tools/perf/ui/browsers/annotate.c
index 200ee0c..bb5a933 100644
--- a/tools/
Suggested-by: Namhyung Kim
Cc: Milian Wolff
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Adrian Hunter
Cc: Wang Nan
Cc: Jin Yao
Cc: Andi Kleen
Cc: Kim Phillips
Cc: David Ahern
Signed-off-by: Taeung Song
---
tools/perf/ui/browser.h | 1 +
tools/perf/ui/browsers/annotate.c | 146 +++
Hi Eddie,
>> Those child nodes represent the downstream i2c buses, and so also
>> contain the i2c slave devices, right? If so, you may want to document
>> that, and/or add a simple device to that example (say, an EEPROM).
>
> Yes, good point, but the driver currently wouldn't do anything with tha
Replace the literal function name "visorbus_create_instance" with the format
specifier "%s" so it can be dynamically filled by the __func__ macro.
Signed-off-by: Quytelda Kahja
---
drivers/staging/unisys/visorbus/visorbus_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Hi Baolin,
[auto build test ERROR on balbi-usb/next]
[also build test ERROR on next-20170627]
[cannot apply to v4.12-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Baolin-Wang/include-uapi
On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
We should allow csumed packet for small buffer, otherwise XDP_PASS
won't wo
gah, forgot to amend the trailing tab change in.
Do you mind just fixing it up when you merge or shall I send v3?
On 06/26/2017 05:57 PM, Doug Berger wrote:
> The fixmap pages need to be on the same pmd page for the current
> implementation of arm early_fixmap. A build time bug check is
> used to ensure that. However, the worst case fixmap range is
> better represented by __end_of_fixed_addresses than by the
The macro insn_fetch marks the 'type' argument as having a specified
alignment. Type attributes can only be applied to structs, unions, or
enums, but insn_fetch is only ever invoked with integral types, so Clang
produces 19 -Wignored-attributes warnings for this source file.
Signed-off-by: Nick D
> -Original Message-
> From: Quytelda Kahja [mailto:quyte...@tamalin.org]
> Sent: Tuesday, June 27, 2017 5:18 PM
> To: Kershner, David A ;
> gre...@linuxfoundation.org
> Cc: de...@driverdev.osuosl.org; linux-kernel@vger.kernel.org; Quytelda
> Kahja
> Subject: [PATCH] Replace the literal
drivers/pci/host/pci-versatile.c: In function 'versatile_pci_probe':
drivers/pci/host/pci-versatile.c:131:38: error: 'dev' undeclared
bridge = devm_pci_alloc_host_bridge(dev, 0);
Was this code ever compiled, much less tested ?
Guenter
On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
>
>
> On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
> > On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
> > > We should allow csumed packet for small buffer, otherwise XDP_PASS
> > > won't work correctly.
> > >
> > > Fixes
On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
We should allow csumed packet for small buffer, otherwise XDP_PASS
won't work correctly.
Fixes commit bb91accf2733 ("virtio-net: XDP support for small buffers")
Signed-off-by: Jason Wan
Hi,
In theory, the PMI interrupts in skid region should be dropped, right?
For a userspace debugger, is it the only choice that relies on the
*skid* PMI interrupt?
Thanks
Jin Yao
On 6/28/2017 9:01 AM, Kyle Huey wrote:
Sent again with LKML CCd, sorry for the noise.
- Kyle
On Tue, Jun 27, 2
On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
> We should allow csumed packet for small buffer, otherwise XDP_PASS
> won't work correctly.
>
> Fixes commit bb91accf2733 ("virtio-net: XDP support for small buffers")
> Signed-off-by: Jason Wang
The issue would be VIRTIO_NET_HDR_F_DAT
On 06/27/2017 07:57 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> Today's linux-next merge of the block tree got a conflict in:
>
> include/linux/fs.h
>
> between commit:
>
> 3f64df8a51ce ("fs: new infrastructure for writeback error handling and
> reporting")
>
> from the file-locks tree and
On Wed, Jun 28, 2017 at 09:51:03AM +0800, Jason Wang wrote:
> We don't hold any tx lock when trying to disable TX during reset, this
> would lead a use after free since ndo_start_xmit() tries to access
> the virtqueue which has already been freed. Fix this by using
> netif_tx_disable() before freei
Hi Greg & Arnd,
On Tue, Jun 27, 2017 at 08:29:17AM +0200, Greg Kroah-Hartman wrote:
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I inclu
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
include/linux/fs.h
between commit:
3f64df8a51ce ("fs: new infrastructure for writeback error handling and
reporting")
from the file-locks tree and commit:
c75b1d9421f8 ("fs: add fcntl() interface for setting/getting
We should allow csumed packet for small buffer, otherwise XDP_PASS
won't work correctly.
Fixes commit bb91accf2733 ("virtio-net: XDP support for small buffers")
Signed-off-by: Jason Wang
---
The patch is needed for -stable.
---
drivers/net/virtio_net.c | 2 +-
1 file changed, 1 insertion(+), 1 d
Hi Shaokun,
[auto build test ERROR on next-20170619]
[also build test ERROR on v4.12-rc7]
[cannot apply to linus/master linux/master arm64/for-next/core v4.12-rc6
v4.12-rc5 v4.12-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
htt
We don't hold any tx lock when trying to disable TX during reset, this
would lead a use after free since ndo_start_xmit() tries to access
the virtqueue which has already been freed. Fix this by using
netif_tx_disable() before freeing the vqs, this could make sure no tx
after vq freeing.
Reported-b
Ram Pai writes:
> Display the pkey number associated with the vma in smaps of a task.
> The key will be seen as below:
>
> VmFlags: rd wr mr mw me dw ac key=0
Why wouldn't we just emit a "ProtectionKey:" line like x86 does?
See their arch_show_smap().
You should probably also do what x86 does,
Johan,
> Make sure to drop the reference to the dma device taken by
> of_find_device_by_node() on probe errors and on driver unbind.
Looks good to me.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Hi Martin,
On 6/27/17, 6:32 PM, "Martin K. Petersen" wrote:
> In qla2xx_start_scsi_mq() and qla2xx_dif_start_scsi_mq() we grab the
> qpair->qp_lock but do access members of the qpair before having the lock.
> Re-order the locking sequence to have all read and write access to qpa
1 - 100 of 1195 matches
Mail list logo
