Hi Nicolas,
On 21/07/16 05:22, Nicolas Pitre wrote:
> This series provides the necessary changes to allow "flat" executable
> binaries meant for no-MMU systems to actually run on systems with a MMU.
> Also thrown in are various cleanups to binfmt_flat.c.
I got to the bottom of why I couldn't run
Hi all,
Changes since 20160720:
The xfs tree gained a conflict against Linus' tree.
The net-next tree gained a conflict against the net tree.
The l2-mtd tree lost its build failure.
The crypto tree lost its build failure.
The kspp tree gained a conflict against the arm64 tree.
The
On 12/07/16 16:53, Jon Hunter wrote:
> To support UHS modes for Tegra an external regulator must be present
> to adjust the IO voltage accordingly. Even if the regulator is not
> present but the host supports the UHS modes and the device supports the
> UHS modes, then we will attempt to switch to a
Hi Sebastian,
On 07/20/2016 05:24 PM, Sebastian Andrzej Siewior wrote:
There is no need the ledtriger to be called *that* early in the hotplug
process (+ with disabled interrupts). As explained by Jacek Anaszewski [0]
there is no need for it.
Therefore this patch moves it to the ONLINE/PREPARE_D
On 20/07/16 16:04, Adrian Hunter wrote:
> On 20/07/16 16:02, Adrian Hunter wrote:
>> On 12/07/16 16:53, Jon Hunter wrote:
>>> The capabilities of the SDHCI host controller are read early during the
>>> SDHCI host initialisation in sdhci_setup_host() and before any
>>> regulators for the host have b
On Thu, Jul 21, 2016 at 08:32:34AM +0200, Pavel Machek wrote:
> Hi!
>
> > > In the mean time you can adjust the name or use XID instead.
> >
> > X has partially fixed this a few years ago. All input drivers (that
> > matter) export a Device Node property that sets the device node for each
> > dev
On Thu, Jul 21, 2016 at 08:29:50AM +0200, Maxime Ripard wrote:
> On Wed, Jul 20, 2016 at 10:29:10AM +0200, Quentin Schulz wrote:
> > + irq = regmap_irq_get_virq(sunxi_gpadc_mfd_dev->regmap_irqc, irq);
> > + ret = devm_request_any_context_irq(&pdev->dev, irq,
> > +
On 2016年07月16日 00:35, Peter Zijlstra wrote:
On Fri, Jul 15, 2016 at 12:07:03PM +0200, Peter Zijlstra wrote:
So if we are kicked by the unlock_slowpath, and the lock is stealed by
someone else, we need hash its node again and set l->locked to
_Q_SLOW_VAL, then enter pv_wait.
Right, let me go
On 07/14/2016, 10:15 AM, Jiri Slaby wrote:
> From: Florian Westphal
>
> 3.12-stable review patch. If anyone has any objections, please let me know.
>
> ===
>
> commit 36472341017529e2b12573093cc0f68719300997 upstream.
I am now dropping this one. 3.12.62 will be released without th
On Thu, 21 Jul 2016 07:13:05 +0100
Jonathan Cameron wrote:
> On 20/07/16 01:02, Dmitry Torokhov wrote:
> > On Mon, Jul 18, 2016 at 03:48:12PM +0300, Aleksei Mamlin wrote:
> >> This patch add support for Domintech DMARD06 accelerometer.
> >>
> >> Domintech DMARD06 is a low-g tri-axial digital acce
Hi!
> > In the mean time you can adjust the name or use XID instead.
>
> X has partially fixed this a few years ago. All input drivers (that
> matter) export a Device Node property that sets the device node for each
> device.
>
> $ xinput list-props "SynPS/2 Synaptics TouchPad" | grep "Device N
On Wed, Jul 20, 2016 at 10:29:10AM +0200, Quentin Schulz wrote:
> This adds support for Allwinner SoCs' (A10, A13 and A31) resistive
> touchscreen. This driver is probed by the MFD sunxi-gpadc-mfd.
>
> This driver uses ADC channels exposed through the IIO framework by
> sunxi-gpadc-iio to get its
> >>> if (atomic_read(&priv->sleepstatus.status) == 0) {
> >>> rw_data = GCR_B_DOZE;
> >>> - retval =
> >>> - ks7010_sdio_write(priv, GCR_B, &rw_data, sizeof(rw_data));
> >>> - if (retval) {
> >>> + if (ks7010_sdio_write(priv,
> >>> +
On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz
wrote:
>On Wed, Jul 20, 2016 at 9:26 PM, zhangfei
>wrote:
>>
>>
>> On 07/21/2016 11:53 AM, John Stultz wrote:
>>>
>>> After lots of debugging on an occasional DMA ERR issue, I realized
>>> that the desc structures which we point the dma hardwa
Thank you very much for the heads up, Jean!
signature.asc
Description: PGP signature
On Wed, Jul 20, 2016 at 08:40:11PM +0200, SF Markus Elfring wrote:
> >>> @@ -713,10 +713,8 @@ static int ks7010_sdio_update_index(struct
> >>> ks_wlan_private *priv, u32 index)
> >>> unsigned char *data_buf;
> >>>
> >>> data_buf = kmalloc(sizeof(u32), GFP_KERNEL);
> >>> - if (!data_buf) {
> >>
Nishanth,
On Wednesday 20 July 2016 09:03 PM, Nishanth Menon wrote:
> On 07/20/2016 09:56 AM, Mugunthan V N wrote:
>> Add documention of ti,impedance-control which can be used to
>> correct MAC impedance mismatch using phy extended registers.
>>
>> Signed-off-by: Mugunthan V N
>> ---
>> Documen
Saves ~450 bytes with my usual config.
$ size vmlinux-000 vmlinux
textdata bss dec hex filename
6752803 3325000 708608 10786411 a4966b vmlinux-000
6752355 3325000 708608 10785963 a494ab vmlinux
Signed-off-by: Alexey Dobriyan
---
fs/open.c |2 +-
1 file
On 19/07/16 19:00, Enric Balletbo Serra wrote:
> Hi Jonathan,
>
> Many thanks for your comments.
>
> 2016-07-18 15:49 GMT+02:00 Jonathan Cameron :
>> On 18/07/16 08:02, Enric Balletbo i Serra wrote:
>>> Let's update the command header to include the definitions related to
>>> the sensors attached
st [-Werror=int-conversion]
*kaddr = bank->io_addr + offset;
^
Caused by commit
6e9c9dda79d9 ("pmem: kill __pmem address space")
I have used the nvdimm tree from next-20160720 for today.
--
Cheers,
Stephen Rothwell
On 20/07/16 01:02, Dmitry Torokhov wrote:
> On Mon, Jul 18, 2016 at 03:48:12PM +0300, Aleksei Mamlin wrote:
>> This patch add support for Domintech DMARD06 accelerometer.
>>
>> Domintech DMARD06 is a low-g tri-axial digital accelerometer with
>> special power saving modes suitable for consumer mobi
Hi Quentin,
On Wed, Jul 20, 2016 at 10:29:11AM +0200, Quentin Schulz wrote:
> This probes the touchscreen driver for Allwinner SoCs (A10, A13 and A31)
> when the property "allwinner,ts-attached" is set in the GPADC (rtp) node of
> the DT.
>
> Some comestic modifications done to shorten and increa
A gentle reminder to consider the patchset for either review or acceptance.
Thanks,
Sunil.
On Tue, Jul 19, 2016 at 11:12 PM, James Morris wrote:
> On Mon, 18 Jul 2016, John Stultz wrote:
>
>> As requested, this patch implements a task_settimerslack and
>> task_gettimerslack LSM hooks so that the /proc//timerslack_ns
>> interface can have finer grained security policies applied to it.
>>
Hi Mel,
On Wed, Jul 20, 2016 at 04:21:51PM +0100, Mel Gorman wrote:
> From: Minchan Kim
>
> Minchan Kim reported that with per-zone lru state it was possible to
> identify that a normal zone with 8^M anonymous pages could trigger
> OOM with non-atomic order-0 allocations as all pages in the zone
Hi Tejun,
After merging the libata tree, today's linux-next build (arm
multi_v7_defconfig) produced these warning:
drivers/ata/libata-scsi.c: In function 'ata_mselect_caching':
drivers/ata/libata-scsi.c:3637:28: warning: suggest parentheses around
comparison in operand of '&' [-Wparentheses]
Hi,
A few months ago, Chris Arges reported a bug involving alternatives/paravirt
patching that was discussed here [1] and here [2]. To briefly summarize the
bug, patch modules that contained .altinstructions or .parainstructions
sections would break because these alternative/paravirt patches would
Introduce arch_klp_init_object_loaded() to complete any additional
arch-specific tasks during patching. Architecture code may override this
function.
Signed-off-by: Jessica Yu
---
include/linux/livepatch.h | 3 +++
kernel/livepatch/core.c | 12 ++--
2 files changed, 13 insertions(+),
Implement arch_klp_init_object_loaded() for x86, which applies
alternatives/paravirt patches. This fixes the order in which relocations
and alternatives/paravirt patches are applied.
Previously, if a patch module had alternatives or paravirt patches,
these were applied first by the module loader b
On Wed, Jul 20, 2016 at 9:26 PM, zhangfei wrote:
>
>
> On 07/21/2016 11:53 AM, John Stultz wrote:
>>
>> After lots of debugging on an occasional DMA ERR issue, I realized
>> that the desc structures which we point the dma hardware are being
>> allocated out of regular memory. This means when we fi
Boot the system without this entry generates following warning.
fb: conflicting fb hw usage mgag200drmfb vs EFI VGA - removing generic driver
After apply this patch, no more conflict message.
fb: switching to mgag200drmfb from EFI VGA
Compile and tested on DL360 Gen9 and it works both console and
I made mistake to type shane's e-mail address, so I will send version
2. Sorry for the noise.
Masanari
On Thu, Jul 21, 2016 at 2:12 PM, Masanari Iida wrote:
> Boot the system without this entry generates following warning.
> fb: conflicting fb hw usage mgag200drmfb vs EFI VGA - removing generic
On Wed, Jul 20, 2016 at 04:21:47PM +0100, Mel Gorman wrote:
> Page reclaim determines whether a pgdat is unreclaimable by examining how
> many pages have been scanned since a page was freed and comparing that
> to the LRU sizes. Skipped pages are not considered reclaim candidates but
> contribute t
Boot the system without this entry generates following warning.
fb: conflicting fb hw usage mgag200drmfb vs EFI VGA - removing generic driver
After apply this patch, no more conflict message.
fb: switching to mgag200drmfb from EFI VGA
Compile and tested on DL360 Gen9 and it works both console and
+++ Miroslav Benes [12/07/16 14:06 +0200]:
On Tue, 5 Jul 2016, Jessica Yu wrote:
Hi,
A few months ago, Chris Arges reported a bug involving alternatives/paravirt
patching that was discussed here [1] and here [2]. To briefly summarize the
bug, patch modules that contained .altinstructions or .p
This has been inconsistent; some returns -EINVAL, some -ENOTSUPP.
Make it consistent in this header, in favor of -ENOTSUPP.
Signed-off-by: Masahiro Yamada
---
include/linux/reset.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/reset.h b/include/linux/rese
The recent update in the reset subsystem requires all reset consumers
to be explicit about the requested reset lines; _explicit or _shared.
This effectively doubled the number of reset_control_get variants.
Also, we already had _optional variants.
We see some pattern in the reset_control_get APIs.
On Thu, Jul 21, 2016 at 11:06:06AM +0800, Liang, Kan wrote:
Hi Fengguang,
I located the unreachable instruction which is ud2.
This instruction will raise invalid opcode exception. So I think
normally it should not be reached. Also ud2 should be generated by
compiler, not our codes.
It's grea
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/powerpc/kernel/Makefile
between commit:
27d114966735 ("powerpc/32: Remove RELOCATABLE_PPC32")
from the powerpc tree and commit:
fd7bacbca47a ("KVM: PPC: Book3S HV: Fix TB corruption in guest exit path on
HMI inter
On 07/21/2016 11:53 AM, John Stultz wrote:
After lots of debugging on an occasional DMA ERR issue, I realized
that the desc structures which we point the dma hardware are being
allocated out of regular memory. This means when we fill the desc
structures, that data doesn't always get flushed out
On Wed, Jul 20, 2016 at 06:37:07PM +0300, Thomas Backlund wrote:
>
> Yeah, but that patch seem to be heading to 4.8 only , so qat build
> in upcoming 4.7 still breaks...
>
> and pulling that fix only to 4.7 breaks too, so I guess more fixes
> would be needed for proper backport then...
>
> or are
From: Vivien Didelot
Date: Wed, 20 Jul 2016 18:18:33 -0400
> Some switches can access an optional external EEPROM via its registers.
>
> The 88E6352 family of switches have 8-bit address / 16-bit data access.
> The new 88E6390 family has 16-bit address / 8-bit data access.
>
> This patchset cle
Hi, Bibby:
On Thu, 2016-07-21 at 11:21 +0800, Bibby Hsieh wrote:
> Hi, CK
>
> I'm appreciate your comments.
>
>
[snip...]
> > >
> > > @@ -469,7 +484,7 @@ void mtk_crtc_ddp_irq(struct drm_crtc *crtc, struct
> > > mtk_ddp_comp *ovl)
> > > if (state->pending_config) {
> > > mtk_dd
From: Andy Green
Currently the k3dma driver doesn't offer the cyclic mode
necessary for handling audio.
This patch adds it.
Cc: Zhangfei Gao
Cc: Jingoo Han
Cc: Krzysztof Kozlowski
Cc: Maxime Ripard
Cc: Vinod Koul
Cc: Dan Williams
Cc: Mark Brown
Cc: Andy Green
Acked-by: Zhangfei Gao
Sig
From: Andy Green
As it was before, as soon as the DMAC IP felt there was an error
he would return IRQ_NONE since no actual transfer had completed.
After spinning on that for 100K interrupts, Linux yanks the IRQ with
a "nobody cared" error.
This patch lets it handle the interrupt and keep the IR
From: Andy Green
The offsets for ERR1 and ERR2 are wrong actually.
That's why you can never clear an error.
Cc: Zhangfei Gao
Cc: Jingoo Han
Cc: Krzysztof Kozlowski
Cc: Maxime Ripard
Cc: Vinod Koul
Cc: Dan Williams
Cc: Mark Brown
Cc: Andy Green
Acked-by: Zhangfei Gao
Signed-off-by: Andy
With cyclic mode, the shared virt-dma logic doesn't actually
manage the descriptor state, nor the calling of the descriptor
free callback. This results in leaking a desc structure every
time we start an audio transfer.
Thus we must manage it ourselves. The k3dma driver already keeps
track of the a
Per Mark's suggestion, I've split out the k3dma changes
on their own as they are mostly fixes and the addition
of cyclic mode.
New in v3:
* With inspiration from YongQin Liu, I figured out the reason we
were seeing occasional DMA ERR issues: The desc structures were
being allocated with kzalloc an
From: Andy Green
Max burst len is a 4-bit field, but at the moment it's clipped with
a 5-bit constant... reduce it to that which can be expressed
Cc: Zhangfei Gao
Cc: Jingoo Han
Cc: Krzysztof Kozlowski
Cc: Maxime Ripard
Cc: Vinod Koul
Cc: Dan Williams
Cc: Mark Brown
Cc: Andy Green
Acked-
This allows the k3dma driver to be selected on HiKey via the ARCH_HISI
dependency.
Cc: Zhangfei Gao
Cc: Jingoo Han
Cc: Krzysztof Kozlowski
Cc: Maxime Ripard
Cc: Vinod Koul
Cc: Dan Williams
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Wei Xu
Cc: Rob Herring
After lots of debugging on an occasional DMA ERR issue, I realized
that the desc structures which we point the dma hardware are being
allocated out of regular memory. This means when we fill the desc
structures, that data doesn't always get flushed out to memory by
the time we start the dma transfe
On 07/20/2016 03:31 AM, Enric Balletbo i Serra wrote:
This patch adds and entry to the sysfs to start firmware upload process
on the specified device with the requested firmware.
The uploading of the firmware needs only to happen once per firmware
upgrade, as the firmware is stored in persistent
This patch implements moving a range of data blocks from source file to
destination file.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 9
fs/f2fs/file.c | 132 +
2 files changed, 141 insertions(+)
diff --git a/fs/f2fs/f2fs.h b/fs
It's enough to show BUG or WARN by f2fs_bug_on for error case.
Then, we don't need to remain corrupted filesystem.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/recovery.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index 5d4461f..9e652d5 100644
--- a/f
When fs utilization is almost full, f2fs_sync_file should do checkpoint if
there is not enough space for roll-forward later. (i.e. space_for_roll_forward)
So, currently we have no lock for sbi->alloc_valid_block_count, resulting in
race condition.
In rare case, we can get -ENOSPC when doing roll-f
On 07/07/2016 12:48 PM, Tahsin Erdogan wrote:
Before merging a bio into an existing request, io scheduler is called to
get its approval first. However, the requests that come from a plug
flush may get merged by block layer without consulting with io
scheduler.
In case of CFQ, this can cause fair
Hi all,
Today's linux-next merge of the device-mapper tree got a conflict in:
drivers/md/dm.c
between commit:
4cc96131afce ("dm: move request-based code out to dm-rq.[hc]")
from the block tree and commit:
70246286e94c ("block: get rid of bio_rw and READA")
from the device-mapper tree.
Hi, CK
I'm appreciate your comments.
On Fri, 2016-07-15 at 17:11 +0800, CK Hu wrote:
> Hi, Bibby:
>
> Some comments inline.
>
> On Thu, 2016-07-07 at 15:37 +0800, Bibby Hsieh wrote:
> > Apply gamma function to correct brightness values.
> > It applies arbitrary mapping curve to compensate the
>
Hi, CK
I'm appreciate your comments.
On Mon, 2016-07-18 at 10:33 +0800, CK Hu wrote:
> Hi, Bibby:
>
> Some comments inline.
>
> On Thu, 2016-07-07 at 15:37 +0800, Bibby Hsieh wrote:
> > Some panels only accept bpc (bit per color) 6-bit.
> > But, the default bpc in mt8173 display data path is 8
At preset, when creating module's map, perf gets 'start' address by parsing
'/proc/modules', but it's module base address, isn't the start address of
'.text' section. In most archs, it's OK. But for s390, it places 'GOT' and
'PLT' relocations before '.text' section. So there exists an offset betwee
Change log:
>From V3:
1.move fixup function to tools/perf/arch/s390/util/machine.c;
2. Add acked-by info from Jiri Olsa ;
>From V2:
1. remove redundancy string 'module_name';
>From V1:
1.change func name from 'fix__arch_module_baseaddr' to
'fix__arch_module_text_start';
2.Parse '.text' start add
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
block/blk-lib.c
between commit:
05bd92dddc59 ("block: missing bio_put following submit_bio_wait")
from Linus' tree and commit:
4e49ea4a3d27 ("block/fs/drivers: remove rw argument from submit_bio")
from the block tre
On 07/20/2016 06:01 PM, Mike Snitzer wrote:
On Wed, Jul 13 2016 at 11:03am -0400,
Kani, Toshimitsu wrote:
On Tue, 2016-07-12 at 22:01 -0400, Mike Snitzer wrote:
On Tue, Jul 12 2016 at 6:22pm -0400,
Kani, Toshimitsu wrote:
On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
:
Thanks
Hi Doug,
On 2016/7/21 5:33, Doug Anderson wrote:
Hi,
On Tue, Jul 19, 2016 at 12:28 AM, Frank Wang wrote:
You need a patch description here, even for simple patches. All you
have now is a subject.
OK, I will describe it next version.
Signed-off-by: Frank Wang
---
arch/arm64/boot/dts/r
Hi Kees,
Today's linux-next merge of the kspp tree got a conflict in:
arch/arm64/include/asm/uaccess.h
between commit:
bffe1baff5d5 ("arm64: kasan: instrument user memory access API")
from the arm64 tree and commit:
aac380fe78b1 ("arm64/uaccess: Enable hardened usercopy")
from the kspp
Le 20/07/2016 à 17:35, Andrew Lunn a écrit :
> On Wed, Jul 20, 2016 at 06:26:41PM -0400, Vivien Didelot wrote:
>> This patch simply moves the legacy DSA code from dsa.c to legacy.c,
>> except the few shared symbols which remain in dsa.c.
>
> I think it is a bit early for this. Lets convert all in
We are trying to test the patchset on x86 and are getting strange
backtraces and aborts. It seems that the cpu before the cpu we are running
on creates an irq_work event that causes a latency event on the next cpu.
This is weird. Is there a new round robin IPI feature in the kernel that I
am not a
On 2016/7/21 5:36, Dave Hansen wrote:
On 07/19/2016 09:18 PM, Zhou Chengming wrote:
When CONFIG_SPARSEMEM_EXTREME is disabled, __section_nr can get
the section number with a subtraction directly.
Does this actually *do* anything?
It was a long time ago, but if I remember correctly, the entire
Prefix the sector number being cleared with a '0x' to make it clear that
this is a hex value.
Signed-off-by: Vishal Verma
---
drivers/nvdimm/pmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
index 608fc44..08ac2cb 100644
---
Normally, an ARS (Address Range Scrub) only happens at
boot/initialization time. There can however arise situations where a
bus-wide rescan is needed - notably, in the case of discovering a latent
media error, we should do a full rescan to figure out what other sectors
are bad, and thus potentially
When a latent (unknown to 'badblocks') error is encountered, it will
trigger a machine check exception. On a system with machine check
recovery, this will only SIGBUS the process(es) which had the bad page
mapped (as opposed to a kernel panic on platforms without machine
check recovery features). I
Changes in v2:
- Rework the ars_done flag in nfit_spa to be ars_required, and reuse it for
rescanning (Dan)
- Rename the ars_rescan attribute to simply 'scrub', and move into the nfit
group since only nfit buses have this capability (Dan)
- Make the scrub attribute RW, and on reads return the n
On Wed, Jul 20, 2016 at 07:48:13PM -0500, Christoph Lameter wrote:
> On Wed, 20 Jul 2016, Waiman Long wrote:
>
> > Christoph, are you OK with Tejun's request to revert the name back to
> > percpu_list? Or do you still think the current name is better?
>
> The percpu structure contains a spinlock
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx4/en_ethtool.c
between commit:
ec25bc04ed8e ("net/mlx4_en: Add resilience in low memory systems")
from the net tree and commit:
9ecc2d86171a ("net/mlx4_en: add xdp forwarding and da
On 07/20/2016 08:48 PM, Christoph Lameter wrote:
On Wed, 20 Jul 2016, Waiman Long wrote:
Christoph, are you OK with Tejun's request to revert the name back to
percpu_list? Or do you still think the current name is better?
The percpu structure contains a spinlock and may be remotely accessed? Y
On Thu, Jul 21, 2016 at 11:07:56AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the xfs tree got a conflict in:
>
> fs/xfs/xfs_ioctl.c
>
> between commit:
>
> 3e0a39654645 ("xfs: fix type confusion in xfs_ioc_swapext")
>
> from Linus' tree and commit:
>
> 7f1
Under some conditions, my Dell XPS 13 9350 puts the EBDA at 0x2c000
but reports the lowmem cutoff as 0. The old code reserves
everything above 0x2c000 and I can't boot [1].
Due to an old quirk, we assume that lowmem ends at 0x9f000. Nonetheless,
the old code would reserve everything from 0x2c000
Hi Arnd,
2016-07-19 1:00 GMT+09:00 Arnd Bergmann :
> Using "make tinyconfig" produces a couple of annoying warnings that show up
> for build test machines all the time:
>
> .config:966:warning: override: NOHIGHMEM changes choice state
> .config:965:warning: override: SLOB changes choice s
Set default config values for 'colors' section with 'colors_config_items[]'
instead of actual const char * type values.
(e.g. using colors_config_item[CONFIG_COLORS_TOP].value.s
instead of "red, default" string value for 'colors.top')
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Wang
To easily set default config values into actual variables for 'colors' config,
it would be better that actual variables for each 'colors' config
also have only one value like 'default_config_item' type.
If we use combined {fore,back}ground colors values in ui_browser_colorset,
it smoothly work to
Set default config values for 'annotate' section with 'annotate_config_items[]'
instead of actual bool type values.
(e.g. using annotate_config_items[CONFIG_ANNOTATE_USE_OFFSET].value.b
instead of 'true' bool type value for 'annotate.use_offset'.)
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hirama
An example result for data dependent write has a typo. This commit
fixes the wrong typo.
Signed-off-by: SeongJae Park
---
Documentation/memory-barriers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/memory-barriers.txt
b/Documentation/memory-barriers.txt
This patchset adds a Korean translation of memory-barriers.txt and fix a typo
that was found during the translation. The translation has started from Feb,
2016 and using a public git tree[1] to manage the work. It's commit history
says that it is following upstream changes as well.
Changes from
On Wed, 2016-07-20 at 14:09 -0500, Rob Herring wrote:
> On Wed, Jul 20, 2016 at 03:28:28PM +0930, Andrew Jeffery wrote:
> >
> > Signed-off-by: Andrew Jeffery
> > ---
> > Documentation/devicetree/bindings/mfd/aspeed-scu.txt | 16
> > 1 file changed, 16 insertions(+)
> > create m
Actual variable for configs of 'annotate' section is like below.
(at ui/browsers/annoate.c)
static struct annotate_browser_opt {
bool hide_src_code,
use_offset,
jump_arrows,
show_linenr,
show_nr_jumps,
show_total_period;
} an
In near future, default_config_item arrays will be added
(e.g. const struct default_config_item colors_config_items[])
To simply assign config key-value pairs to default_config_item,
add macros that are CONF_VAR() and CONF_*_VAR() for each type.
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Wang Nan
Cc: M
When initializing default perf config values,
we currently use values of actual type(int, bool, char *, etc.).
For example,
If there isn't user config value at ~/.perfconfig
for 'annotate.use_offset' config variable,
default value for it is 'true' bool type value in perf like below.
At ui/browser
Hello, :)
When initializing default perf config values,
we currently use values of actual type(int, bool, char *, etc.).
But I suggest using default config key-value pairs arrays.
For example,
If there isn't user config value at ~/.perfconfig for 'annotate.use_offset'
config variable,
default va
Actual variable for configs of 'colors' section is like below.
(at ui/browser.c)
static struct ui_browser_colorset {
const char *name, *fg, *bg;
int colorset;
} ui_browser__colorsets[] = {
{
.colorset = HE_COLORSET_TOP,
.name = "top",
Hi Sean,
> > + int ret;
> > + struct ir_spi_data *idata = (struct ir_spi_data *) dev->priv;
>
> No cast needed.
yes, thanks.
> > + ret = regulator_enable(idata->regulator);
> > + if (ret)
> > + return ret;
> > +
> > + mutex_lock(&idata->mutex);
> > + idata->xfer.len = n;
>
Hi all,
Today's linux-next merge of the xfs tree got a conflict in:
fs/xfs/xfs_ioctl.c
between commit:
3e0a39654645 ("xfs: fix type confusion in xfs_ioc_swapext")
from Linus' tree and commit:
7f1b62457b58 ("xfs: fix type confusion in xfs_ioc_swapext")
from the xfs tree.
These are not
The ramoops can be configured to enable each pstore type by setting
their size. In that case, it'd be better not to register disabled types
in the first place.
Signed-off-by: Namhyung Kim
---
fs/pstore/ram.c| 8 +++-
include/linux/pstore.h | 2 --
2 files changed, 7 insertions(+), 3
This patch adds new PSTORE_FLAGS for each pstore type so that they can
be enabled separately. This is a preparation for ongoing virtio-pstore
work to support those types flexibly.
The PSTORE_FLAGS_FRAGILE is changed to PSTORE_FLAGS_DMESG to preserve the
original behavior.
Cc: "Rafael J. Wysocki"
2016-07-20 19:58 GMT+09:00 Geert Uytterhoeven :
> On Sat, Jul 16, 2016 at 6:57 AM, Masahiro Yamada
> wrote:
>> 2016-07-16 11:11 GMT+09:00 Michael Turquette :
>>> Quoting Masahiro Yamada (2016-05-05 00:57:17)
Several SoCs implement platform drivers for clocks rather than
CLK_OF_DECLARE().
On Fri, May 20, 2016 at 02:27:05PM +0200, Samuel Thibault wrote:
> Muhammad Falak R Wani, on Fri 20 May 2016 17:53:28 +0530, wrote:
> > Use memdup_user to duplicate a memory region from user-space to
> > kernel-space, instead of open coding using kmalloc & copy_from_user.
> >
> > Signed-off-by: Mu
Hi Sean,
> > Raw transmitters receive the data which need to be sent to
> > receivers from userspace as stream of bits, they don't require
> > any handling from the lirc framework.
>
> No drivers of type RC_DRIVER_IR_RAW_TX should handle tx just like any
> other device, so data should be provided
On Wed, 20 Jul 2016, Waiman Long wrote:
> Christoph, are you OK with Tejun's request to revert the name back to
> percpu_list? Or do you still think the current name is better?
The percpu structure contains a spinlock and may be remotely accessed? You
are aware that other percpu variables that sh
On Wed, Jul 20, 2016 at 06:18:36PM -0400, Vivien Didelot wrote:
> Get rid of the last usage of the locked mv88e6xxx_reg_read function with
> a new mv88e6xxx_port_read helper, useful later for chips with different
> port registers base address.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andre
Hi Sean,
> > + if (dev->driver_type == RC_DRIVER_IR_RAW ||
> > + dev->driver_type == RC_DRIVER_IR_RAW_TX) {
>
> Here the if is wrong. It should be
> "if (dev->driver_type != RC_DRIVER_IR_RAW_TX)". Note that as result
> the decoder thread is not started, so patch 4 won
On Wed, Jul 20, 2016 at 06:18:35PM -0400, Vivien Didelot wrote:
> The 6352 family of switches and compatibles provide a 8-bit address and
> 16-bit data access to an optional EEPROM.
>
> Newer chip such as the 6390 family slightly changed the access to 16-bit
> address and 8-bit data.
>
> This com
1 - 100 of 647 matches
Mail list logo
