Attempts to modify un-leased objects are rejected with an error.
Information returned about unleased objects is modified to make them
appear unusable and/or disconnected.
Changes for v2 as suggested by Daniel Vetter :
With the change in the __drm_mode_object_find API to
Separate out lease debugging from the core.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/drm_drv.c | 3 ++-
include/drm/drmP.h| 4
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index
This will allow __drm_mode_object_file to be extended to perform
access control checks based on the file in use.
Suggested-by: Daniel Vetter
Signed-off-by: Keith Packard
---
drivers/gpu/drm/amd/amdgpu/amdgpu_connectors.c | 16
Here's a second try at mode resource leasing. The differences from v1
are mostly deleting functionality that isn't currently useful.
There are no more sub-leases; there's the owner, the owner is the only
lessor and so the only one who can create leases and hand those out.
The lessor can now
This provides new data structures to hold "lease" information about
drm mode setting objects, and provides for creating new drm_masters
which have access to a subset of the available drm resources.
An 'owner' is a drm_master which is not leasing the objects from
another drm_master, and hence
drm_mode_create_lease
Creates a lease for a list of drm mode objects, returning an
fd for the new drm_master and a 64-bit identifier for the lessee
drm_mode_list_lesees
List the identifiers of the lessees for a master file
drm_mode_get_lease
List the leased
This patch fixes the following sparse warning in fbtft/fbtft-io.c
CHECK drivers/staging/fbtft/fbtft-io.c
drivers/staging/fbtft/fbtft-io.c:74:29: warning: incorrect type in assignment
(different base types)
drivers/staging/fbtft/fbtft-io.c:74:29:expected unsigned long long
[unsigned]
-the-vTPM-proxy-driver-to-pass-locality-to-emulator/20170429-115352
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
include/linux/init.h:1: warning: no structured comments found
kernel/sched/core.c:2085: warning: No description found for parameter 'rf'
kernel/sched/core.
Currently the file descriptors are allocated using a custom allocator.
This patchset replaces the custom code with an IDR. This replacement will
result in some memory saving for processes with relatively few open files
and improve performance of workloads with very large numbers of open files.
Now that the IDR uses the radix tree, we can expose the radix tree tags
to users of the IDR. A few spots in the radix tree needed to be changed
to cope with the fact that the IDR can have NULL pointers with tags set.
One of the more notable changes is that IDR_FREE really is special -- an
index
In the file descriptor table duplication code (called at fork()), we
need to duplicate an IDR. But we have to do it under a lock (so another
thread doesn't open/close a fd in the middle), and there's no suitable
preload operation for this today. Adding just idr_copy_preload() isn't
enough as
Instead of storing all the file pointers in a single array, use an
IDR. It is RCU-safe, and does not need to be reallocated when the
fd array grows. It also handles allocation of new file descriptors.
Signed-off-by: Sandhya Bankar
[mawil...@microsoft.com: fixes]
The IDR is used in file descriptor allocation code to
allocate new file descriptor so, no need of next_fd to
track next file descriptor.
Hence removing it from file descriptor allocation code path.
Signed-off-by: Sandhya Bankar
Signed-off-by: Matthew Wilcox
On Fri, Apr 28, 2017 at 01:18:18PM -0600, Shuah Khan wrote:
> On 04/28/2017 02:30 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.65 release.
> > There are 17 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Fri, Apr 28, 2017 at 11:46:06AM -0700, Guenter Roeck wrote:
> On Fri, Apr 28, 2017 at 10:30:13AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.65 release.
> > There are 17 patches in this series, all will be posted as a response
> > to this one.
Replace close_on_exec with idr_(get,set,clear)_tag().
Through this patch, added new IDR tag FD_TAG_CLOEXEC
which is passing to idr_(get,set,clear)_tag() to
achieve close_on_exec functionality.
Also removed get_close_on_exec() and using close_on_exec() instead of that.
Signed-off-by: Sandhya
Completing the conversion of the file descriptor allocation code to use
the IDR.
This patch includes below changes:
- Move max_fds from struct fdtable to files_struct.
- Added fill_max_fds() routine to calculate the new value of max_fds
to matches the old behaviour of alloc_fdtable() code
Previously, the only way to capture data is to read the exposed sysfs
files in_accel_[x/y/z]_raw and applying the scale from in_accel_scale.
Provide a way for continuous data capture that allows multiple data
channels to be read at once by setting up buffer support.
Initialize scan_type fields
The ADXL345 provides a DATA_READY interrupt function to signal
availability of new data. This interrupt function is latched and can be
cleared by reading the data registers. The polarity is set to active
high by default.
Support this functionality by setting it up as an IIO trigger.
In addition,
Move code that enables measurement/standby mode into its own function
and call that function when appropriate. Previously, we set the sensor
to measurement in probe and back to standby during remove. Change it
here to only enter measurement mode when request for data is initiated.
The DATA_READY
Convert select to use idr_get_tag_batch().
Signed-off-by: Sandhya Bankar
Signed-off-by: Matthew Wilcox
---
fs/select.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/fs/select.c b/fs/select.c
index
Removes a sparse warning about init_files() not being declared.
Signed-off-by: Matthew Wilcox
---
fs/file.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/file.c b/fs/file.c
index 56c5731..23f198b 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -19,6 +19,7 @@
#include
2017-04-28 16:30 GMT+03:00 Bin Liu :
> On Fri, Apr 28, 2017 at 04:15:09PM +0300, Matwey V. Kornilov wrote:
>> 2017-04-28 15:43 GMT+03:00 Bin Liu :
>> > On Fri, Apr 28, 2017 at 03:13:55PM +0300, Matwey V. Kornilov wrote:
>> >> which i
>> >>
>> >> 2017-04-28 14:58
Dear Friend,
I know that this mail will come to you as a surprise since we have not
known or met before now, but please, I would like you to treat it like
blood brother affair and with the urgency and secrecy it requires. I
am Mr. Hassan Alwan Ali, an Audit staff of (C.B.N) Central Bank of
-vector-of-ns_last_pid-s-on-ns-hierarhy/20170429-155011
config: i386-defconfig (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
All errors (new ones prefixed by >>):
Hello,
On Fri, 2017-04-28 at 22:17 +0300, Andy Shevchenko wrote:
> On Wed, Feb 22, 2017 at 12:24 PM, Ritesh Raj Sarraf wrote:
>
> > Any further comment on this patch ? Will this be accepted ?
> > Please give a N/ACK.
>
> Sorry for a long delay, but I can't go with this without
Hello Andy,
Thus wrote Andy Shevchenko (andy.shevche...@gmail.com):
> On Tue, Apr 18, 2017 at 12:11 PM, Martin Kaiser wrote:
> > checkpatch is asking for a 4 digit octal number. And at least for me,
> > 0444 makes it clearer what the permissions actually are. Yes, somewhere
>
Add the ability to iterate over tagged entries in the IDR with
idr_get_next_tag() and idr_for_each_entry_tagged().
Signed-off-by: Matthew Wilcox
---
include/linux/idr.h | 15 ++-
lib/idr.c | 30
To implement select() on top of the IDR, we need to be able to get the
tags which represent the open files in bulk. For this user, it makes
sense to get a batch of BITS_PER_LONG tags at a time, and until another
user shows up that wants something different, let's enforce that instead
of coping
The IDR has removed the need to have full_fds_bits hence removing it.
Signed-off-by: Sandhya Bankar
Signed-off-by: Matthew Wilcox
---
fs/file.c | 18 +-
include/linux/fdtable.h | 2 --
2 files changed, 1
Use idr_tag_get() in fd_is_open() to know whether a given fd is
allocated. Also move fd_is_open() to file.c and make it static
as it is only called from one place.
Signed-off-by: Sandhya Bankar
Signed-off-by: Matthew Wilcox
---
fs/file.c
Use the IDR iteration functionality instead of the open_fds bitmap to
call filp_close() for each open file. Also make close_files() return
void, because it no longer uses the fdtable.
Signed-off-by: Sandhya Bankar
Signed-off-by: Matthew Wilcox
Introduce the DATA_READY trigger and enable triggered buffering. Additional
changes include introduction of functions set_mode and data_ready, allow
either INT1/INT2 pin be used by specifying interrupt-names.
Triggered buffer was tested on both DATA_READY trigger and the hrtimer software
trigger.
Add interrupt-names property in order to specify interrupt pin in use.
Signed-off-by: Eva Rachel Retuya
Acked-by: Rob Herring
---
Change in v2:
* Add Rob's Acked-by tag
Documentation/devicetree/bindings/iio/accel/adxl345.txt | 4
1 file changed, 4
On Saturday 29 April 2017 05:36 AM, Matthias Kaehlcke wrote:
Some regulators have different settling times for voltage increases and
decreases. To avoid a time penalty on the faster transition extend the
settling time property to allow for different settings for upward and
downward transitions.
> Hmmm, allocs -> callocs. Are these actually beneficial? If so, why?
> Because one multiplication is rolled into the call?
Did the previous size calculations contain the general possibility for
integer overflows?
https://cwe.mitre.org/data/definitions/190.html
* Will the computed values
Hi Dan,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.11-rc8 next-20170428]
[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/Dan-Williams/dynamic_hex_dump-cleanup/20170429
Hi!
> > + devices[index].subdev_fds[0] = SYS_OPEN("/dev/video_sensor", O_RDWR, 0);
> > + devices[index].subdev_fds[1] = SYS_OPEN("/dev/video_focus", O_RDWR, 0);
> > + devices[index].subdev_fds[2] = -1;
>
> Hardcoding names here is not a good idea. Ideally, it should open
> the MC, using
On 2017/4/29 10:46, Al Viro wrote:
> On Sat, Apr 29, 2017 at 10:38:48AM +0800, Ding Tianhong wrote:
>> The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve
>> ->msg_iter on error) will revert the iov buffer if copy to iter
>> failed, but it didn't copy any datagram if the
PSX pads can be connected directly to the SPI bus.
Signed-off-by: Tomohiro Yoshidomi
---
drivers/input/joystick/Kconfig | 17 ++
drivers/input/joystick/Makefile | 1 +
drivers/input/joystick/psxpad-spi.c | 387
3 files
Mr.Torokhov
I changed source, and sent PATCH v5 to you.
* Delete about 'analog 2'
Deleted experimental features.
Possibility of confusing SDL.
* Delete about setadmode()
Never set analog mode from the system to the pad.
* Delete SPI 'delay_usecs'
Unnecessary
* Delete psxpad_spi_deinit_ff()
On 04/28/17 at 12:37pm, Kees Cook wrote:
> On Wed, Apr 26, 2017 at 3:16 AM, Baoquan He wrote:
> > In commit:
> >
> > f28442497b5c ("x86/boot: Fix KASLR and memmap= collision")
> >
> > ... the memmap= option is parsed so that KASLR can avoid those reserved
> > regions. It uses
On 04/28/17 at 12:39pm, Kees Cook wrote:
> On Wed, Apr 26, 2017 at 3:16 AM, Baoquan He wrote:
> > Option mem= will limit the max address a system can use and any memory
> > region above the limit will be removed.
> >
> > Furthermore, memmap=nn[KMG] which has no offset specified
On Fri, Apr 28, 2017 at 03:33:07PM -0400, Jerome Glisse wrote:
> On Fri, Apr 28, 2017 at 12:22:24PM -0700, Dan Williams wrote:
> > Are you sure about needing to hook the 2 -> 1 transition? Could we
> > change ZONE_DEVICE pages to not have an elevated reference count when
> > they are created so
On Fri, Apr 28, 2017 at 10:18:09AM -0700, Jerry Snitselaar wrote:
> On Fri Apr 28 17, Jarkko Sakkinen wrote:
> > On Wed, Apr 26, 2017 at 03:39:54PM -0700, Jerry Snitselaar wrote:
> > > For easier decoding, output the error code returned
> > > from the tpm device in hex when the device is TPM2.0.
>
On Fri, 28 Apr 2017 19:25:39 +0900
Masami Hiramatsu wrote:
> Print out fatal error in stderr as same as fatal() does.
>
> Signed-off-by: Masami Hiramatsu
> ---
> arch/um/kernel/physmem.c |8
> arch/um/kernel/um_arch.c |2 +-
>
Good Day,
Please accept my apologies for writing you a surprise letter.I am
Mr.David Owain, account Manager with an investment bank here in
Burkina Faso.I have a very important business I want to discuss with
you.There is a draft account opened in my firm by a long-time client
of our bank.I have
commit 9304b5b0d4fe8498d3d059db4bb8a7de253355a5 adds casting of le16
values to cpu to get rid of sparse warnings. The u4bAcParam is therefore
constructed using machines endianess. However, the parameter ought to be casted
back to little endian to keep the function logic the same as before.
Split the u4bAcParam parameter construction to multiple lines for easier
readability.
Signed-off-by: Tuomo Rinne
---
drivers/staging/rtl8192u/r8192U_dm.c | 28 +++-
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git
Remove scope unnecessary scope that is already enforced by the if
statements scope.
Signed-off-by: Tuomo Rinne
---
drivers/staging/rtl8192u/r8192U_dm.c | 66 +---
1 file changed, 32 insertions(+), 34 deletions(-)
diff --git
I will get into this with detail after 4.12-rc1.
/Jarkko
On Fri, Apr 28, 2017 at 09:02:15AM -0400, Stefan Berger wrote:
> The purpose of this series of patches is to enable the passing of the locality
> a command is executing in to a TPM emulator. To enable this we introduce a new
> flag for the
On Sat, 2017-04-29 at 11:06 -0700, Paul E. McKenney wrote:
> If someone will either repost a fresh series or point me at exactly
> the set of patches to use, I will run it through rcutorture again.
Patchlet is against x86-tip/master.today.
-Mike
On Fri, Apr 28, 2017 at 06:03:14PM -0400, Tejun Heo wrote:
> On Tue, Apr 18, 2017 at 10:12:16AM +0100, Andre Przywara wrote:
> > Yeah, so I stack-dumped on the zero allocations and indeed they are
> > called from cleanup functions:
> > drivers/pinctrl/pinmux.c:pinmux_generic_free_functions():
> >
On 04/26/17 14:29, Greg Hackmann wrote:
> On 04/26/2017 02:24 PM, h...@zytor.com wrote:
This really feels like a "fix your compiler" issue.
>>>
>>> We already use the other forms, what's so bad about adding mul too?
>>> And if this lets us build under clang, all the better.
>>>
>>> -Kees
>>
From: Colin Ian King
trivial fix to spelling mistakes in dev_info and scmd_printk
messages. Also join lines on split literal string to clean up
checkpatch warning.
Signed-off-by: Colin Ian King
---
drivers/scsi/megaraid/megaraid_sas_base.c
On Sat, Apr 29, 2017 at 04:17:18PM -0700, Andy Lutomirski wrote:
> On Sat, Apr 29, 2017 at 3:04 PM, Al Viro wrote:
> > New AT_... flag - AT_NO_JUMPS
> >
> > Semantics: pathname resolution must not involve
> > * traversals of absolute symlinks
> > *
Remove unused check and variables after:
drm/rockchip: Set line flag config register in vop_crtc_enable
Signed-off-by: Jeffy Chen
---
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git
On 4/28/2017 9:37 PM, Geliang Tang wrote:
> Use setup_timer() instead of init_timer() to simplify the code.
>
> Signed-off-by: Geliang Tang
> ---
> Changes in v2:
> - use setup_timer() in i40iw_terminate_start_timer().
I already applied your previous patch and did the
On Sat, 8 Apr 2017 20:53:18 +0100
Sergei Trofimovich wrote:
> Starting from gcc-5.4+ gcc generates MLX
> instructions in more cases to refer local
> symbols:
> https://gcc.gnu.org/PR60465
>
> That caused ia64 module loader to choke
> on such instructions:
> fuse:
Hi,
On Sat, Apr 29, 2017 at 06:40:53PM +0900, Tomohiro Yoshidomi wrote:
> PSX pads can be connected directly to the SPI bus.
>
> Signed-off-by: Tomohiro Yoshidomi
Thank you very much for making requested changes and your patience. I
think we just need a few finishing
Hi,
On Sat, Apr 29, 2017 at 05:34:28PM +0300, Alex A. Mihaylov wrote:
> Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge
> monitor with M5 Fuel Gauge algorithm
>
> Slave device provide software layer for access to internal registers
> MAX17211/MAX17215 chip.
Please convert
On Sat, 2017-04-29 at 22:17 +0530, Dhiru Kholia wrote:
> This coding style issue was found by checkpatch.pl script. Using
> __func__ instead of hardcoded function name should help in future
> refactoring of this code.
>
> Signed-off-by: Dhiru Kholia
> ---
>
On Sat, Apr 29, 2017 at 06:06:40PM +0200, Mike Galbraith wrote:
> Note: there is more. With this applied, my desktop box will no longer
> reproduce when booted to init 3 with nowatchdog on the command line.
> My 8 socket DL980 OTOH still will, though it takes longer, and is
> seemingly no
Hi Tuomo,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on next-20170428]
[cannot apply to v4.11-rc8]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Note: there is more. With this applied, my desktop box will no longer
reproduce when booted to init 3 with nowatchdog on the command line.
My 8 socket DL980 OTOH still will, though it takes longer, and is
seemingly no longer interested in following up with a permanent RCU
stall after the tsc
Hi Alexey
25.03.2017, 20:08, "Alexey Ignatov" :
> struct w1_gpio_platform_data was allocated using devres when using
> device tree. Then it was assigned to dev.platform_data, which leaded
> to double free on device removal by devres and by direct
> kfree(platform_data) in
* Dan Williams wrote:
> Kirill points out that the calls to {get,put}_dev_pagemap() can be
> removed from the mm fast path if we take a single get_dev_pagemap()
> reference to signify that the page is alive and use the final put of the
> page to drop that reference.
>
Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge
monitor with M5 Fuel Gauge algorithm
This driver provide userspace access to MAX17211/MAX17215 data with
power_supply class drivers.
---
drivers/power/supply/Kconfig| 8 +
drivers/power/supply/Makefile |
Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge
monitor with M5 Fuel Gauge algorithm
Slave device provide software layer for access to internal registers
MAX17211/MAX17215 chip.
---
drivers/w1/slaves/Kconfig | 12
drivers/w1/slaves/Makefile | 1 +
Maxim Semiconductor MAX17211/MAX17215 is M5 Fuel Gauge Monitor with
OneWire (W1) interface.
This patch provide W1 family, MAX17211x slave device and MAX17211x
battery power_supply class device.
Alex A. Mihaylov (2):
Add support for OneWire (W1) devices family 0x26 (MAX17211/MAX17215)
Add
Fixes the following sparse warnings:
drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23: warning: invalid
assignment: |=
drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23:left side has type
restricted __le32
drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23:right side has type int
On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote:
>
> While dpaa2_fd.simple structure fields are marked __leXX,
> corresponding cpu_to_leXX / leXX_to_cpu conversions are missing.
>
> While here, fix dpaa2_fd_{get,set}_bpid such that BMT, IVP bits
> sharing the 16-bit
Hi,
Please make sure you Cc the relevant people / mailing lists. You
can use ./scripts/get_maintainer.pl to find out who should receive
the patches.
On Sat, Apr 29, 2017 at 05:34:29PM +0300, Alex A. Mihaylov wrote:
> Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge
> monitor
On 4/29/2017 7:32 PM, Stuart Yoder wrote:
> On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote:
>>
>> While dpaa2_fd.simple structure fields are marked __leXX,
>> corresponding cpu_to_leXX / leXX_to_cpu conversions are missing.
>>
>> While here, fix dpaa2_fd_{get,set}_bpid
On Thu, Apr 27, 2017 at 01:07:07PM +0200, Arnd Bergmann wrote:
> The names in the MODULE_DEVICE_TABLE and the actual array don't match:
>
> drivers/crypto/stm32/stm32_crc32.c:309:21: error: 'sti_dt_ids' undeclared
> here (not in a function); did you mean 'stm32_dt_ids'?
>
> This changes the
Sparse spits out a warnings about __le16 and unsigned short assignment.
Change the type of size and event members of struct hostif_hdr
to __le16 and correct conversion to the proper cpu type.
Signed-off-by: Cezary Gapinski
---
drivers/staging/ks7010/ks7010_sdio.c | 10
Hi Sean,
On 04/28/2017 11:03 PM, Sean Paul wrote:
On Fri, Apr 28, 2017 at 03:37:47PM +0800, Jeffy Chen wrote:
We need to set vop config done after update line flag config, it's a
new requirement for chips newer than rk3368.
Since we would only use line flag irq for vact_end, let's move it to
2017-04-29 11:16 GMT+03:00 Matwey V. Kornilov :
> 2017-04-28 16:30 GMT+03:00 Bin Liu :
>> On Fri, Apr 28, 2017 at 04:15:09PM +0300, Matwey V. Kornilov wrote:
>>> 2017-04-28 15:43 GMT+03:00 Bin Liu :
>>> > On Fri, Apr 28, 2017 at 03:13:55PM +0300,
On Sat, Apr 29, 2017 at 03:47:36AM +0100, Al Viro wrote:
> On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote:
> > On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote:
> > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote:
> > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400,
This coding style issue was found by checkpatch.pl script. Using
__func__ instead of hardcoded function name should help in future
refactoring of this code.
Signed-off-by: Dhiru Kholia
---
drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +-
1 file changed, 1
The current test works only for a single patch context as it is
done in the foreach ($rawlines) loop that precedes the loop where
the actual $context_function variable is used.
'
Move the set of $context_function into the foreach (@lines) loop
where it is useful for each patch context.
Dear Beloved,
You were chosen to receive my Cash Grant Donation of £2,000,000 GBP. Do contact
me for details.
Regards,
Mrs. Anita Eric Rubenstein
Kirill Tkhai writes:
> On 27.04.2017 19:07, Eric W. Biederman wrote:
>> Kirill Tkhai writes:
>>
>>> On 27.04.2017 18:15, Eric W. Biederman wrote:
Kirill Tkhai writes:
> On implementing of nested pid namespaces
At Fri, 28 Apr 2017 15:34:06 +0200,
Paolo Bonzini wrote:
>
>
>
> On 27/04/2017 02:42, Satoru Takeuchi wrote:
> > At Wed, 26 Apr 2017 18:58:27 +0200,
> >> On 26/04/2017 13:47, Satoru Takeuchi wrote:
> >>> OK, here it is.
> >>
> >> It looks like the cause is that AMD has removed TBM instructions
Hey,
On Sat, 2017-04-29 at 11:16 -0700, Dmitry Torokhov wrote:
> "Say Y here if you wish to connect PSX (PS1/2) pad via SPI
> interface."
It should say "PlayStation 1/2 joypads". Using "Play Station" is
incorrect, PSX is a code name so you could mention it in between
brackets. Saying "pads" is
From: Colin Ian King
trivial fix to spelling mistake in message.
Signed-off-by: Colin Ian King
---
kernel/trace/trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index
From: Colin Ian King
trivial fix to spelling mistake in dev_warn message,
"ali_capture_preapre" should be "ali_capture_prepare"
Signed-off-by: Colin Ian King
---
sound/pci/ali5451/ali5451.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Colin Ian King
trivial fix to spelling mistakes in dev_info and scmd_printk
messages. Also join lines on split literal string to clean up
checkpatch warning.
Signed-off-by: Colin Ian King
---
drivers/scsi/megaraid/megaraid_sas_base.c
From: Colin Ian King
trivial fix to spelling mistake in an error message.
Signed-off-by: Colin Ian King
---
tools/virtio/virtio_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/virtio/virtio_test.c
__printf validation adds format and argument validation.
Fix the various broken format/argument mismatches.
Signed-off-by: Joe Perches
---
v2: bah, now without unrelated changes to other staging files...
I'm not at all sure all the modifications are appropriate.
Some maybe
It is pointless and confusing to allow a pid namespace hierarchy and
the user namespace hierarchy to get out of sync. The owner of a child
pid namespace should be the owner of the parent pid namespace or
a descendant of the owner of the parent pid namespace.
Otherwise it is possible to
This patch simply uses the changes introduced in previous patches and migrates
apollo, ltlk, audptr, decext, spkout and dectlk. Migrations are straightforward
function pointer updates.
Signed-off by: Okash Khawaja
Reviewed-by: Samuel Thibault
This patch adds further TTY-based functionality, specifically implementation
of send_xchar and tiocmset methods, and input. send_xchar and tiocmset
methods simply delegate to corresponding TTY operations.
For input, it implements the receive_buf2 callback in tty_ldisc_ops of
speakup's ldisc. If a
On Fri 28 Apr 10:42 PDT 2017, Rob Herring wrote:
> On Sat, Apr 22, 2017 at 10:35:17AM -0700, Bjorn Andersson wrote:
> > This adds the binding for describing shared memory buffers for
> > implementing the remote filesystem protocol.
> >
> > Signed-off-by: Bjorn Andersson
On Fri 28 Apr 15:02 PDT 2017, Jordan Crouse wrote:
> On Fri, Apr 28, 2017 at 12:13:52PM +0300, Stanimir Varbanov wrote:
> > +int venus_boot(struct device *parent, struct device *fw_dev)
> > +{
> > + const struct firmware *mdt;
> > + phys_addr_t mem_phys;
> > + ssize_t fw_size;
> > +
On Sat, Apr 29, 2017 at 11:51:40AM -0400, Dave Jones wrote:
> > > > Gyah... It's a bloody dumb braino in iov_iter_revert() for
> pipe-backed
> > > > ones. Sorry, the oneliner below should fix it.
> > >
> > > 5 hrs in, looking good so far.
> >
> > Mind your Tested-by on the fix?
>
>
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> It is pointless and confusing to allow a pid namespace hierarchy and
> the user namespace hierarchy to get out of sync. The owner of a child
> pid namespace should be the owner of the parent pid namespace or
> a descendant of the owner of
On Sat, Apr 29, 2017 at 08:20:33PM +0200, Mike Galbraith wrote:
> On Sat, 2017-04-29 at 11:06 -0700, Paul E. McKenney wrote:
>
> > If someone will either repost a fresh series or point me at exactly
> > the set of patches to use, I will run it through rcutorture again.
>
> Patchlet is against
New AT_... flag - AT_NO_JUMPS
Semantics: pathname resolution must not involve
* traversals of absolute symlinks
* traversals of procfs-style symlinks
* traversals of mountpoints (including bindings, referrals, etc.)
* traversal of .. in the starting point of
On Sat, Apr 29, 2017 at 3:04 PM, Al Viro wrote:
> New AT_... flag - AT_NO_JUMPS
>
> Semantics: pathname resolution must not involve
> * traversals of absolute symlinks
> * traversals of procfs-style symlinks
> * traversals of mountpoints (including
1 - 100 of 320 matches
Mail list logo