From: Kuninori Morimoto
This driver's Copyright is under Renesas Solutions Corp
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c
b
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
195 600 0 795 31b drivers/pci/h
The function converts strings like ttyS0 and ttyUSB0 to dev_t like
(4, 64) and (188, 0). It does this by scanning tty_drivers list for
corresponding device name and index. If the driver is not registered,
this function returns -ENODEV. It also acquires tty_mutex.
Signed-off-by: Okash Khawaja
---
This patch introduces new module parameter, dev, which takes a string
representing the device that the external synth is connected to, e.g.
ttyS0, ttyUSB0 etc. This is then used to communicate with the synth.
That way, speakup can support more than ttyS*. As of this patch, it
only supports ttyS*, t
Hi,
I have updated the patches based on feedback. For patch 1, In favour of
consistency, I've updated the code which extracts trailing digits so
that it is like similar code in tty_find_polling_driver. Also fixed
checkpatch warnings.
Here's summary of the patches
Patch 1 adds functionality to co
This patch adds functionality to validate and convert either a device
name or 'ser' memmber of synth into dev_t. Subsequent patch in this set
will call it to convert user-specified device into device number. For
device name, this patch does some basic sanity checks on the string
passed in. It curre
On Mon, Jun 19, 2017 at 5:46 PM, Dave Chinner wrote:
> On Mon, Jun 19, 2017 at 08:22:10AM -0700, Andy Lutomirski wrote:
>> On Mon, Jun 19, 2017 at 6:21 AM, Dave Chinner wrote:
>> > On Sat, Jun 17, 2017 at 10:05:45PM -0700, Andy Lutomirski wrote:
>> >> On Sat, Jun 17, 2017 at 8:15 PM, Dan Williams
On Mon, 19 Jun 2017 20:41:52 +0200,
Bhumika Goyal wrote:
>
> Declare snd_ratnum structures as const as their reference is only
> stored in the rate field of a snd_pcm_hw_constraint_ratnums structure.
> This field is of type const, so snd_ratnum structures can be made const.
>
> Bhumika Goyal (2):
Fixing the clk enable failure path in qcom_qmp_phy_init()
and cleanup the reset control deassertion failure path in
qcom_qmp_phy_com_init().
Fixes: e78f3d15e115 ("phy: qcom-qmp: new qmp phy driver for qcom-chipsets")
Cc: Kishon Vijay Abraham I
Signed-off-by: Vivek Gautam
---
drivers/phy/qualco
Hi all,
Changes since 20170619:
The arm64 tree lost its complex conflicts.
The block tree gained conflicts against the btrfs-kdave.
The tty tree gained a conflict against the arm-soc tree.
The kspp tree gained a build failure for which I applied a merge fix
patch.
The akpm-current tree lost
On Mon, Jun 19, 2017 at 10:57:18PM +0200, Jason A. Donenfeld wrote:
>
> With rc6 already released and rc7 coming up, I'd really appreciate you
> stepping in here and either ACKing the above commit, or giving your
> two cents about it in case I need to roll something different.
I actually had set
On 06/20/2017 10:40 AM, Balbir Singh wrote:
> On Fri, 2017-06-16 at 20:52 -0700, Ram Pai wrote:
>> Memory protection keys enable applications to protect its
>> address space from inadvertent access or corruption from
>> itself.
>
> I presume by itself you mean protection between threads?
Between
On Mon, 19 Jun 2017 01:15:22 +0200,
Hans Peter Möller wrote:
>
> If you can do it, I would appreciate it.
> Thanks.
OK, applied both patches now. Thanks.
Takashi
>
> brgds
> HPM
>
> On Sat, Jun 17, 2017 at 5:20 PM, Takashi Iwai wrote:
>
> > On Sat, 17 Jun 2017 21:03:40 +0200,
> > Hans Pet
On Tue, Jun 20, 2017 at 08:12:26AM +0300, Kalle Valo wrote:
> Willy Tarreau writes:
>
> > From: RafaÅ MiÅecki
> >
> > commit a971df0b9d04674e325346c17de9a895425ca5e1 upstream.
> >
> > This allows tracking device state and e.g. makes devm work as expected.
> >
> > Signed-off-by: RafaÅ MiÅecki
On Thu, Jun 8, 2017 at 1:25 PM, Dietmar Eggemann
wrote:
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> static int
> init_cpu_capacity_callback(struct notifier_block *nb,
> @@ -185,6 +192,7 @@ init_cpu_capacity_callback(struct notifier_block *nb,
>
Hi Guenter,
On Tue, Jun 20, 2017 at 12:51:46AM +0200, Willy Tarreau wrote:
> Hi Guenter,
>
> On Mon, Jun 19, 2017 at 03:46:36PM -0700, Guenter Roeck wrote:
> > Build results:
> > total: 121 pass: 118 fail: 3
> > Failed builds:
> > arm:at91_dt_defconfig
> > arm:sama5_defconfig
> >
On 06/17/2017 09:22 AM, Ram Pai wrote:
> The Documentaton file is moved from x86 into the generic area,
> since this feature is now supported by more than one archs.
>
> Signed-off-by: Ram Pai
> ---
> Documentation/vm/protection-keys.txt | 110
> ++
> Documentat
File size before:
textdata bss dec hex filename
24691552 244045 fcd drivers/video/fbdev/fsl-diu-fb.o
File size After adding 'const':
textdata bss dec hex filename
3821 200 244045 fcd drivers/video/fbdev/fsl-diu-fb.o
Sig
The shmem_acct_block and the update of used_blocks are following one
another in all the places they are used. Combine these two into a helper
function.
Signed-off-by: Mike Rapoport
---
mm/shmem.c | 102 -
1 file changed, 46 insertions(+
For shmem VMAs we can use shmem_mfill_zeropage_pte for UFFDIO_ZEROPAGE
Signed-off-by: Mike Rapoport
---
mm/userfaultfd.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index 48c015c..8119270 100644
--- a/mm/userfaultfd.c
+++ b/mm/use
Currently we update inode and shmem_inode_info before verifying that
used_blocks will not exceed max_blocks. In case it will, we undo the
update. Let's switch the order and move the verification of the blocks
count before the inode and shmem_inode_info update.
Signed-off-by: Mike Rapoport
---
mm
Hi,
These patches enable support for UFFDIO_ZEROPAGE for shared memory.
The first two patches are not strictly related to userfaultfd, they are
just minor refactoring to reduce amount of code duplication.
Mike Rapoport (7):
shmem: shmem_charge: verify max_block is not exceeded before inode upd
Signed-off-by: Mike Rapoport
---
tools/testing/selftests/vm/userfaultfd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/vm/userfaultfd.c
b/tools/testing/selftests/vm/userfaultfd.c
index 1eae79a..b0c9263 100644
--- a/tools/testing/selftests/vm/userfau
Shuffle the code a bit to improve readability.
Signed-off-by: Mike Rapoport
---
mm/userfaultfd.c | 46 ++
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index 8bcb501..48c015c 100644
--- a/mm/userfau
Now when shmem VMAs can be filled with zero page via userfaultfd we can
report that UFFDIO_ZEROPAGE is available for those VMAs
Signed-off-by: Mike Rapoport
---
fs/userfaultfd.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
ind
shmem_mfill_zeropage_pte is the low level routine that implements the
userfaultfd UFFDIO_ZEROPAGE command. Since for shmem mappings zero pages are
always allocated and accounted, the new method is a slight extension of the
existing shmem_mcopy_atomic_pte.
Signed-off-by: Mike Rapoport
---
include
If 'wiphy_new()' fails, we leak 'ops'. Add a new label in the error
handling path to free it in such a case.
Fixes: 5c22fb85102a7 ("brcmfmac: add wowl gtk rekeying offload support")
Signed-off-by: Christophe JAILLET
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 3 ++-
1 file
On Sun, Jun 18, 2017 at 09:13:28PM -0400, Stefan Berger wrote:
> Can you adapt your test cases. I haven't tried them, but having
> them would be important.
branch nsfscaps of github.com/hallyn/ltp now has a patch on top
which makes it work with your capabilities. Tests are passing.
thanks,
-ser
On 06/17/2017 09:22 AM, Ram Pai wrote:
> Added test support for PowerPC implementation off protection keys.
>
> Signed-off-by: Ram Pai
First of all, there are a lot of instances where we use *pkru*
named functions on power even the real implementations have
taken care of doing appropriate things
ANDOM so that the answer is 'n'. It *is* spammy
> for PowerPC, because they aren't getting their CRNG initialized
> quickly enough, so several userspace processes are getting
> fork/exec'ed with an uninitialized CRNG.
It's very spammy for ARM as well. I booted next-2
On Fri, Jun 16, 2017 at 09:29:28AM +0200, Quentin Schulz wrote:
> The setting of clocks and presets is currently done in probe only but
> once deep PM support is added, it'll be needed in the resume function.
>
> Let's create a function for this setting.
>
> Signed-off-by: Quentin Schulz
Acked-b
Christophe JAILLET writes:
> If 'wiphy_new()' fails, we leak 'ops'. Add a new label in the error
> handling path to free it in such a case.
>
> Fixes: 5c22fb85102a7 ("brcmfmac: add wowl gtk rekeying offload support")
> Signed-off-by: Christophe JAILLET
The prefix should be "brcmfmac:", like in
On Fri, Jun 16, 2017 at 09:29:29AM +0200, Quentin Schulz wrote:
> This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2
> SoC's SDHCI controller.
>
> When resuming from deepest state, it is required to restore preset
> registers as the registers are lost since VDD core has been s
Am 20.06.2017 um 06:40 schrieb Oleksij Rempel:
> snvs_lpgpr confirmed to work with imx6ul as well.
>
> Signed-off-by: Oleksij Rempel
> Tested-by: Guy Shapiro
> ---
> Documentation/devicetree/bindings/nvmem/snvs-lpgpr.txt | 3 ++-
> arch/arm/boot/dts/imx6ul.dtsi | 4
Will,
On 07.06.17 12:50:12, Will Deacon wrote:
> Thanks, I've pushed this out as:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-next/ras-apei
>
> which I'll merge into for-next/core (and therefore linux-next) either the
> end of this week or the beginning of next week
On 16/06/17 10:29, Quentin Schulz wrote:
> The setting of clocks and presets is currently done in probe only but
> once deep PM support is added, it'll be needed in the resume function.
>
> Let's create a function for this setting.
>
> Signed-off-by: Quentin Schulz
Apart from cosmetic comment b
On 2017-06-19 22:55:37 [+0200], Jason A. Donenfeld wrote:
> On Mon, Jun 19, 2017 at 9:45 AM, Sebastian Andrzej Siewior
> wrote:
> > ehm. You sure? I simply delayed the lock-dropping _after_ the state
> > variable was been modified. So it was basically what your patch did
> > except it was unlocked
On Mon, Jun 19, 2017 at 06:26:23PM +0200, Jessica Yu wrote:
> +++ Corentin Labbe [06/06/17 14:17 +0200]:
> >This patch just swap del_usage_link() before add_usage_link().
> >
> >Signed-off-by: Corentin Labbe
>
> Could you combine this with the 2nd patch? By itself this patch
> doesn't tell us muc
On 06/19/2017 11:29 PM, Ram Pai wrote:
> On Mon, Jun 19, 2017 at 09:06:13PM +1000, Michael Ellerman wrote:
>> Ram Pai writes:
>>
>>> Signed-off-by: Ram Pai
>>> ---
>>> arch/powerpc/kernel/exceptions-64s.S | 16 ++--
>>> 1 file changed, 10 insertions(+), 6 deletions(-)
>>>
>>> diff --
On 19 June 2017 at 17:03, Will Deacon wrote:
> On Mon, Jun 19, 2017 at 04:37:24PM +0200, Ard Biesheuvel wrote:
>> On arm64, the /dev/kmem driver barely works, given that it assumes that
>> VMALLOC_START > PAGE_OFFSET, which is not the case on arm64. Due to the
>
> Probably worth being explicit abo
On 06/17/2017 09:22 AM, Ram Pai wrote:
> The value of the AMR register at the time of exception
> is made available in gp_regs[PT_AMR] of the siginfo.
>
> This field can be used to reprogram the permission bits of
> any valid pkey.
>
> Similarly the value of the pkey, whose protection got violate
On Mon, Jun 19, 2017 at 01:56:40PM -0700, Kees Cook wrote:
> Since the ACPICA source is maintained externally to the kernel, we can
> neither switch it to designated initializers nor mark it
> __no_randomize_layout. Until ACPICA-upstream changes[1] land to handle the
> designated initialization, ex
Thomas,
Am 20.06.2017 um 03:56 schrieb Thomas Meyer:
> Hi,
>
> I finally did figure out where in the host kernel the ptrace syscall
> fails with -EFAULT.
Nice! Thanks a lot for digging into this. I still had no chance to setup
Ipv6 to connect to your host and figure myself. ;-\
> In arch/x86/ke
On Tue, 20 Jun 2017, Dou Liyang wrote:
> At 06/20/2017 07:37 AM, Thomas Gleixner wrote:
> [...]
> >
> > +/**
> > + * irq_fixup_move_pending - Cleanup irq move pending from a dying CPU
> > + * @desc: Interrupt descpriptor to clean up
> > + * @force_clear: If set clear the move pending bi
As it turns out, arm64 deviates from other architectures in the way it
maps the VMALLOC region: on most (all?) other architectures, it resides
strictly above the kernel's direct mapping of DRAM, but on arm64, this
is the other way around. For instance, for a 48-bit VA configuration,
we have
modu
On 09/06/17 21:56, Laura Abbott wrote:
> On 06/07/2017 05:35 AM, Igor Stoppa wrote:
[...]
> The pool logic looks remarkably similar to genalloc (lib/genalloc.c).
> It's not a perfect 1-to-1 mapping but it's close enough to be worth
> a look.
Indeed. I have prepared a new incarnation of pmalloc,
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
48051408 062131845 drivers/gpu/d
On Sun, Jun 18, 2017 at 11:45:07PM -0700, Deepa Dinamani wrote:
> The series aims at isolating data conversions of time_t based structures:
> struct timespec and struct itimerspec at user space boundaries.
> This helps to later change the underlying types to handle y2038 changes
> to these.
>
> Th
* Kishon Vijay Abraham I [170618 23:37]:
> Hi Tony,
>
> On Monday 19 June 2017 11:32 AM, Tony Lindgren wrote:
> > * Kishon Vijay Abraham I [170616 05:47]:
> >> The data manual of J6/J6 Eco recommends to set different IODELAY values
> >> depending on the mode in which the MMC/SD is enumerated in
On Mon, 2017-06-19 at 15:31 +1000, Stewart Smith wrote:
> IBM Verse is a web UI around Lotus Domino mail servers (much like
> the Lotus Notes client talks to Domino servers).
>
> For various reasons, it is not at all suitable for kernel development,
> all of which have been raised (repeatedly) int
From: Daniel Walter
fscrypt provides facilities to use different encryption algorithms which
are selectable by userspace when setting the encryption policy. Currently,
only AES-256-XTS for file contents and AES-256-CBC-CTS for file names are
implemented. This is a clear case of kernel offers the
This adds support for the new AC97 bus code, which discovers the devices
rather than uses platform data.
As part of this discovery, it enables a multi-function device wm97xx,
which supports touchscreen, battery, ADC and an audio codec. This patch
adds the code to bind the touchscreen "cell" as the
Add support for the new ac97 bus model, where devices are automatically
discovered on AC-Links.
Signed-off-by: Robert Jarzmik
---
sound/soc/codecs/Kconfig | 3 ++-
sound/soc/codecs/wm9713.c | 39 +++
2 files changed, 29 insertions(+), 13 deletions(-)
diff -
All pxa library functions don't use the input parameters for nothing but
slot number. This simplifies their prototypes, and makes them usable by
both the legacy ac97 bus and the new ac97 bus.
Signed-off-by: Robert Jarzmik
---
include/sound/pxa2xx-lib.h | 15 +--
sound/arm/pxa2xx-ac9
From: Takashi Iwai
soc_cleanup_card_resources() call snd_card_free() at the last of its
procedure. This turned out to lead to a use-after-free.
PCM runtimes have been already removed via soc_remove_pcm_runtimes(),
while it's dereferenced later in soc_pcm_free() called via
snd_card_free().
The f
The WM9705, WM9712 and WM9713 are highly integrated codecs, with an
audio codec, DAC and ADC, GPIO unit and a touchscreen interface.
Historically the support was spread across drivers/input/touchscreen and
sound/soc/codecs. The sharing was done through ac97 bus sharing. This
model will not withsta
Add support for the new ac97 bus model, where devices are automatically
discovered on AC-Links.
Signed-off-by: Robert Jarzmik
---
sound/soc/codecs/Kconfig | 3 ++-
sound/soc/codecs/wm9705.c | 35 +++
2 files changed, 25 insertions(+), 13 deletions(-)
diff --git
Add the new ac97 bus support, with ac97 bus automatic probing.
Signed-off-by: Robert Jarzmik
Acked-by: Charles Keepax
---
sound/Kconfig | 2 ++
sound/Makefile| 1 +
sound/soc/Kconfig | 4
3 files changed, 7 insertions(+)
diff --git a/sound/Kconfig b/sound/Kconfig
index ee2e69a9ecd
Add a private data structure. This is a preparation for a codec which
would need an another data on top of snd_ac97, which will be the case
when an MFD wm97xx device will probe wm9705.
Signed-off-by: Robert Jarzmik
---
sound/soc/codecs/wm9705.c | 36
1 file c
AC97 is a bus for sound usage. It enables for a AC97 AC-Link to link one
controller to 0 to 4 AC97 codecs.
The goal of this new implementation is to implement a device/driver
model for AC97, with an automatic scan of the bus and automatic
discovery of AC97 codec devices.
Signed-off-by: Robert Jar
wm97xx-core does several things in it initialization :
- touchscreen input device setup
- battery device creation
As the wm97xx is actually a multi-function device handling an audio
codec, a touchscreen, a gpio block and an ADC, reshape the probing to
isolate what is truly input/touchscreen spec
Hi Lars, Mark, Charles, Lee,
This serie has been stalled for almost one year, as I wasn't feeling that
well lately. I'm quite better now, so let's get back to it.
As it's been so long since the last review, I basically withdrew all my former
objections and took into account all remarks regardless
Documentation/kbuild/makefiles.txt says the change for align options
occurred at GCC 3.0, and Documentation/process/changes.rst says the
minimal supported GCC version is 3.2, so it should be safe to hard-code
-falign* options.
Fix the only user arch/x86/Makefile_32.cpu and deprecate the
cc-option-
Hi Sanchayan,
On 19.06.2017 07:13, Sanchayan wrote:
Hello Oleksij,
On 17-06-14 22:48:52, Oleksij Rempel wrote:
Hallo all,
this is RFC patchset to provide remoteproc functionality on
imx7d SoC.
Since current kernel do not have devicetrees for board which
I used for testing, this RFC patchset i
On Sat, 2017-06-17 at 21:38 +0200, Greg KH wrote:
> But we don't accept kernel patches for some mythical future option
> that might be happening some time in the future. Heck, I'm still not
> convinced that firmware signing isn't anything more than just some
> snakeoil in the first place!
I for
Add support for the new ac97 bus model, where devices are automatically
discovered on AC-Links.
Signed-off-by: Robert Jarzmik
---
sound/soc/codecs/Kconfig | 3 ++-
sound/soc/codecs/wm9712.c | 37 -
2 files changed, 26 insertions(+), 14 deletions(-)
diff --g
Switch to the new ac97 bus support in sound/ac97 instead of the legacy
snd_ac97 one.
Signed-off-by: Robert Jarzmik
---
Since v1: split into 2 patches, the former being XXX ac97 codec agnostic
---
sound/arm/Kconfig | 1 -
sound/soc/pxa/Kconfig | 5 ++---
sound/soc/pxa/pxa2xx-ac9
Dell Latitude 3160 does not have keyboard backlight, but there is a
sysfs interface for it, which does nothing at all.
KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have
KBD_LED_OFF_TOKEN or KBD_LED_AUTO_*_TOKEN, it should be safe to assume it
does not support keyboard backligh
On Sat, 2017-06-17 at 12:26 -0300, Mauro Carvalho Chehab wrote:
> Each text file under Documentation follows a different
> format. Some doesn't even have titles!
>
> Change its representation to follow the adopted standard,
> using ReST markups for it to be parseable by Sphinx:
>
> - mark titles;
-bfq-update-wr_busy_queues-if-needed-on-a-queue-split/20170619-145003
config: i386-randconfig-x000-201725 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: it may well be a FALSE
The clut is not synchronized with the drm gamma_lut state.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 53 ++
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 12 +-
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h | 4 ++
3 files ch
Hi,
Thank you for your review!
On 15.06.2017 21:01, Suman Anna wrote:
Hi Oleksij,
On 06/14/2017 03:48 PM, Oleksij Rempel wrote:
From: Oleksij Rempel
this driver was tested on NXP imx7d but should work on
imx6sx as well.
It will upload firmware to OCRAM, which shared memory between
Cortex A7
All layers of all supported chips support this, the only variable is the
base address of the lookup table in the register map.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 5 +
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c| 13 +++
drivers/gpu/
DRM drivers supporting clut may want a convenient way to only use
non-default .gamma_set and .gamma_get ops in the drm_fb_helper_funcs
in order to avoid the following
/*
* The driver really shouldn't advertise pseudo/directcolor
* visuals if it can't deal with the palette
Hi!
This series adds support for an 8-bit clut mode in the atmel-hlcdc
driver.
I have now tested patch 1 with the below program (modeset.c
adapted from https://github.com/dvdhrm/docs/tree/master/drm-howto
to use an 8-bit mode).
Since v2 I have also cleared up why the first 16 entries of the clut
On Sun, 18 Jun 2017 12:04:26 +0200
Pavel Machek wrote:
> On Fri 2017-06-02 22:54:54, Nicholas Piggin wrote:
> > Switch from incremental build to thin archives for packaging built-in.o.
> > binutils version must be bumped to 2.20. Proposed patch for 4.13.
> >
> > Signed-off-by: Nicholas Piggin
On 2017-06-17 02:39:40 [+0200], Jason A. Donenfeld wrote:
> On Fri, Jun 16, 2017 at 4:35 PM, Sebastian Andrzej Siewior
> wrote:
> > I wouldn't just push the lock one up as is but move that write part to
> > crng_init to remain within the locked section. Like that:
>
> We can't quite do that, beca
Jeff Layton wrote:
> Do you have a reference to the discussion so I can understand the
> rationale there?
I'm afraid not - it was around 15-20 years ago, I think. I seem to remember
the rationale being something like "because it's a stupid idea".
David
+Alexandre and Nicolas
Hi Peter,
Can you please Cc at91 maintainers next time?
On Mon, 19 Jun 2017 09:44:23 +0200
Peter Rosin wrote:
> Hi!
>
> This series adds support for an 8-bit clut mode in the atmel-hlcdc
> driver.
>
> I have now tested patch 1 with the below program (modeset.c
> adapte
Hi Jacopo,
Thank you for the patch.
On Friday 16 Jun 2017 10:59:41 Jacopo Mondi wrote:
> Add output-enable generic pin configuration property.
> This properties allows enabling/disabling pin's output capabilities
> without actually driving any value on the line.
>
> Signed-off-by: Jacopo Mondi
On Mon, Jun 19, 2017 at 01:27:08PM +0800, Herbert Xu wrote:
> On Tue, Jun 06, 2017 at 03:44:17PM +0200, Corentin Labbe wrote:
> > The crypto engine could actually only enqueue hash and ablkcipher request.
> > This patch permit it to enqueue skcipher requets by adding all necessary
> > functions.
>
Hi Tony,
On Monday 19 June 2017 12:55 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [170618 23:37]:
>> Hi Tony,
>>
>> On Monday 19 June 2017 11:32 AM, Tony Lindgren wrote:
>>> * Kishon Vijay Abraham I [170616 05:47]:
The data manual of J6/J6 Eco recommends to set different IODELAY val
Thanks for your kindly reply.
We are think of how to change our driver to follow the comments now.
I reply one thing about reading BER measures at get_frontend() in this mail.
On 2017/06/13 22:30, Mauro Carvalho Chehab wrote:
> Em Fri, 14 Apr 2017 11:31:50 +0900
> escreveu:
>
>> From: Yasunari
On Monday 19 June 2017 15:36:29 Kai-Heng Feng wrote:
> Dell Latitude 3160 does not have keyboard backlight, but there is a
> sysfs interface for it, which does nothing at all.
>
> KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have
*ON* really?
> KBD_LED_OFF_TOKEN or KBD_LED_A
Hi Benjamin
On 06/16/2017 04:03 PM, Benjamin Gaignard wrote:
> Make driver use u64 variables and functions to be sure that
> it will support dates after year 2038.
>
> Signed-off-by: Benjamin Gaignard
> ---
> drivers/rtc/rtc-st-lpc.c | 19 ---
> 1 file changed, 8 insertions(+)
On Tue, 2017-05-30 at 18:53 +0900, Hirokazu Honda wrote:
> A driver error message is shown without DEBUG definition
> to find an error and debug easily.
>
> Signed-off-by: Hirokazu Honda
Acked-by: Tiffany Lin
> ---
> drivers/media/platform/mtk-vcodec/mtk_vcodec_util.h | 20 +---
* Multicast addresses are never valid as local address
* Link-local IPv6 unicast addresses may only be used as remote when the
local address is link-local as well
* Don't allow link-local IPv6 local/remote addresses without interface
We also store in the flags field if link-local addresses are u
As link-local addresses are only valid for a single interface, we can allow
to use the same VNI for multiple independent VXLANs, as long as the used
interfaces are distinct. This way, VXLANs can always be used as a drop-in
replacement for VLANs with greater ID space.
This also extends VNI lookup t
If VXLAN is run over link-local IPv6 addresses, it is necessary to store
the ifindex in the FDB entries. Otherwise, the used interface is undefined
and unicast communication will most likely fail.
Support for link-local IPv4 addresses should be possible as well, but as
the semantics aren't as well
Address families of source and destination addresses must match, and
changelink operations can't change the address family.
In addition, always use the VXLAN_F_IPV6 to check if a VXLAN device uses
IPv4 or IPv6.
Signed-off-by: Matthias Schiffer
---
Notes:
v2: new patch
v3: rebase
drive
ATTENZIONE;
La cassetta postale ha superato il limite di archiviazione, che è 5 GB come
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non
si può essere in grado di inviare o ricevere nuovi messaggi fino a
ri-convalidare la tua mailbox. Per rinnovare la vostra casella d
There is no good reason to keep the flags twice in vxlan_dev and
vxlan_config.
Signed-off-by: Matthias Schiffer
---
Notes:
v2: new patch
v3: rebase
drivers/net/vxlan.c | 76 +--
include/net/vxlan.h | 1 -
net/openvswitch/vpor
Running VXLANs over IPv6 link-local addresses allows to use them as a
drop-in replacement for VLANs, avoiding to allocate additional outer IP
addresses to run the VXLAN over.
Since v1, I have added a lot more consistency checks to the address
configuration, making sure address families and scopes
The vxlan_dev_configure function was mixing validation and application of
the vxlan configuration; this could easily lead to bugs with the changelink
operation, as it was hard to see if the function wcould return an error
after parts of the configuration had already been applied.
This commit split
On Sun, Jun 18, 2017 at 04:27:42PM +0300, Andy Shevchenko wrote:
> This doesn't have actual parameter name.
> Btw, I would drop dev_ suffix completely from parameter (you have it
> in function name).
Good call, thanks.
> > + * Locking: this acquires tty_mutex
>
> ...and releases.
>
> Perhap
On Fri 16-06-17 19:04:44, Tahsin Erdogan wrote:
> On Thu, Jun 15, 2017 at 2:10 AM, Jan Kara wrote:
> > I agree with moving ext4_xattr_rehash_entry() out of ext4_xattr_rehash().
> > However how about just keeping ext4_xattr_rehash() in
> > ext4_xattr_block_set() (so that you don't have to pass adit
On 15 June 2017 at 12:06, Peter Chen wrote:
> On Thu, Jun 15, 2017 at 11:35:20AM +0200, Ulf Hansson wrote:
>> On 15 June 2017 at 11:11, Peter Chen wrote:
>> > On Thu, Jun 15, 2017 at 10:11:45AM +0200, Ulf Hansson wrote:
>> >> > Yes, you are right. This is the limitation for this power sequence
>>
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (sparc
defconfig) failed like this:
arch/sparc/mm/extable.c:16:1: error: conflicting types for 'search_extable'
search_extable(const struct exception_table_entry *start,
^
In file included from arch/sparc/mm/extable.c:6:0:
Hi all,
Changes since 20170616:
Undropped tree: uuid
The arm64 tree gained conflicts against the uuid tree so I merged the
version of the arm64 tree from next-20170615 for today.
The sound-asoc tree lost its build failure.
The scsi tree gained conflicts against the block tree.
The kspp tree l
On Sun, Jun 18, 2017 at 09:58:27AM +0100, Okash Khawaja wrote:
> +int ser_to_dev(int ser, dev_t *dev_no)
> +{
> + if (ser < 0 || ser > (255 - 64)) {
> +pr_err("speakup: Invalid ser param. \
> + Must be between 0 and 191 inclusive.\n");
I pointed out
101 - 200 of 1571 matches
Mail list logo
