pr_err() messages should end with a new-line to avoid other messages
being concatenated.
Signed-off-by: Arvind Yadav
---
drivers/input/input.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/input.c b/drivers/input/input.c
index d268fdc..ffb8642 100644
--- a/dri
Coverity-scan recently found a possible NULL pointer dereference in
fc_block_scsi_eh() as starget_to_rport() either returns the rport for
the startget or NULL.
While it is rather unlikely to have fc_block_scsi_eh() called without
an rport associated it's a good idea to catch potential misuses of t
On Tue, Sep 26, 2017 at 07:09:14AM +0200, Daniel Vetter wrote:
> On Mon, Sep 25, 2017 at 11:26:27AM -0700, Laura Abbott wrote:
> > On 09/20/2017 01:45 AM, Benjamin Gaignard wrote:
> > > Instead a getting one common device "/dev/ion" for
> > > all the heaps this patch allow to create one device
> >
On Mon, Sep 25, 2017 at 11:29:07PM +, Bart Van Assche wrote:
> Did you perhaps intend to use WARN_ON_ONCE() instead of WARN_ON()?
Now that you're saying it. I'll send a v2.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumsh...@suse.de
This patch will make all print functions receive the fp argument, and opens
a dump file in process_event function
Changes since v1:
- modify the dump file name to -script-dump-.txt
ect. perf.data-script-dump-cycles.txt, perf.data-script-dump-cs.txt
- split the original patch(Make all those related
Hi Rohit,
Just some comments:
On Mon, Sep 25, 2017 at 5:02 PM, Rohit Jain wrote:
> While looking for CPUs to place running tasks on, the scheduler
> completely ignores the capacity stolen away by RT/IRQ tasks.
>
> This patch fixes that.
>
> Signed-off-by: Rohit Jain
> ---
> kernel/sched/fair.c
It would be somewhat safer to put parentheses around parameters of
a macro with parameters. Put it.
Signed-off-by: Byungchul Park
---
include/linux/llist.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/llist.h b/include/linux/llist.h
index 1957635..e280b
On Tue, Sep 26, 2017 at 01:15:41AM +0300, Dmitry Osipenko wrote:
> This driver provides accelerated video decoding to NVIDIA Tegra20 SoC's,
> it is a result of reverse-engineering efforts. Driver has been tested on
> Toshiba AC100 and Acer A500, it should work on any Tegra20 device.
>
> In userspa
pr_err() messages should end with a new-line to avoid other messages
being concatenated.
Signed-off-by: Arvind Yadav
---
drivers/infiniband/hw/ocrdma/ocrdma_stats.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/ocrdma/ocrdma_stats.c
b/drivers/infiniba
On Mon, Sep 25, 2017 at 06:50:00PM -0500, Bjorn Helgaas wrote:
> Greg, I assume you'll deal with this one? Just let me know if I
> should do something with it.
I've already applied it to my driver-core-next tree, thanks.
greg k-h
pr_err() and mlx5_ib_dbg( messages should terminated with a new-line to
avoid other messages being concatenated.
Signed-off-by: Arvind Yadav
---
drivers/infiniband/hw/mlx5/mr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/mlx5/mr.c b/drivers/infin
Introduce a new option to print trace output to files named by the
monitored events and update perf-script documentation accordingly.
Shown below is output of perf script command with the newly introduced
option.
$perf record -e cycles -e cs -ag -- sleep 10
$perf script --per-e
This patch will add the fp argument to all the print functions so that they can
use different
file pointer to print on the screen or dump in the file.
Changes since v1:
- add the __maybe_unused attribute for the fp argument in all the print
functions,
because the fp is not used in this patch bu
This patch will replace printf with fprintf for all print functions in the
builtin-script in order to support the per-event-dump option.
Changes since v1:
- remove the fp_selection_helper function for setting the fp argument, and use
a local variable to do the same thing.
Signed-off-by: yuzhouji
This patch will add a new bool variable per_event_dump to mark the
per-event-dump option,
and add the OPT_BOOLEAN for per-event-dump in the perf_data_file struct.
Changes since v1:
- remove the set for script.tool.per_event_dump variable,since the OPT_BOOLEAN
will do the same thing.
Signed-off-
On Mon, Sep 25, 2017 at 11:32 PM, Arnd Bergmann wrote:
> On Mon, Sep 25, 2017 at 7:41 AM, David Laight wrote:
>> From: Arnd Bergmann
>>> Sent: 22 September 2017 22:29
>> ...
>>> It seems that this is triggered in part by using strlcpy(), which the
>>> compiler doesn't recognize as copying at most
On Mon, 25 Sep 2017, Tejun Heo wrote:
> Hello,
>
> On Mon, Sep 25, 2017 at 04:33:02PM +0100, Mark Rutland wrote:
> > Unfortunately, the generic this_cpu_read(), which is intended to be
> > irq-safe, is not:
> >
> > #define this_cpu_generic_read(pcp) \
> > ({
On Mon, Sep 25, 2017 at 02:41:56PM -0400, Chris Gorman wrote:
> fixed typo in comment for north_community
>
> Signed-off-by: Chris Gorman
Please fix title to be something like "pinctrl: cherryview: Fix typo
in comment". And also in the commit message, start it with capital
letter and end with ".
On Tue, Sep 26, 2017 at 02:41:35PM +0800, AceLan Kao wrote:
> Some platform(BIOS) blocks legacy interrupts (INTx), and only allows MSI
> for WLAN device. So adding a quirk to list those machines and set
> use_msi automatically.
> Adding Dell Inspiron 24-3460 to the quirk.
Huh? Using MSI should be
BIOS on Dell Vostro 15-3572 blocks legacy interrupts (INTx),
and only allows MSI for WLAN device.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/init.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9
BIOS on Dell Inspiron 14-3473 blocks legacy interrupts (INTx),
and only allows MSI for WLAN device.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/init.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/at
> When using tc qdisc to configure DCB parameter, dcb_ops->setup_tc
> is used to tell hclge_dcb module to do the setup.
While this might be a step in the right direction, this causes an inconsistency
in user experience - Some [well, most] vendors didn't allow the mqprio
priority mapping to affect
On Mon, Sep 25, 2017 at 06:37:28PM -0700, Linus Torvalds wrote:
> Pulled and pushed out, but I'd like to note that sparse would have
> caught this. Except we are so far away from being sparse-clean that
> nobody runs it.
I tend to run sparse over the nvme code before sending pull request
every tim
On (09/18/17 00:01), Masahiro Yamada wrote:
> Commit 069f0cd00df0 ("printk: Make the printk*once() variants return
> a value") surrounded the macro implementation with ({ ... }).
>
> Now, the inner do { ... } while (0); is redundant.
>
> Signed-off-by: Masahiro Yamada
looks ok to me. can't say
BIOS on Dell Inspiron 3472 blocks legacy interrupts (INTx),
and only allows MSI for WLAN device.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/init.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9k
Adding MSI support for ath9k devices.
This patch is originally from Qualcomm, but they have no intention of
submitting and maintaining ath9k driver now.
The credit should go to Qualcomm.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/hw.c | 33 ++--
drivers/ne
Some platform(BIOS) blocks legacy interrupts (INTx), and only allows MSI
for WLAN device. So adding a quirk to list those machines and set
use_msi automatically.
Adding Dell Inspiron 24-3460 to the quirk.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/init.c | 21 ++
On Tue, 26 Sep 2017 12:39:24 +0900
Masahiro Yamada wrote:
> Read Status and Read ID require tWHR before reading the first data.
> Insert a very short wait to make sure to meet the spec.
>
> I have not seen any problem report for now, but nand_command() and
> nand_command_lP() are generic hooks,
BIOS on Dell Vostro 3262 blocks legacy interrupts (INTx),
and only allows MSI for WLAN device.
Signed-off-by: AceLan Kao
---
drivers/net/wireless/ath/ath9k/init.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9k/i
On Mon, Sep 25, 2017 at 05:13:59PM -0600, Ross Zwisler wrote:
> Currently only the blocksize is checked, but we should really be calling
> bdev_dax_supported() which also tests to make sure we can get a
> struct dax_device and that the dax_direct_access() path is working.
>
> This is the same chec
>
> A bit late to a party, but:
>
> On Mon, Dec 8, 2014 at 12:50 AM, Amos Kong wrote:
> > From: Rusty Russell
> >
> > There's currently a big lock around everything, and it means that we
> > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current)
> > while the rng is reading. T
On Mon, Sep 25, 2017 at 05:14:04PM -0600, Ross Zwisler wrote:
> Re-enable the XFS per-inode DAX flag, preventing S_DAX from changing when
> any mappings are present.
Before we re-enable it please come up with a coherent description
of the per-inode DAX flag that makes sense to a user. We'll also
Bjorn Helgaas writes:
> On Mon, Sep 11, 2017 at 04:55:11AM -0700, Greg Kroah-Hartman wrote:
>> On Mon, Sep 11, 2017 at 09:45:41AM +0200, Nicolai Stange wrote:
>> > Quote from Documentation/filesystems/sysfs.txt:
>> >
>> > show() must not use snprintf() when formatting the value to be
>> > re
On Mon, Sep 25, 2017 at 05:14:03PM -0600, Ross Zwisler wrote:
> When mappings are created the vma->vm_flags that they use vary based on
> whether the inode being mapped is using DAX or not. This setup happens in
> XFS via mmap_region()=>call_mmap()=>xfs_file_mmap().
>
> For us to be able to safel
> +static bool
> +xfs_is_dax_state_changing(
> + unsigned intxflags,
> + struct xfs_inode*ip)
And I have no fricking idea what 'is_dax_state_changing' is supposed
to mean for the caller. This needs a better name and/or a comment
explaining the function.
On 2017年09月26日 13:12, Daniel Vetter wrote:
On Thu, Sep 21, 2017 at 09:02:22AM +0800, Mark yao wrote:
On 2017年09月21日 06:29, Thomas Meyer wrote:
Use vma_pages function on vma object instead of explicit computation.
Found by coccinelle spatch "api/vma_pages.cocci"
Signed-off-by: Thomas Meyer
---
On Mon, Sep 25, 2017 at 7:41 AM, David Laight wrote:
> From: Arnd Bergmann
>> Sent: 22 September 2017 22:29
> ...
>> It seems that this is triggered in part by using strlcpy(), which the
>> compiler doesn't recognize as copying at most 'len' bytes, since strlcpy
>> is not part of the C standard.
>
The S6SY761 touchscreen is a capicitive multi-touch controller
for mobile use. It's connected with i2c at the address 0x48.
This commit provides a basic version of the driver which can
handle only initialization, touch events and power states.
The controller is controlled by a firmware which, in
We can't just take locking one level up, as we need differnet locking
for different kinds of I/O.
I think you probably want an IOCB_DAX flag to check IS_DAX once and
then stick to it, similar to what we do for direct I/O.
On (09/06/17 10:27), Rob Herring wrote:
[..]
> > Rob, Grant,
> > will this dirty hack work for you? I can respin the patch.
>
> Yes, as long as you intend to fix things later.
Rob, sorry for the delay, I just sent out a simple patch. It contains that
'less-than-pretty' const cast. As of updating
Do not strdup() console options. It seems that the only reason for
it to be strdup()-ed was a compilation warning: printk, UART and
console drivers, for some reason, expect char pointer instead of
const char pointer. So we can just pass `of_stdout_options', but
need to cast it to char pointer. A be
* Fengguang Wu wrote:
> On Mon, Sep 25, 2017 at 04:55:09PM +0200, Ingo Molnar wrote:
> >
> > * Fengguang Wu wrote:
> >
> > > On Mon, Sep 25, 2017 at 10:20:13AM +0800, kernel test robot wrote:
> > > > Hi Ingo,
> > > >
> > > > On your request I'm resending the report here, with attached dmesg,
>
From: Alexander Usyskin
This patch fixes a regression caused by the new changes
in the "run wake" handlers.
The mei devices that support D0i3 are no longer receiving an interrupt
after entering runtime suspend state and will stall.
pci_dev_run_wake function now returns "true" for some devices
(
All error handling paths 'goto err_drop_spawn' except this one.
In order to avoid some resources leak, we should do it as well here.
Fixes: f1c131b45410 ("crypto: xts - Convert to skcipher")
Signed-off-by: Christophe JAILLET
---
crypto/xts.c | 6 --
1 file changed, 4 insertions(+), 2 deletio
Hi, Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Tuesday, September 26, 2017 12:14 PM
> To: Zhang, Rui ; Rafal Milecki
> Cc: Markus Mayer ; Eduardo Valentin
> ; Rob Herring ; Mark Rutland
> ; Doug Berger ; Brian
> Norris ; Gregory Fong
> ; R
pr_err() messages should end with a new-line to avoid other messages
being concatenated.
Signed-off-by: Arvind Yadav
---
drivers/hsi/clients/hsi_char.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hsi/clients/hsi_char.c b/drivers/hsi/clients/hsi_char.c
index 57
On 26 September 2017 04:54:41 BST, Stephen Rothwell
wrote:
>Hi Greg,
>
>After merging the staging tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>
>drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field
>'driver_module' specified in initializer
> .driver_m
The only way of stopping the watchdog is by resetting it.
Add the watchdog op for stopping the device and reset if
a reset line is provided.
At same time WDOG_HW_RUNNING should be remove from dw_wdt_start.
As commented by Guenter Roeck:
dw_wdt sets WDOG_HW_RUNNING in its open function. Result is
t
Hi Arnaldo and all,
Is there someone looking at this issue? I can provide more info if you need.
This issue makes it so inconvenient to use perf. Thanks.
On Wed, Sep 13, 2017 at 09:54:25AM +0800, Du, Changbin wrote:
> On Tue, Sep 12, 2017 at 11:33:50AM -0300, Arnaldo Carvalho de Melo wrote:
> > E
From: Steffen Trumtrar
Signed-off-by: Steffen Trumtrar
Signed-off-by: Oleksij Rempel
Cc: Dinh Nguyen
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/boot/dts/socfpga.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dts
On Tue, Sep 26, 2017 at 09:48:01AM +0800, 陈华才 wrote:
> Hi, Christoph,
>
> Can I put the declaration in asm/dma-coherence.h?
Generally something not expose to the rest of the kernel (that is not
in arch/mips/include/) would be preferred, but in the end the architecture
maintainer will have to deci
Ping for review status, thanks.
On Fri, Sep 15, 2017 at 07:19:31PM +0800, changbin...@intel.com wrote:
> From: Changbin Du
>
> There are some trace options to control what gets printed in the trace
> output or manipulate the tracers. This patch add a commandline option
> to set it.
>
> Example
Maintenance releases Git v2.10.5, v2.11.4, v2.12.5 and v2.13.6 are
now available at the usual places. These are solely about hardening
"git shell" that is used on servers against an unsafe user input,
which "git cvsserver" copes with poorly. A copy of the release notes
for v2.10.5 is attached at
The latest maintenance release Git v2.14.2 is now available at the
usual places. In addition to the cvsserver related fixes that
appear in 2.10.5, 2.11.4, 2.12.5 and 2.13.6 announced separately,
this also includes various fixes that were merged already to the
'master' branch.
The tarballs are fou
On Thu, 21 Sep 2017 17:01:05 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> MTK_PMIC_WRAP is the basic and required configuration for those various
> MediaTek PMICs, so turning MTK_PMIC_WRAP into visible symbols easily
> allows users tending to have the enablement for those PMICs.
I
Ops, sorry,
this patch must have come from the wrong branch on my PC as this
driver has also been tested as module :/
Sorry,
I will send the patch v4 with this fix.
Andi
On Tue, Sep 26, 2017 at 09:02:41AM +0800, kbuild test robot wrote:
> Hi Andi,
>
> [auto build test ERROR on input/next]
> [a
On Thu, 21 Sep 2017 16:46:35 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Add cleanup for placing all Kconfig for all MediaTek SoC drivers under
> the independent menu as other SoCs vendor usually did.
>
> Signed-off-by: Sean Wang
> ---
> drivers/soc/mediatek/Kconfig | 4
>
Hi Tatsiana,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.14-rc2 next-20170922]
[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/Alexey-Dobriyan/fdmap-2/20170926-105150
[+Rafael, Ulf]
On Tue, Sep 26, 2017 at 2:29 PM, Mohandass, Divagar
wrote:
> Hi Sakari & Tomas,
>
> Are you ok with the current revision, let me know if any changes are needed.
Nope, my concerns have not been addressed, but we need someone from
the PM world to clarify how we should do this to wor
Hi Sakari & Tomas,
Are you ok with the current revision, let me know if any changes are needed.
---
^Divagar
>-Original Message-
>From: sakari.ai...@iki.fi [mailto:sakari.ai...@iki.fi]
>Sent: Wednesday, September 20, 2017 3:02 PM
>To: Tomasz Figa
>Cc: Mani, Rajmohan ; Mohandass, Divagar
Hi Andy,
Sorry missed the 'Suggested-by' tag. Can I resend the v6 with this change, so
that Wolfram can pick these patches ?
---
^Divagar
>-Original Message-
>From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
>Sent: Friday, September 22, 2017 9:42 PM
>To: Mani, Rajmohan
>Cc: Moh
On 25.09.2017 18:17, Guenter Roeck wrote:
If a watchdog driver's open function sets WDOG_HW_RUNNING with the
expectation that the watchdog can not be stopped, but then stops the
watchdog anyway in its stop function, kref_get() wil not be called in
watchdog_open(). If the watchdog then stops on cl
Hi,
On 25.09.2017 18:16, Guenter Roeck wrote:
On Mon, Sep 25, 2017 at 07:25:30AM +0200, Oleksij Rempel wrote:
From: Steffen Trumtrar
The only way of stopping the watchdog is by resetting it.
Add the watchdog op for stopping the device and reset if
a reset line is provided.
Signed-off-by: Ste
re32 (bc27113620ca unicore32-oldabi: add oldabi syscall
interface)
CONFLICT (content): Merge conflict in arch/unicore32/include/asm/Kbuild
Merging xtensa/xtensa-for-next (271335b9726e Merge branch 'xtensa-fixes' into
xtensa-for-next)
Merging fscrypt/master (c250b7dd8e73 fscrypt: make ->dummy
On Thu, Sep 21, 2017 at 09:02:22AM +0800, Mark yao wrote:
> On 2017年09月21日 06:29, Thomas Meyer wrote:
> > Use vma_pages function on vma object instead of explicit computation.
> > Found by coccinelle spatch "api/vma_pages.cocci"
> >
> > Signed-off-by: Thomas Meyer
> > ---
> Looks good for me:
> A
On 09/25/2017 05:45 PM, Dmitry Osipenko wrote:
> On 26.09.2017 02:01, Stephen Warren wrote:
>> On 09/25/2017 04:15 PM, Dmitry Osipenko wrote:
>>> Video decoder, found on NVIDIA Tegra20 SoC, supports a standard set of
>>> video formats like H.264 / MPEG-4 / WMV / VC1. Currently driver supports
>>> d
On Tuesday 26 September 2017 05:35 AM, Viresh Kumar wrote:
> The drivers/base/power/ directory is special and contains code related
> to power management core like system suspend/resume, hibernation, etc.
> It was fine to keep the OPP code inside it when we had just one file for
> it, but it is gro
On Mon, Sep 25, 2017 at 11:26:27AM -0700, Laura Abbott wrote:
> On 09/20/2017 01:45 AM, Benjamin Gaignard wrote:
> > Instead a getting one common device "/dev/ion" for
> > all the heaps this patch allow to create one device
> > entry ("/dev/ionX") per heap.
> > Getting an entry per heap could allow
On Mon, 2017-09-18 at 13:15 -0700, Guenter Roeck wrote:
> On Mon, Sep 18, 2017 at 02:26:38PM -0500, Rob Herring wrote:
> > On Fri, Sep 08, 2017 at 02:39:17PM +1000, Andrew Jeffery wrote:
> > > > > > Signed-off-by: Andrew Jeffery
> > > ---
> > > .../devicetree/bindings/hwmon/pmbus/max31785.txt |
From: Hyunchul Lee
When erase count and volume identifier headers are read,
ubi_io_is_bad is called. So instead of calling ubi_io_is_bad
from scan_peb, use the result.
this patch reduces the attach time by about 15% in my
environment.
ARMv7 1GHZ based board, 66.8MiB MTD partition
On Fri, Aug 25, 2017 at 10:09:45AM -0700, Matthias Kaehlcke wrote:
> The only call of wait_for_engine() is wrapped in a GEM_WARN_ON macro,
> which confusingly suppresses the call unless CONFIG_DRM_I915_DEBUG_GEM
> is set.
>
> According to http://www.spinics.net/lists/intel-gfx/msg128768.html the
>
On 09/25/2017 07:51 PM, joelaf wrote:
Hi Rohit,
Just some comments:
Hi Joel,
Thanks for the comments
On 09/25/2017 05:02 PM, Rohit Jain wrote:
While looking for idle CPUs for a waking task, we should also account
for the delays caused due to the bandwidth reduction by RT/IRQ tasks.
This
On Thu, Sep 21, 2017 at 09:43:41AM +0300, Amir Goldstein wrote:
> On Thu, Sep 21, 2017 at 1:22 AM, Dave Chinner wrote:
> > [cc lkml, PeterZ and Byungchul]
> ...
> > The thing is, this IO completion has nothing to do with the lower
> > filesystem - it's the IO completion for the filesystem on the l
Fixes the warning:
arch/x86/kvm/vmx.c:64:32: warning: variable 'vmx_cpu_id' is not needed
and will not be emitted [-Wunneeded-internal-declaration]``
Other callers of MODULE_DEVICE_TABLE() seem to check their second
argument during driver init with the x86_match_cpu() function, if their
first argu
Hi Aliaksandr,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.14-rc2 next-20170922]
[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/Alexey-Dobriyan/fdmap-2/20170926-1051
When the arbitration between NOR and NAND flash is enabled
the field bit[21] in the Data Flash Control Register
needs to be set to 1 according to guidleine GL-5830741.
This patch introduces a new compatible string "marvell,nand-force-csx"
which is activated through device tree to implement the gu
When the arbitration between NOR and NAND flash is enabled
the field bit[21] in the Data Flash Control Register
needs to be set to 1 according to guidleine GL-5830741.
This patch series contain the following patches:
* Patch 1: "dt-bindings: mtd: pxa3xx: Add "marvell,nand-force-csx" compatible
s
When the arbitration between NOR and NAND flash is enabled
the field bit[21] in the Data Flash Control Register
needs to be set to 1 according to guidleine GL-5830741.
This commit sets the FORCE_CSX bit to 1 if the compatible
string "marvell,nand-force-csx" is enabled in the device tree
of the co
Good find, will send a patch with your suggestion. The documentation
for x86_match_cpu() says:
25 * Arrays used to match for this should also be declared using
26 * MODULE_DEVICE_TABLE(x86cpu, ...)
Will save another patch for a friend, then.
On Mon, Sep 25, 2017 at 8:35 PM, Josh Triplett w
On 09/25/2017 08:02 PM, Zhang, Rui wrote:
> Hi, Florian,
>
> This patch set was dropped in the last minute because of this discussion
> https://patchwork.kernel.org/patch/9936325/
> as I don’t want to rebase the patch before sending the pull request.
Ah, you wanted to squash that patch into the i
On Mon, Sep 25, 2017 at 11:23:31PM +0200, Richard Weinberger wrote:
> Hi!
>
> While playing with bcc's opensnoop tool on Linux 4.14-rc2 I managed to
> trigger
> this splat:
>
> [ 297.629773] WARNING: kernel stack frame pointer at 880156a5fea0 in
> bash:2103 has bad value 7ffec7d87e50
Hi Martin,
After merging the scsi-mkp tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/scsi/hisi_sas/hisi_sas_main.c: In function 'hisi_sas_controller_reset':
drivers/scsi/hisi_sas/hisi_sas_main.c:1049:24: warning: unused variable
'sas_ha' [-Wunused-variable]
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field
'driver_module' specified in initializer
.driver_module = THIS_MODULE,
^
In file included from include/linux/linkage.h
On Thu, Sep 21, 2017 at 05:47:14PM +0900, Byungchul Park wrote:
> On Thu, Sep 21, 2017 at 08:22:56AM +1000, Dave Chinner wrote:
> > Peter, this is the sort of false positive I mentioned were likely to
> > occur without some serious work to annotate the IO stack to prevent
> > them. We can nest mul
This patch fixes some spelling typos found in Kconfig files.
Signed-off-by: Masanari Iida
---
arch/alpha/Kconfig| 2 +-
arch/arc/Kconfig | 6 +++---
arch/arm/mach-bcm/Kconfig | 6 +++---
arch/arm/plat-samsung/Kconfig | 2 +-
arch/arm64
On 26-09-2017 00:16, Casey Leedom wrote:
> | From: Raj, Ashok
> | Sent: Monday, September 25, 2017 8:54 AM
> |
> | Not sure how the page->offset would end up being greater than page-size?
Refer below
> |
> | If you have additional traces, please send them by.
> |
> | Is this a new driver? wonderi
This patch fixes some spelling typo and grammar error
found in printk messages.
Signed-off-by: Masanari Iida
---
drivers/fmc/fmc-core.c| 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c | 2 +-
drivers/gpu/drm/i915/intel_cdclk.c| 4
Hi Paul,
On Mon, 25 Sep 2017 20:26:28 -0700 "Paul E. McKenney"
wrote:
>
> This conflict will disappear tomorrow, as I have merged the commit
> from Linus's tree in place of mine and have added another commit that
> removes the READ_ONCE()s. Same result, but no conflict. ;-)
Thanks, I figured
Read Status and Read ID require tWHR before reading the first data.
Insert a very short wait to make sure to meet the spec.
I have not seen any problem report for now, but nand_command() and
nand_command_lP() are generic hooks, so it makes sense to implement
fail-safe code here.
Signed-off-by: Ma
Hi, Dmitry
Always thank you for your comment.
I resent patch file modified about your comment. Please confirm it.
Incidentally, Our IC use 40bit register address I2C protocol format at
flash mode. 40 bit means just 5 byte buffers.
( address data address is as below )
--
On Mon, Sep 25, 2017 at 08:07:41PM -0700, Nick Desaulniers wrote:
> today I noticed I was getting the warning:
>
> arch/x86/kvm/vmx.c:64:32: warning: variable 'vmx_cpu_id' is not needed
> and will not be emitted [-Wunneeded-internal-declaration]
>
> seems like this was added in commit: e9bda3b3d0
When account the nr_phys_segments during merging bios into rq,
only consider segments merging in individual bio but not all
the bios in a rq. This leads to the bigger nr_phys_segments of
rq than the real one when the segments of bios in rq are
contiguous and mergeable. The nr_phys_segments of rq wi
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e365806ac289457263a133bd32df8df49897f612
commit: 39358a033b2e4432052265c1fa0f36f572d8cfb5 objtool, x86: Add facility for
asm code to provide unwind hints
date: 2 months ago
config: x86_64-randconfig-a0-092
The HiDeep touchscreen device is a capacitive multi-touch controller
mainly for multi-touch supported devices use. It use I2C interface for
communication to IC and provide axis X, Y, Z locations for ten finger
touch through input event interface to userspace.
It support the Crimson and the Lime tw
On Tue, Sep 26, 2017 at 01:00:18PM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next merge of the rcu tree got a conflict in:
>
> kernel/rcu/tree.c
>
> between commit:
>
> 28585a832602 ("rcu: Allow for page faults in NMI handlers")
>
> from Linus' tree and commit:
>
> 3e2
From: Vivien Didelot
Date: Fri, 22 Sep 2017 19:01:54 -0400
> This patchset makes slave open and close symmetrical and provides
> helpers for enabling or disabling a given DSA port.
>
> Changes in v3:
> - save the phy_device change for a future patchset
>
> Changes in v2:
> - do not remove t
From: Haiyang Zhang
Date: Fri, 22 Sep 2017 15:31:38 -0700
> From: Haiyang Zhang
>
> For older hosts without multi-channel (vRSS) support, and some error
> cases, we still need to set the real number of queues to one.
> This patch adds this missing setting.
>
> Fixes: 8195b1396ec8 ("hv_netvsc:
On Tue, 26 Sep 2017 09:23:20 +0800
zhouchengming wrote:
> On 2017/9/26 3:40, Steven Rostedt wrote:
> > On Mon, 11 Sep 2017 14:51:49 +0800
> > Zhou Chengming wrote:
> >
> >> push_rt_task() pick the first pushable task and find an eligible
> >> lowest_rq, then double_lock_balance(rq, lowest_rq).
On Sun, Sep 24, 2017 at 09:56:32PM -0700, Paul E. McKenney wrote:
> On Mon, Sep 25, 2017 at 06:41:30AM +0200, Steven Rostedt wrote:
> > Sorry for the top post, currently on a train to Paris.
> >
> > This series already went through all my testing, and I would hate to rebase
> > it for this reason
From: Arnd Bergmann
Date: Fri, 22 Sep 2017 23:29:19 +0200
> When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large
> stack frames in some functions. This goes unnoticed normally because
> CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit
> 3f181b4d8652
1 - 100 of 831 matches
Mail list logo
