From: Omar Sandoval
Again, there's no point in passing this in every time. Make it part of
`struct scale_bitmap_queue` and clean up the API.
Signed-off-by: Omar Sandoval
---
block/blk-mq-tag.c | 33 +++--
block/blk-mq-tag.h | 1 -
include/linux/
From: Omar Sandoval
In order to get good cache behavior from a scale_bitmap, we want each
CPU to stick to its own cacheline(s) as much as possible. This might
happen naturally as the bitmap gets filled up and the last_cache values
spread out, but we really want this behavior from the start. blk-m
From: Omar Sandoval
The original `bt_alloc()` we converted from was using `kzalloc()`, not
`kzalloc_node()`, to allocate the wait queues. This was probably an
oversight, so fix it for `scale_bitmap_queue_init_node()`.
Signed-off-by: Omar Sandoval
---
lib/scale_bitmap.c | 2 +-
1 file changed,
From: Omar Sandoval
This is a generally useful data structure, so make it available to
anyone else who might want to use it. It's also a nice cleanup
separating the allocation logic from the rest of the tag handling logic.
The code is behind a new Kconfig option, CONFIG_SCALE_BITMAP, which is
on
On 9/7/16 4:46 PM, Omar Sandoval wrote:
From: Omar Sandoval
This is a generally useful data structure, so make it available to
anyone else who might want to use it. It's also a nice cleanup
separating the allocation logic from the rest of the tag handling logic.
The code is behind a new Kconfi
On 09/07/2016 05:15 AM, Andy Shevchenko wrote:
On Tue, 2016-09-06 at 18:04 -0700, Kuppuswamy Sathyanarayanan wrote:
According to the intel_mid_sfi_get_pdata() function definition,
get_platform_data() function should returns NULL on no platform
data scenario and return ERR_PTR on platform data
According to the intel_mid_sfi_get_pdata() function definition,
get_platform_data() function should returns NULL on no platform
data scenario and return ERR_PTR on platform data initialization
failures. But current device platform initialization code does not
follow this requirement. This patch fix
Hi Bjorn,
On 8/30/2016 10:04 AM, Ray Jui wrote:
On 8/30/2016 10:00 AM, Bjorn Helgaas wrote:
On Tue, Aug 30, 2016 at 09:36:52AM -0700, Ray Jui wrote:
On 8/30/2016 6:37 AM, Bjorn Helgaas wrote:
On Mon, Aug 29, 2016 at 05:37:09PM -0700, Ray Jui wrote:
Hi Bjorn,
On 8/24/2016 10:54 AM, Bjorn
Hi
My fpga device has multiple msi interrupts and I am trying to create an
uio device for each msi interrupt. In the probe function of the pci
device, I enable MSI for the pci device and allocate mem for uio info
structures ( one for each msi ). First uio-info->irq is equal to the irq
number
On 09/07/2016 12:37 PM, Arnd Bergmann wrote:
On Wednesday, September 7, 2016 11:49:59 AM CEST Laura Abbott wrote:
- if (dir & _IOC_WRITE)
- if (copy_from_user(&data, (void __user *)arg, _IOC_SIZE(cmd)))
- return -EFAULT;
+ /*
+* The copy_f
On Wed, Sep 07, 2016 at 09:35:30PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/9/2 4:46, Jaegeuk Kim wrote:
> > Fix wrong condition check for defragmentation of a file.
> >
> > Signed-off-by: Jaegeuk Kim
> > ---
> > fs/f2fs/file.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
On 2016-09-07 07:22 PM, Kees Cook wrote:
On Mon, Sep 5, 2016 at 1:14 PM, wrote:
From: Robert Foss
Fixed a -> an typo.
Signed-off-by: Robert Foss
Acked-by: Kees Cook
This could be taken directly into the docs tree, I think -- no reason
to make it depend on the rest of the series.
Ag
ged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-rewrite-20160907-1
Pulled.
On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki wrote:
> Please let me know what you think and if you can run some benchmarks you
> care about and see if the changes make any difference (this way or another),
> please do that and let me know what you've found.
LGTM (I just reviewed the
From: David Howells
Date: Wed, 07 Sep 2016 16:25:50 +0100
>
> Here's a patch that adds a tracepoint that allows local aborts to be
> debugged. This needs to be applied on top of the just-posted call refcount
> overhaul patch.
>
> The patches can be found here also:
>
>
> http://git.ker
On Wed, Sep 07, 2016 at 10:12:17PM +0800, Chao Yu wrote:
> On 2016/9/3 2:36, Jaegeuk Kim wrote:
> > On Fri, Sep 02, 2016 at 03:33:33PM +0800, Chao Yu wrote:
> >> Hi Jaegeuk,
> >>
> >> On 2016/8/27 8:53, Jaegeuk Kim wrote:
> >>> This can avoid bio splits due to different op_flags.
> >>
> >> I though
On Wed, Sep 07, 2016 at 04:44:58PM -0700, Stephen Boyd wrote:
> Quoting David Gibson (2016-08-30 16:55:23)
> > On Mon, Aug 29, 2016 at 07:07:49PM -0700, Stephen Boyd wrote:
> > > Quoting David Gibson (2016-08-29 06:45:11)
> > > > So, combining those thoughts together, I'm thinking dtc format for
>
2016-08-31 10:16 GMT+09:00 Joe Perches :
> On Wed, 2016-08-31 at 08:57 +0900, Masahiro Yamada wrote:
>> Spelling corrections for (among other things):
>> * according
> []
>> * width
>
> When possible and appropriate, can you please
> update scripts/spelling.txt too?
>
> Thanks, Joe
Hi Joe,
Y
On Wednesday, September 07, 2016 05:22:26 PM Steve Muckle wrote:
> On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki wrote:
> > Please let me know what you think and if you can run some benchmarks you
> > care about and see if the changes make any difference (this way or another),
> > ple
On Wed, 2016-09-07 at 17:22 -0700, Steve Muckle wrote:
> On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki wrote:
> >
> > Please let me know what you think and if you can run some
> > benchmarks you
> > care about and see if the changes make any difference (this way or
> > another),
> >
From: Hayes Wang
Date: Wed, 7 Sep 2016 16:12:19 +0800
> Some people prefer to use ECM mode rather than vendor mode. Therefore, I add
> CONFIG_RTL8152_CONFIG_VALUE in Kconfig. Then, the users could choose the USB
> configuration value which they want. The default is to support vendor mode
> only.
On Wednesday, September 07, 2016 05:35:50 PM Srinivas Pandruvada wrote:
> On Wed, 2016-09-07 at 17:22 -0700, Steve Muckle wrote:
> > On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki wrote:
> > >
> > > Please let me know what you think and if you can run some
> > > benchmarks you
> > > c
On Wed, Sep 07, 2016 at 05:01:56PM -0700, Alexei Starovoitov wrote:
> On 9/7/16 4:46 PM, Omar Sandoval wrote:
> > From: Omar Sandoval
> >
> > This is a generally useful data structure, so make it available to
> > anyone else who might want to use it. It's also a nice cleanup
> > separating the al
From: Baoyou Xie
Date: Wed, 7 Sep 2016 19:07:00 +0800
> We get 4 warnings when building kernel with W=1:
> drivers/net/ethernet/qlogic/qed/qed_selftest.c:6:5: warning: no previous
> prototype for 'qed_selftest_memory' [-Wmissing-prototypes]
> drivers/net/ethernet/qlogic/qed/qed_selftest.c:19:5:
xhci_setup_device() should return failure with correct error number
when xhci host has died, removed or halted.
Cc: sta...@vger.kernel.org # 4.3+
Signed-off-by: Lu Baolu
---
v1->v2:
- fix email mismatch issue
drivers/usb/host/xhci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
di
From: Yuval Mintz
Date: Wed, 7 Sep 2016 11:55:34 +
>> We get a few warnings when building kernel with W=1:
>> drivers/net/ethernet/qlogic/qed/qed_l2.c:112:5: warning: no previous
>> prototype for 'qed_sp_vport_start' [-Wmissing-prototypes]
>>
>>
>> In fact, these functions are only used
Hi Randy,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.8-rc5 next-20160907]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to rec
On Thu, 2016-09-08 at 02:44 +0200, Rafael J. Wysocki wrote:
> On Wednesday, September 07, 2016 05:35:50 PM Srinivas Pandruvada
> wrote:
> >
> > On Wed, 2016-09-07 at 17:22 -0700, Steve Muckle wrote:
> > >
> > > On Sat, Sep 03, 2016 at 02:56:48AM +0200, Rafael J. Wysocki
> > > wrote:
> > > >
> >
Hi Jacek,
Thank you very much for review.
> -Original Message-
> From: Jacek Anaszewski [mailto:jacek.anaszew...@gmail.com]
> Sent: Wednesday, September 07, 2016 11:21 PM
> To: Vadim Pasternak ; rpur...@rpsys.net;
> j.anaszew...@samsung.com
> Cc: d...@treblig.org; linux-l...@vger.kernel.o
Check for snd_pcm_ops structures that are only stored in the ops field of a
snd_soc_platform_driver structure or passed as the third argument to
snd_pcm_set_ops. The corresponding field or parameter is declared const,
so snd_pcm_ops structures that have this property can be declared as const
also.
On Wed, Sep 7, 2016 at 4:34 PM, Stephen Boyd wrote:
> In the case of ULPI devices, we want to be able to load the
> driver before registering the device so that we don't get stuck
> in a loop waiting for the phy module to appear and failing usb
> controller probe. Currently we request the ulpi mod
On Wed, Sep 7, 2016 at 4:34 PM, Stephen Boyd wrote:
> The ULPI bus can be built as a module, and it will soon be
> calling these functions when it supports probing devices from DT.
> Export them so they can be used by the ULPI module.
>
> Cc: Rob Herring
> Cc:
> Signed-off-by: Stephen Boyd
> --
+++ Petr Mladek [07/09/16 15:13 +0200]:
The commit 66cc69e34e86a231 ("Fix: module signature vs tracepoints:
add new TAINT_UNSIGNED_MODULE") updated module_taint_flags() to
potentially print one more character. But it did not increase the
size of the corresponding buffers in m_show() and print_mod
On Wed, 2016-09-07 at 16:38 +0200, Linus Walleij wrote:
> On Tue, Aug 30, 2016 at 9:54 AM, Andrew Jeffery wrote:
>
> >
> > Signed-off-by: Andrew Jeffery
> > Acked-by: Rob Herring
> > Acked-by: Joel Stanley
> Acked-by: Linus Walleij
>
> I guess the MFD maintainer (Lee Jones) should merge thi
Check for snd_pcm_ops structures that are only stored in the ops field of a
snd_soc_platform_driver structure or passed as the third argument to
snd_pcm_set_ops. The corresponding field or parameter is declared const,
so snd_pcm_ops structures that have this property can be declared as const
also.
On Wed, 2016-09-07 at 17:30 +0100, Lee Jones wrote:
> On Wed, 07 Sep 2016, Linus Walleij wrote:
>
> >
> > On Tue, Aug 30, 2016 at 9:54 AM, Andrew Jeffery wrote:
> >
> > >
> > > Signed-off-by: Andrew Jeffery
> > > Acked-by: Rob Herring
> > > Acked-by: Joel Stanley
> > Acked-by: Linus Walleij
On Tue, Aug 16, 2016 at 11:22:01PM +0900, Seung-Woo Kim wrote:
> From pwm_samsung_calc_tin(), there is routine to find the lowest
> divider possible to generate lower frequency than requested one.
> But it is always possible to generate requested frequency with
> large enough modulation bits except
On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha
>
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes care of
> enab
On Wednesday, September 07, 2016 05:49:31 PM Srinivas Pandruvada wrote:
> On Thu, 2016-09-08 at 02:44 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, September 07, 2016 05:35:50 PM Srinivas Pandruvada
> > wrote:
> > >
> > > On Wed, 2016-09-07 at 17:22 -0700, Steve Muckle wrote:
> > > >
> > > >
On Wed, Sep 7, 2016 at 4:35 PM, Stephen Boyd wrote:
> The qcom HSIC ULPI phy doesn't have any bits set in the vendor or
> product ID registers. This makes it impossible to make a ULPI
> driver match against the ID registers. Add support to discover
> the ULPI phys via DT help alleviate this proble
On 9/7/16 5:38 PM, Omar Sandoval wrote:
On Wed, Sep 07, 2016 at 05:01:56PM -0700, Alexei Starovoitov wrote:
On 9/7/16 4:46 PM, Omar Sandoval wrote:
From: Omar Sandoval
This is a generally useful data structure, so make it available to
anyone else who might want to use it. It's also a nice cle
On Wed, Sep 07, 2016 at 05:24:08PM +0200, Arnd Bergmann wrote:
> On Wednesday, September 7, 2016 1:24:07 PM CEST Felipe Balbi wrote:
> >
> > Hi,
> >
> > Arnd Bergmann writes:
> >
> > [...]
> >
> > > Regarding the DMA configuration that you mention in ci_hdrc_add_device(),
> > > I think we shou
Check for snd_pcm_ops structures that are only stored in the ops field of a
snd_soc_platform_driver structure or passed as the third argument to
snd_pcm_set_ops. The corresponding field or parameter is declared const,
so snd_pcm_ops structures that have this property can be declared as const
also.
Check for snd_pcm_ops structures that are only stored in the ops field of a
snd_soc_platform_driver structure or passed as the third argument to
snd_pcm_set_ops. The corresponding field or parameter is declared const,
so snd_pcm_ops structures that have this property can be declared as const
also.
On Wed, 2016-09-07 at 16:43 +0200, Linus Walleij wrote:
> On Tue, Aug 30, 2016 at 9:54 AM, Andrew Jeffery wrote:
>
> >
> > Signed-off-by: Andrew Jeffery
> > Acked-by: Joel Stanley
> Patch applied to the GPIO tree with Rob's ACK and moved the compatible
> to the first line in the process.
Than
On Wed, Sep 07, 2016 at 02:35:07PM -0700, Stephen Boyd wrote:
> The two extcon notifiers are almost the same except for the
> variable name for the cable structure and the id notifier inverts
> the cable->state logic. Make it the same and replace two
> functions with one to save some lines. This al
The DMA_SG is still a type of memory copy operation that should
conform the hardware restriction. So this patch just applies the
copy_align to DMA_SG as well.
Signed-off-by: Nicolin Chen
---
drivers/dma/dmatest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/dma
On 04/09/2016 18:12, Peter Meerwald-Stadler wrote:
>
>> The Allwinner SoCs all have an ADC that can also act as a touchscreen
>> controller and a thermal sensor. This patch adds the ADC driver which is
>> based on the MFD for the same SoCs ADC.
>
> nitpicking ahead
>
[...]
>> diff --git a/drive
Hello Minchan,
sorry, I don't have enough time at the moment to review it in details
due to some urgent issues I'm working on. can this wait?
I was looking at loop.c awhile ago and was considering to do something
similar to what they have done; but it never happened.
I'm a bit 'surprised' tha
On Wed, Sep 07, 2016 at 10:45:06AM +0200, Daniel Wagner wrote:
> From: Daniel Wagner
>
> The firmware user helper code tracks the current state of the loading
> process via unsigned long status and a complection in struct
> firmware_buf. We only need this for the usermode helper as such we can
>
Hi Jens and Tejun,
The command line was in the original email:
$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
And agree, in general it'd be nice if there was a link to the image as
well, so that folks can reproduce.
Yes we have a reproduce script internally, however need to polish it
On Wed, Sep 07, 2016 at 10:45:07AM +0200, Daniel Wagner wrote:
> From: Daniel Wagner
>
> We track the state of the loading with bit ops. Since the state machine
> has only a couple of states and there are only a few simple state
> transition
And they are all mutually exclusive ?
> we can model
On 2016-09-01 15:27, Bjorn Andersson wrote:
Make it possible to match rpmsg devices based on device tree node, in
addition to the id table. In some of these cases the rpmsg driver would
not have a id_table, so make this optional.
Signed-off-by: Bjorn Andersson
---
Changes since v1:
- None
dr
On 2016-09-01 15:27, Bjorn Andersson wrote:
By basing rpmsg device names on channel id we end up with human
readable
device names in sysfs and debug logs.
Signed-off-by: Bjorn Andersson
---
Changes since v1:
- None
drivers/rpmsg/virtio_rpmsg_bus.c | 12 ++--
1 file changed, 2 insert
On Tue, Jul 26, 2016 at 11:22:13AM -0700, Brian Norris wrote:
> While the particular usage in question is likely safe (struct
> cros_ec_command is 32-bit aligned, followed by <=32-bit fields), it's
> been suggested this is not a great pattern to follow for the general
> case -- for example, if we f
On Thu, Sep 8, 2016 at 5:34 AM, Stephen Boyd wrote:
> The state of USB ChipIdea support on Qualcomm's platforms is not great.
> The DT description of these devices requires up to three different nodes
> for what amounts to be the same hardware block, when there should really
> only be one. Further
On 09/08, Fengguang Wu wrote:
>Hi Jens and Tejun,
>
>>The command line was in the original email:
>>
>>$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
>>
>>And agree, in general it'd be nice if there was a link to the image as
>>well, so that folks can reproduce.
>
>Yes we have a reproduce s
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/intel_pm.c
between commit:
9909113cc48a ("drm/i915/gen9: Only copy WM results for changed pipes to
skl_hw")
from Linus' tree and commits:
2722efb90b34 ("drm/i915/gen9: Only copy WM results fo
On Wed, 7 Sep 2016 10:12:14 -0400
David Long wrote:
> On 09/07/2016 01:52 AM, Masami Hiramatsu wrote:
> > On Tue, 6 Sep 2016 13:54:59 -0400
> > David Long wrote:
> >
> >> From: "David A. Long"
> >>
> >> Kprobes searches backwards a finite number of instructions to determine if
> >> there is an
Hi Gautham,
Thanks for fixing this.
On Wed, Sep 7, 2016 at 1:16 AM, Gautham R. Shenoy
wrote:
> From: "Gautham R. Shenoy"
>
> pnv_wakeup_tb_loss function currently expects the cr4 to be "eq" if
> the CPU is waking up from a complete hypervisor state loss. Hence, it
> currently restores the SPR c
If the FTM counter reaches the FTM_MOD value between the reading of the
TOF bit and the writing of 0 to the TOF bit, the process of clearing the
TOF bit does not work as expected when FTMx_CONF[NUMTOF] != 0 and the
current TOF count is less than FTMx_CONF[NUMTOF]. If the above condition
is met, the
Oled, thank you for moving this patch on.
on 09/07/2016 08:35 PM, Oleg Nesterov wrote:
> On 09/07, chengchao wrote:
>>
>> Oleg, thank you very much.
>>
>> on 09/06/2016 11:22 PM, Oleg Nesterov wrote:
>>> On 09/06, chengchao wrote:
the key point is for CONFIG_PREEMPT_NONE=y,
...
Thanks for looking into this.
I have tested that it compiles and passes checks (C=2) cleanly after
this patch.
Acked-by: Andrey Utkin
While we're at it, what about constification of
*-core.c:static struct pci_driver *_pci_driver = {
*-video.c:static struct vb2_ops *_video_qops = {
*-video.c:sta
Heiko,
On 05.09.2016 08:35, Heiko Schocher wrote:
> I think yes ...
>
>> Is this part of a tree-wide cleanup?
>
> Yes, and I thought it is worth to change this part in linux too.
Agreed. Can you please resend with a proper change log and (more important)
a correct sob-chain? From: and first Sig
Sorry, +Cc f2fs & kernel mailing list.
On 2016/9/8 10:27, Chao Yu wrote:
> Update my maintainership of f2fs to maintainer instead of reviewer.
>
> Signed-off-by: Chao Yu
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> ind
On Mon, Sep 05, 2016 at 06:01:29PM +0800, shh@gmail.com wrote:
> From: Shaohui Xie
>
> SCFG and DCFG are SoC-specific devices can be found on SoCs like LS1021A,
> LS1043A and LS1046A, this patch updates bindings for SCFG and DCFG to
> reflect more SoCs.
>
> Signed-off-by: Shaohui Xie
> ---
Hello,
On Tue, Sep 06, 2016 at 10:22:20AM +0200, Andreas Mohr wrote:
> On Tue, Sep 06, 2016 at 04:24:17PM +0900, Minchan Kim wrote:
> > @@ -1464,6 +1908,9 @@ static int __init zram_init(void)
> > num_devices--;
> > }
> >
> > + if (create_workers())
> > + goto out_erro
In dwc2_hsotg_udc_start(), don't initialize the controller for device
mode unless we are actually in device mode.
Tested-by: Heiko Stuebner
Tested-by: Stefan Wahren
Signed-off-by: John Youn
---
drivers/usb/dwc2/gadget.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a
Add a delay to the core soft reset function to account for the IDDIG
debounce filter.
If the current mode is host, either due to the force mode bit being
set (which persists after core reset) or the connector id pin, a core
soft reset will temporarily reset the mode to device and a delay from
the
When a force mode bit is set and the IDDIG debounce filter is enabled,
there is a delay for the forced mode to take effect. This delay is due
to the IDDIG debounce filter and is variable depending on the platform's
PHY clock speed. To account for this delay we can poll for the expected
mode.
On a
This series accounts for the delay from the IDDIG debounce filter when
switching modes. This delay is a function of the PHY clock speed and
can range from 5-50 ms. This delay must be taken into account on core
reset and force modes. A full explanation is provided in the patch
commit log and code co
The patch (commit id: a0a6e06d545a753740c9d8d5ce2c4fdd3ab1c021) adding
tracepoints for alarmtimers will build failed on S390 platform, due to
S390 defconfig did not define CONFIG_RTC_LIB macro to define the
rtc_ktime_to_tm() function which is used in this patch. Thus we should
add dummy static inli
Hi, Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git for-rc
to receive the latest Thermal Management updates for v4.8-rc6 with
top-most commit 87260d3f7aecba9a5fadc6886c338b2a8fccfca9:
thermal: rcar_thermal: Fix priv->zone error handling (2016-09-06
20:4
Hi Thomas,
On 8 September 2016 at 00:03, Thomas Gleixner wrote:
> On Tue, 6 Sep 2016, John Stultz wrote:
>> > Changes since v3:
>> > - Fix the build error on S390.
>>
>> Since the original change is already applied to tip/timers/core, can
>> you provide an incremental patch (a patch against tip/
Each individual node in the system has a ZONELIST_FALLBACK zonelist
and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback
order of zones during memory allocations. Sometimes it helps to dump
these zonelists to see the priority order of various zones in them.
Particularly platforms wh
Bjørn Mork [mailto:bj...@mork.no]
> Sent: Wednesday, September 07, 2016 9:51 PM
[...]
> So this adds a lot of code to work around the issues you introduced by
> unnecessarily blacklisting the CDC ECM configuration earlier, and still
> makes the r8152 driver handle the device even in ECM mode.
I su
Dne 3.9.2016 v 21:58 Borislav Petkov napsal(a):
> From: Borislav Petkov
>
> When building a bindeb-pkg target into an object output dir, i.e., O=, I
> get:
>
> find: `scripts/gcc-plugins': No such file or directory
> /mnt/kernel/kernel/linux-2.6/scripts/package/Makefile:97: recipe for target
Hi Sergey,
On Thu, Sep 08, 2016 at 10:34:44AM +0900, Sergey Senozhatsky wrote:
> Hello Minchan,
>
> sorry, I don't have enough time at the moment to review it in details
> due to some urgent issues I'm working on. can this wait?
Why not.
I need a time to complete the work for removing RFC tag,
On Wed, 7 Sep 2016 13:55:47 -0700
Randy Dunlap wrote:
> Yes, that works. Thanks.
>
> Acked-by: Randy Dunlap
Hmm, would "Tested-by" be a more appropriate tag?
-- Steve
On Thu, 8 Sep 2016 07:42:01 +1000
Stephen Rothwell wrote:
> > Link:
> > http://lkml.kernel.org/r/20160907175258.1f17a...@canb.auug.org.au
>
> That is not the reporting email ... Randy's was a reply to that one
> with message id
> "".
>
Strange, I wonder how I got that email. I cut an
David Miller [mailto:da...@davemloft.net]
> Sent: Thursday, September 08, 2016 8:38 AM
[...]
> By forcing a certain mode via a Kconfig value, you are basically making it
> impossible for distributions to do something reasonable here.
The request is always from some manufacturers, not end users.
Th
IP blocks allowing a variety of trace sources to log debugging
information to a pre-defined area have been introduced on a couple of
architecture [1][2]. These system trace blocks (also known as STM)
typically follow the MIPI STPv2 protocol [3] and provide a system wide
logging facility to any devi
Currently Function traces can be only exported to ring buffer, this
patch added trace_export concept which can process traces and export
them to a registered destination as an addition to the current only
output of Ftrace - i.e. ring buffer.
In this way, if we want Function traces to be sent to ot
If CONFIG_STM_FTRACE is selected, Function trace data can be writen
to sink via STM, all functions that related to writing data packets
to STM should be marked 'notrace' to avoid being traced by Ftrace,
otherwise the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Acked-by:
This patch adds a driver that models itself as an stm_source. Once the stm
device and stm_source have been linked via sysfs, the driver registers
itself as a trace_export and everything passed to the interface from Ftrace
subsystem will end up in the STM trace engine.
Signed-off-by: Chunyan Zhang
On Wed, Sep 07, 2016 at 07:55:52AM -0800, Kent Overstreet wrote:
> That said, I'm not advocating people rush out to throw bcachefs on their
> servers
> or use it without backups yet, it's still young and needs more widespread
> testing.
Hi Kent!
Have you started using xfstests to stress test bca
On Thu, 8 Sep 2016, Andrey Utkin wrote:
> Thanks for looking into this.
> I have tested that it compiles and passes checks (C=2) cleanly after
> this patch.
>
> Acked-by: Andrey Utkin
>
> While we're at it, what about constification of
> *-core.c:static struct pci_driver *_pci_driver = {
> *-vi
The musb driver calls into this phy driver to disable/enable squelch
detection. This function was introduced in 24fe86a617c5 ("phy: sun4i-usb:
Add a sunxi specific function for setting squelch-detect"). This
function in turn calls sun4i_usb_phy_write, which uses a mutex to
guard the common access r
On Mon, Jul 11, 2016 at 04:18:08PM +0800, Weiqing Kong wrote:
> Use the mtk_pwm_data struction to define different registers
> and add MT2701 specific register operations, such as MT2701
> doesn't have commit register, needs to disable double buffer
> before writing register, and needs to select ma
The usbphy and usb_otg nodes in the A23 and A33 dts files only differ
by compatible, and for the usbphy, the size of one of its register
regions.
Move all the common bits to the A23/A33 common dtsi file.
Signed-off-by: Chen-Yu Tsai
---
Hi Maxime,
This patch applies on top of your A23/A33 CCU p
This patch adds support to parse probe data for
the dwc3-octeon driver using device tree. The
DWC3 IP core is found on OCTEON III processors.
Signed-off-by: Steven J. Hill
---
drivers/usb/dwc3/Kconfig | 10 +
drivers/usb/dwc3/Makefile | 1 +
drivers/usb/dwc3/dwc3-octeon.c | 96 ++
Le 22/08/2016 à 23:40, Rafał Miłecki a écrit :
> From: Rafał Miłecki
>
> Netgear R8500 is another BCM47094 device, it just has three BCM4366
> wireless chipsets. It's a very standard DT with mostly GPIO devices.
>
> Signed-off-by: Rafał Miłecki
Applied, thanks!
--
Florian
Le 22/08/2016 à 22:37, Rafał Miłecki a écrit :
> BCM53573 seems to be low priced alternative for Northstar chipsts. It
> uses single core Cortex-A7 and doesn't have SDU or local (TWD) timer. It
> was also stripped out of independent SPI controller and 2 GMACs.
>
> DTS for Tenda AC9 isn't completed
On Wed, 7 Sep 2016, Alexander Shishkin wrote:
> Vince Weaver writes:
>
> > On Wed, 7 Sep 2016, Alexander Shishkin wrote:
> >
> >> Sure. And yes, I did catch a warning, which calls for one more patch
> >> (below). Also one unrelated thing in PEBS that Peter fixed.
> >
> > Does that fix this which
On 09/08/2016 12:34 AM, Dave Hansen wrote:
On 09/06/2016 11:51 PM, Xiao Guangrong wrote:
In order to fix this bug, we make 'file->version' indicate the next VMA
we want to handle
This new approach makes it more likely that we'll skip a new VMA that
gets inserted in between the read()s. But,
Hi,
On Thu, Sep 1, 2016 at 10:16 PM, Maxime Ripard
wrote:
> This commit introduces the clocks found in the Allwinner A33 CCU.
>
> Since this SoC is very similar to the A23, and we share a significant share
> of the DTSI, the clock IDs that are going to be used will also be shared
> with the A23,
From: Tomeu Vizoso
Remove code for reading the EDID and DPCD fields and use the helpers
instead.
Besides the obvious code reduction, other helpers are being added to the
core that could be used in this driver and will be good to be able to
use them instead of duplicating them.
Signed-off-by: To
Make sure the request PSR state could effect in analogix_dp_send_psr_spd()
function, or printing the error Sink PSR state if we failed to effect
the request PSR setting.
Signed-off-by: Yakir Yang
---
Changes in v2:
- A bunch of good fixes from Sean
drivers/gpu/drm/bridge/analogix/analogix_dp_co
On 04/09/2016 16:35, Jonathan Cameron wrote:
> On 01/09/16 15:05, Quentin Schulz wrote:
>> The Allwinner SoCs all have an ADC that can also act as a touchscreen
>> controller and a thermal sensor. This patch adds the ADC driver which is
>> based on the MFD for the same SoCs ADC.
>>
>> This also reg
On Wed, 2016-09-07 at 16:50 +0200, Linus Walleij wrote:
> On Tue, Aug 30, 2016 at 9:54 AM, Andrew Jeffery wrote:
>
> >
> > The Aspeed SoCs typically provide more than 200 pins for GPIO and other
> > functions. The signal enabled on a pin is determined on a priority
> > basis, where a given pin c
701 - 800 of 859 matches
Mail list logo
