On Thu, Oct 22, 2015 at 11:05:26AM -0400, Murali Karicheri wrote:
> On 10/21/2015 08:56 AM, WingMan Kwok wrote:
> >On TI's Keystone platforms, several peripherals such as the
> >gbe ethernet switch, 10gbe ethernet switch and PCIe controller
> >require the use of a SerDes for converting SoC
We've been testing out restartable sequences + malloc changes for use
at Facebook. Below are some test results, as well as some possible
changes based on Paul Turner's original patches
https://lkml.org/lkml/2015/6/24/665
I ran one service with several permutations of various mallocs. The
Introduce the notion of 'restartable sequence'. This is a user-defined range
within which we guarantee user-execution will occur serially with respect
to scheduling events such as migration or competition with other threads.
Preemption, or other interruption within this region, results in
Em Thu, Oct 22, 2015 at 03:28:49PM +0900, Namhyung Kim escreveu:
> Currently 'perf top --call-graph' option is same as 'perf record'. But
> 'perf top' also need to receive display options in 'perf report'. To do
> that, change parse_callchain_report_opt() to allow record options too.
>
> Now
Em Thu, Oct 22, 2015 at 11:28:32PM +0900, Namhyung Kim escreveu:
> The --call-graph option is complex so we should provide better guide for
> users. Also change help message to be consistent with config option
> names. Now perf top will show help like below:
>
> $ perf top --call-graph
>
On Thu, Oct 22, 2015 at 12:21:33AM -0400, Johannes Weiner wrote:
...
> @@ -5500,13 +5524,38 @@ void sock_release_memcg(struct sock *sk)
> */
> bool mem_cgroup_charge_skmem(struct mem_cgroup *memcg, unsigned int nr_pages)
> {
> + unsigned int batch = max(CHARGE_BATCH, nr_pages);
>
Remove black line suggested by Sergei
This patch is to the ath5k/eeprom.c that fixes up warning caught by
coccicheck:
Unneeded variable: "ret". Return "0" on line 980
Remove unneeded variable ret created to return zero.
Signed-off-by: Punit Vara
---
On Mon, Oct 19, 2015 at 06:14:29PM +0100, Luis de Bethencourt wrote:
> Boolean tests do not need explicit comparison to true or false.
>
> Signed-off-by: Luis de Bethencourt
> ---
> diff --git a/drivers/staging/rtl8712/usb_ops_linux.c
>
Hello,
I did some more investigations, (wireshark)
The unlink of /tmp/crontab.vYPoHR/crontab is tranlated into a rename nfs call ?
(.nfs file)
NFS 670 V3 READDIRPLUS Reply (Call In 731) crontab .. .
NFS 210 V3 LOOKUP Call (Reply In 734), DH:
Daniel Borkmann writes:
> On 10/20/2015 08:56 PM, Eric W. Biederman wrote:
> ...
>> Just FYI: Using a device for this kind of interface is pretty
>> much a non-starter as that quickly gets you into situations where
>> things do not work in containers. If someone gets a
On Wed, 21 Oct 2015 18:20:27 +0200
Jens Kuske wrote:
> The Allwinner H3 is a home entertainment system oriented SoC with
> four Cortex-A7 cores and a Mali-400MP2 GPU.
>
> Signed-off-by: Jens Kuske
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 499
>
Hi Linus
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media media/v4.3-4
For some regression fixes and potential security issues:
- netup_unidvb: fix potential crash when spi is NULL
- rtl28xxu: fix control message flaws
- m88ds3103: fix
On Fri, 16 Oct 2015, Moritz Fischer wrote:
Hi Moritz,
I just noticed a problem regarding private data. Fortunately
it is easy to fix. See below...
> +static int zynq_fpga_probe(struct platform_device *pdev)
> +{
> + struct device *dev = >dev;
> + struct zynq_fpga_priv *priv;
> +
Similar to enable_event/disable_event triggers, these triggers enable
and disable the aggregation of events into maps rather than enabling
and disabling their writing into the trace buffer.
They can be used to automatically start and stop hist triggers based
on a matching filter condition.
If
Allow users to define any number of hist triggers per trace event.
Any number of hist triggers may be added for a given event, which may
differ by key, value, or filter.
Reading the event's 'hist' file will display the output of all the
hist triggers defined on an event concatenated in the order
This patch is to the ath5k/eeprom.c that fixes up warning caught by
coccicheck:
-Unneeded variable: "ret". Return "0" on line 1733
Remove unneccesary variable ret created to return zero.
Signed-off-by: Punit Vara
---
drivers/net/wireless/ath/ath5k/eeprom.c | 5 ++---
1
Allow users to have address fields displayed as symbols in the output
by appending '.sym' or 'sym-offset' to field names:
# echo hist:keys=aaa.sym,bbb.sym-offset ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by: Masami
Add documentation and usage examples for 'hist' triggers.
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
---
Documentation/trace/events.txt | 1135
1 file changed, 1135 insertions(+)
Allow users to define 'named' hist triggers. All triggers created
with the same 'name=xxx' option will update the same shared histogram
data.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx ... [ if filter] > event/trigger
to this:
# echo hist:name=xxx:keys=xxx
From: Masami Hiramatsu
Add the hist trigger testcases for ftracetest.
This checks the basic histogram trigger behaviors like as;
- Histogram trigger itself
- Histogram with string key
- Histogram with compound keys
- Histogram with sort key
- Histogram
Allow users to specify multiple trace event fields to use in keys by
allowing multiple fields in the 'keys=' keyword. With this addition,
any unique combination of any of the fields named in the 'keys'
keyword will result in a new entry being added to the hash table.
Signed-off-by: Tom Zanussi
On 10/20/2015 02:33 AM, LABBE Corentin wrote:
Precalculated hash for empty message are now present in hash headers.
This patch just use them.
Signed-off-by: LABBE Corentin
Tested-by: Tom Lendacky
Acked-by: Tom Lendacky
If we assume the maximum size for a string field, we don't have to
worry about its position. Since we only allow two keys in a compound
key and having more than one string key in a given compound key
doesn't make much sense anyway, trading a bit of extra space instead
of introducing an arbitrary
From: Namhyung Kim
The string in a trace event is usually recorded as dynamic array which
is variable length. But current hist code only support fixed length
array so it cannot support most strings.
This patch fixes it by checking filter_type of the field and get
proper
Allow users to append 'clear' to an existing trigger in order to have
the hash table cleared.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx:vals=yyy:sort=zzz.descending:pause/cont \
[ if filter] > event/trigger
to this:
# echo
Allow users to have pid fields displayed as program names in the output
by appending '.execname' to field names:
# echo hist:keys=aaa.execname ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
It's often useful to be able to use a stacktrace as a hash key, for
keeping a count of the number of times a particular call path resulted
in a trace event, for instance. Add a special key named 'stacktrace'
which can be used as key in a 'keys=' param for this purpose:
# echo
On Mon, Oct 19, 2015 at 12:43 AM, Pramod Kumar wrote:
> This new compatible string, "brcm,iproc-gpio", should be used for
> all new iproc-based future SoCs.
Can't predict the future and crazy whims of hardware designers.
This is fine for matching, but you should also have
Hello,
Message from Saudi Arabia Prince Alwaleed bin Talal for his charity donation
and You have been selected as recipient/benefactor for $5Million Dollars from
Alwaleed Philanthropic Foundation Grant.for more information contact Via email
ppichar...@outlook.com
Thanks
Ally Mohammed
--
On 10/22/2015 11:43 AM, Rob Herring wrote:
On Mon, Oct 19, 2015 at 12:43 AM, Pramod Kumar wrote:
Add ngpios property to the gpio controller's DT node so that controller
driver extracts total number of gpio lines present in controller
from DT and removes dependency on
On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote:
>
>
> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote:
>> But that's moot currently because Greg believes that the time spent
>> probing devices at boot time could be reduced enough so that the order
>> in
Use i2c_add_driver as it will add THIS_MODULE for us.
Signed-off-by: Andrew F. Davis
---
drivers/usb/misc/usb3503.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503.c
index 64ff5b9..b45cb77 100644
---
On 19/10/15 18:47, Mark Brown wrote:
> On Mon, Oct 12, 2015 at 01:40:29PM +0100, Damien Horsley wrote:
>
>> +static inline u32 img_i2s_in_ch_disable(struct img_i2s_in *i2s, u32 chan)
>> +{
>> +u32 reg;
>> +
>> +reg = img_i2s_in_ch_readl(i2s, chan, IMG_I2S_IN_CH_CTL);
>> +reg &=
I'm announcing the release of the 3.4.110 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
Comments inline below:
> This change turns the UFS variant (SCSI_UFS_QCOM) into a UFS
> a platform device.
> In order to do so a few additional changes are required:
> 1. The ufshcd-pltfrm is no longer serves as a platform device.
>Now it only serves as a group of platform APIs such as PM
On Thu, 2015-10-22 at 03:53 +0530, Muhammad Falak R Wani wrote:
> Use struct pci_device_id instead of DEFINE_PCI_DEVICE_TABLE with
> the goal of getting rid of this macro completely, as this macro
> is deprecated.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
>
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 43e41adc9e8c36545888d78fed2ef8d102a938dc:
>
> perf record: Add ability to sample call branches (2015-10-20 10:30:55 +0200)
>
> are
On Wed, 21 Oct 2015 21:18:45 +0200
Hans de Goede wrote:
> Great to see that you've started working on this again. Last weekend I
> ended up working on this too together with Reinder E.N. de Haan
>
> (added to the Cc).
>
> We took a slightly different
>
> When migrating anonymous memory from system memory to device memory
> CPU pte are replaced with special HMM swap entry so that page fault,
> get user page (gup), fork, ... are properly redirected to HMM helpers.
>
> This patch only add the new swap type entry and hooks HMM helpers
>
On Wed, Oct 21, 2015 at 06:20:26PM +0200, Jens Kuske wrote:
> Adding a new compatible allows us to define SoC specific behaviour
> if necessary, for example forcing a particular device out of reset
> even if no driver is actually using it.
>
> Signed-off-by: Jens Kuske
commit-0f96a99 introduces the following warning message:
drivers/firmware/efi/fake_mem.c:186:20: warning: cast to pointer
from integer of different size [-Wint-to-pointer-cast]
new_memmap_phy was defined as a u64 value and casted to void*.
This causes a warning of int-to-pointer-cast on x86
--
> 1 file changed, 12 insertions(+), 49 deletions(-)
This patch breaks compound page futexes with the following panic:
[ 33.465456] general protection fault: [#1] SMP
[ 33.465991] CPU: 1 PID: 523 Comm: tst Not tainted 4.3.0-rc6-next-201510
This patch add hw_reset for dw_mmc to implement hw reset
procedure. It's useful for mmc core to recover emmc devices
if emmc runs into unexpected state. Add MMC_CAP_HW_RESET
capability to dw_mmc extension driver directly if it needs hw_reset.
Signed-off-by: Shawn Lin
dax_clear_blocks is currently performing a cond_resched() after every
PAGE_SIZE memset. We need not check so frequently, for example md-raid
only calls cond_resched() at stripe granularity. Also, in preparation
for introducing a dax_map_atomic() operation that temporarily pins a dax
mapping move
Both, __dax_pmd_fault, and clear_pmem() were taking special steps to
clear memory a page at a time to take advantage of non-temporal
clear_page() implementations. However, x86_64 does not use
non-temporal instructions for clear_page(), and arch_clear_pmem() was
always incurring the cost of
As requested [1], break out the block specific updates from the dax-gup
series [2], to merge via the block tree.
1/ Enable dax mappings for raw block devices. This addresses the review
comments (from Ross and Honza) from the RFC [3].
2/ Introduce dax_map_atomic() to fix races between device
Hi,
On 10/22/2015 07:35 AM, Wanpeng Li wrote:
[...]
Now, if I understand correctly the issue is that dl_task_timer() does:
rq = task_rq_lock(p, );
[...]
if (has_pushable_dl_tasks(rq))
push_dl_task(rq);
with task_rq_lock() that pins rq->lock and push_tl_task() that invokes
Looks good to me.
Reviewed-by: Subhash Jadavani
> Some of the data structures (like response UPIU) and/or its elements
> (unused fields) should be cleared before sending out the respective
> command to UFS device.
>
> This change clears the UPIU response data structure
Hi Fida,
On 10/21/2015 12:58 PM, Fida Mohammad wrote:
Use of resource managed function devm_led_classdev_register to
make initialization path simpler. Also removed redundant remove
function.
Signed-off-by: Fida Mohammad
---
drivers/leds/leds-wrap.c | 26
Hi Ingo,
On Thu, Oct 22, 2015 at 4:32 PM, Ingo Molnar wrote:
>
> * Namhyung Kim wrote:
>
>> The caller callchain order is useful with --children option since it can
>> show 'overview' style output, but other commands which don't use
>> --children feature
On 2015/10/22 14:21, Alexei Starovoitov wrote:
On 10/21/15 10:31 PM, Wangnan (F) wrote:
+if ((attr->type != PERF_TYPE_RAW &&
+ !(attr->type == PERF_TYPE_SOFTWARE &&
+ attr->config == PERF_COUNT_SW_BPF_OUTPUT) &&
+ attr->type != PERF_TYPE_HARDWARE) ||
+
This patch changes return type of pstore_is_mounted from int to bool.
Signed-off-by: Geliang Tang
---
fs/pstore/inode.c| 2 +-
fs/pstore/internal.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
index
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde [mailto:m...@pengutronix.de]
> Sent: Thursday, October 22, 2015 1:52 PM
> To: Arnd Bergmann; linux-arm-ker...@lists.infradead.org
> Cc: Appana Durga Kedareswara Rao; Anirudha Sarangi; w...@grandegger.com;
> Michal Simek; Soren
Since nested variants of mdiobus_read/write are used in multiple
drivers, add nested variants in the mdiobus core.
Suggested-by: Andrew Lunn
Signed-off-by: Neil Armstrong
---
drivers/net/phy/mdio_bus.c | 55 ++
In order to avoid locked signal false positive for nested mdiobus
read/write calls, nested code was introduced in mv88e6xxx and
mdio-mux.
But mv88e6060 also needs such nested mdiobus read/write calls.
For sake of refactoring, introduce nested variants of mdiobus read/write
and make them used by
On Thu, Oct 22, 2015 at 10:29:59AM +0200, Jean-Francois Moine wrote:
> On Thu, 22 Oct 2015 10:05:08 +0200
> Maxime Ripard wrote:
>
> > > + uart0: serial@01c28000 {
> > > + compatible = "snps,dw-apb-uart";
> > > + reg =
* Arnaldo Carvalho de Melo wrote:
> > 5) --no-children
> >
> > I agree that 'perf top -g --no-children' looks more intuitive than 'perf
> > top -g'.
>
> So, what do you propose, to switch back the default to --no-children, for
> both
> tools, top and report? Now that I am
On Thu, Oct 22, 2015 at 10:21:36AM +0900, Minchan Kim wrote:
> Hello Hugh,
>
> On Wed, Oct 21, 2015 at 05:59:59PM -0700, Hugh Dickins wrote:
> > On Thu, 22 Oct 2015, Minchan Kim wrote:
> > >
> > > I added the code to check it and queued it again but I had another oops
> > > in this time but
On Wed, Oct 21, 2015 at 10:07:44PM -0600, Jens Axboe wrote:
> On 10/21/2015 06:31 PM, Tejun Heo wrote:
> >Hello, Jens.
> >
> >This is one of hopefully final adjustments to cgroup v2 behavior
> >before lifting the devel mask. If the patch is okay, can I route the
> >patch through cgroup/for-4.4 so
Adjust the return value of parse_ioapics_under_ir as negative value representing
failure and "0" representing succcess. Just make it consistent with other
function implementation, and we can judge if calling is successfull by
if (!parse_ioapics_under_ir()) style.
Signed-off-by: Baoquan He
MMC core stack and blk layer can do some recovery if mmc
device runs into broken state for any reasons. So we implement it
for DesignWare MMC host controller.
>From Synopsys DesignWare Cores Mobile Storage Host Databook
(Section 7.4.4), we get the details:
1. Program CMD12 to end any transfer in
This patch implement hw_reset function for DesignWare
MMC controller. By adding this feature, mmc blk can
do some basic recovery if emmc device cannot work any
more for unknown reasons.
Signed-off-by: Shawn Lin
---
drivers/mmc/host/dw_mmc.c | 29
On 10/21/15 10:31 PM, Wangnan (F) wrote:
+if ((attr->type != PERF_TYPE_RAW &&
+ !(attr->type == PERF_TYPE_SOFTWARE &&
+ attr->config == PERF_COUNT_SW_BPF_OUTPUT) &&
+ attr->type != PERF_TYPE_HARDWARE) ||
+attr->inherit) {
This 'if' statement is so complex.
The hifn_795x driver is old and have lots of style issue.
This patch try to solve easy ones.
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 301 +
1 file changed, 138 insertions(+), 163 deletions(-)
diff
The hifn_test function is redundant with test done at register time by
the crypto API, so remove it.
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 58 --
1 file changed, 58 deletions(-)
diff --git
The oom_adj has been replaced by oom_score_adj in kernel,
but the /proc/pid/oom_adj is provided for legacy purposes.
When write/read a value into/from /proc/pid/oom_adj,
there is a transformation between oom_adj and oom_score_adj.
After writing a new value into /proc/pid/oom_adj, then read it.
>
> -int copy_page_range(struct mm_struct *dst, struct mm_struct *src,
> - struct vm_area_struct *vma);
> +int copy_page_range(struct mm_struct *dst_mm, struct mm_struct *src_mm,
> + struct vm_area_struct *dst_vma,
> + struct vm_area_struct
On Thu, Oct 22, 2015 at 4:29 PM, Wangnan (F) wrote:
>
>
> On 2015/10/22 15:16, Namhyung Kim wrote:
>>
>> Hi,
>>
>> On Wed, Oct 21, 2015 at 10:00 PM, Wangnan (F) wrote:
>>>
>>>
>>> On 2015/10/21 16:53, Namhyung Kim wrote:
Hi,
On Wed,
On 2015/10/22 15:53, Namhyung Kim wrote:
On Thu, Oct 22, 2015 at 4:29 PM, Wangnan (F) wrote:
[SNIP]
I understand the need of using aliases but I think it's more natural
to use event name for simple cases..
I will consider this. However, if we allow using event name
Hi!
On Wed, Oct 21, 2015 at 04:33:53PM -0700, Stephen Boyd wrote:
> These APIs aren't used, so remove them. This can be reverted if
> we get a user at some point.
>
> Cc: Maxime Ripard
> Suggested-by: Michael Turquette
> Signed-off-by:
Hi,
On 22-10-15 09:49, Jens Kuske wrote:
Hi,
On 21/10/15 21:18, Hans de Goede wrote:
Great to see that you've started working on this again. Last weekend I
ended up working on this too together with Reinder E.N. de Haan
(added to the Cc).
We took a slightly different
On Thursday 22 October 2015 10:21:58 Marc Kleine-Budde wrote:
> On 10/22/2015 10:14 AM, Arnd Bergmann wrote:
> > On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
> >> The driver only supports memory-mapped I/O [by ioremap()],
> >> so readl/writel is actually the right thing to
On Thu, Oct 22, 2015 at 11:40 AM, Christoph Hellwig wrote:
> On Tue, Oct 20, 2015 at 01:53:42PM +0300, Daniel Baluta wrote:
>> We don't want to hardcode default groups at subsystem
>> creation time. We export:
>> * configfs_register_group
>> * configfs_unregister_group
>>
The caller callchain order is useful with --children option since it can
show 'overview' style output, but other commands which don't use
--children feature like 'perf script' or even 'perf report/top' without
--children are better to keep caller order.
Cc: Adrian Hunter
Looks good to me.
Reviewed-by: Subhash Jadavani
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 34 +-
> drivers/scsi/ufs/ufshcd.h | 21 +
> 2 files changed, 38
Looks good to me.
Reviewed-by: Subhash Jadavani
> New revisions of UFS host controller supports the new UniPro
> hardware controller (referred as QUniPro). This patch adds
> the support to enable this new UniPro controller hardware.
>
> This change also adds power
* Namhyung Kim wrote:
> The caller callchain order is useful with --children option since it can
> show 'overview' style output, but other commands which don't use
> --children feature like 'perf script' or even 'perf report/top' without
> --children are better to keep
earliest_dl.next is used to cache the next earliest ready task
which also is pushable in order to be a candidate of pushable
tasks during pull algorithm. If the earliest_dl.next deadline
of the sr_rq is earlier than the earliest_dl.curr deadline of
current rq, the task from the sr_rq can be
Hello,
> diff --git a/include/linux/eventfd.h b/include/linux/eventfd.h
> index ff0b981..87de343 100644
> --- a/include/linux/eventfd.h
> +++ b/include/linux/eventfd.h
>
> -/*
> - * CAREFUL: Check include/uapi/asm-generic/fcntl.h when defining
> - * new flags, since they might collide with O_*
On Thursday 22 October 2015 07:02:14 subha...@codeaurora.org wrote:
> >
> > Required properties:
> > -- compatible: compatible list, contains "jedec,ufs-1.1"
> > +- compatible: compatible list, contains "jedec,ufs-1.1" or
> > + "qcom,msm8994-ufshc" or
Hi,
On Wed, Oct 21, 2015 at 06:20:27PM +0200, Jens Kuske wrote:
> The Allwinner H3 is a home entertainment system oriented SoC with
> four Cortex-A7 cores and a Mali-400MP2 GPU.
>
> Signed-off-by: Jens Kuske
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 499
>
On Thu, 22 Oct 2015 10:05:08 +0200
Maxime Ripard wrote:
> > + uart0: serial@01c28000 {
> > + compatible = "snps,dw-apb-uart";
> > + reg = <0x01c28000 0x400>;
> > + interrupts = ;
> > +
Hi,
On Thu, Oct 22, 2015 at 01:21:26AM -0700, josef.gajdu...@gmail.com wrote:
> Hi everyone,
>
> I might be missing something, but why is the PL* GPIO bank not
> declared here?
Because it's in the PRCM. This one was adding support for the main
port controller.
Maxime
--
Maxime Ripard, Free
> On 22 okt. 2015, at 19:28, Taku Izumi wrote:
>
> commit-0f96a99 introduces the following warning message:
>
> drivers/firmware/efi/fake_mem.c:186:20: warning: cast to pointer
> from integer of different size [-Wint-to-pointer-cast]
>
> new_memmap_phy was defined
Looks good to me.
Reviewed-by: Subhash Jadavani
> This patch exposes the ioctl interface for UFS driver via SCSI device
> ioctl interface. As of now UFS driver would provide the ioctl for query
> interface to connected UFS device.
>
> Signed-off-by: Dolev Raviv
Hi Geert-san,
> Sent: Tuesday, October 20, 2015 9:22 PM
>
> Hi Shimoda-san,
>
> On Tue, Oct 20, 2015 at 2:18 PM, Yoshihiro Shimoda
> wrote:
> > This patch fixes an issue that the "length" of scatterlist should be
> > set using sh_dma_length(). Otherwise, a
Looks good to me.
Reviewed-by: Subhash Jadavani
> In order to simplify the code a set of wrapper functions is created
> to test and call each of the variant operations.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 1 -
Looks good to me.
Reviewed-by: Subhash Jadavani
> This change is required in order to be able to build the component
> as a module.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: 21 October 2015 23:15
> To: Wangzhou (B)
> Cc: Bjorn Helgaas; jingooh...@gmail.com; pratyush.an...@gmail.com; Arnd
> Bergmann; li...@arm.linux.org.uk; thomas.petazz...@free-electrons.com;
> Gabriele Paoloni;
On Thu, 2015-10-22 at 04:16 +0530, Muhammad Falak R Wani wrote:
> Remove boilerplate code by using macro module_pci_driver.
> For drivers whose __init and __exit paths only register and
> unregister to the pci API, it is preferred to use this macro.
>
> Signed-off-by: Muhammad Falak R Wani
* Wangnan (F) wrote:
>
>
> On 2015/10/22 0:57, Peter Zijlstra wrote:
> >On Wed, Oct 21, 2015 at 11:06:47PM +0800, pi3orama wrote:
> >>>So explain; how does this eBPF stuff work.
> >>I think I get your point this time, and let me explain the eBPF stuff to
> >>you.
> >>
>
On 22/10/15 02:15, Julian Calaby wrote:
>
> This hunk should be in patch 1:
Indeed, Thanks.
Jens
>
>> @@ -1000,9 +1005,8 @@ static void __init sunxi_divs_clk_setup(struct
>> device_node *node,
>>
>> for (i = 0; i < SUNXI_DIVS_BASE_NAME_MAX_LEN - 1 &&
>>
This patch adds a comment before waitqueue_active noting that memory
barriers are required.
In the following code, the wake_up thread might fail to wake up the
waiting thread and leave it sleeping due to lack of memory barriers.
wake_up thread waiting thread
* Namhyung Kim wrote:
> +#define CALLCHAIN_HELP "setup and enables call-graph (stack chain/backtrace)
> recording: "
> +
> +#ifdef HAVE_DWARF_UNWIND_SUPPORT
> +#define CALLCHAIN_RECORD_HELP CALLCHAIN_HELP "fp dwarf lbr"
> +#else
> +#define CALLCHAIN_RECORD_HELP
On Tue, 20 Oct 2015, Thomas Gleixner wrote:
> On Tue, 20 Oct 2015, Russell King - ARM Linux wrote:
> > I think Rob's patches need another review in light of this, to determine
> > how much breakage there is here, and a decision how to proceed made on
> > that basis.
>
> I'll go over them tomorrow
Peter Zijlstra wrote:
> On Fri, Oct 09, 2015 at 12:35:59AM +, Kosuke Tatsukawa wrote:
>> This patch adds a comment before waitqueue_active noting that a memory
>> barrier is required.
>>
>> Besides the original problem in drivers/tty/n_tty.c which caused a
>> program stall (described in
On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
> The driver only supports memory-mapped I/O [by ioremap()],
> so readl/writel is actually the right thing to do, IMO.
> During the validation of this driver or IP on ARM 64-bit processor
> while sending lot of packets observed
Hello Anand,
On 10/22/2015 07:03 AM, Anand Moon wrote:
> Hi Javier,
>
> On 22 October 2015 at 08:22, Javier Martinez Canillas
> wrote:
>> Hello Krzysztof,
>>
>> On 10/22/2015 03:43 AM, Krzysztof Kozlowski wrote:
>>> On 22.10.2015 10:20, Javier Martinez Canillas wrote:>
Looks good to me.
Reviewed-by: Subhash Jadavani
> Export the following functions in order to avoid build errors
> when the component PHY_QCOM_UFS is compiled as a module:
>
> ERROR: "ufs_qcom_phy_disable_ref_clk"
> [drivers/scsi/ufs/ufs-qcom.ko] undefined!
> ERROR:
Hi Thomas,
I got the following call trace when I called some set time syscalls in
userspace.
---start---
Jan 01 00:02:29 Linux kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Jan 01 00:02:29 Linux kernel: 0: (2 GPs behind) idle=913/1/0
softirq=59289/59291 fqs=488
Jan 01
1 - 100 of 1836 matches
Mail list logo