et me try reply-all this time. :)
Acked-by: John Stultz
thanks
-john
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
On Mon, Sep 17, 2018 at 12:25 PM, Andy Lutomirski wrote:
> On Fri, Sep 14, 2018 at 5:50 AM, Thomas Gleixner wrote:
>> The code flow for the vclocks is convoluted as it requires the vclocks
>> which can be invalidated separately from the vsyscall_gtod_data sequence to
>> store the fact in a separa
On Thu, Nov 1, 2018 at 3:15 PM, Liam Mark wrote:
> Based on the suggestions from Laura I created a first draft for a change
> which will attempt to ensure that uncached mappings are only applied to
> ION memory who's cache lines have been cleaned.
> It does this by providing cached mappings (for u
t; > > the current situation. Because of this problem, just drop the in-kernel
> > > copy of the ion code now, as it's not used, and is only causing problems
> > > for everyone involved.
> > >
> > > Cc: "Arve Hjønnevåg"
> > >
On Mon, Jan 28, 2019 at 1:44 PM Andrew F. Davis wrote:
>
> Previously the heap to allocate from was selected by a mask of allowed
> heap types. This may have been done as a primitive form of constraint
> solving, the first heap type that matched any set bit of the heap mask
> was allocated from, u
On Fri, Feb 15, 2019 at 11:22 AM Andrew F. Davis wrote:
>
> On 2/15/19 1:01 PM, John Stultz wrote:
> > On Fri, Feb 15, 2019 at 2:51 AM Brian Starkey wrote:
> >> On Thu, Feb 14, 2019 at 09:38:29AM -0800, John Stultz wrote:
> >>> 2) For patches that cause ABI br
On Fri, Feb 15, 2019 at 12:52 PM Andrew F. Davis wrote:
> On 2/15/19 1:58 PM, John Stultz wrote:
> > So yea, I don't think we should tie our hands in reworking the
> > interfaces, but it would be nice to avoid having subtle ABI changes
> > that don't have clear wa
On Fri, Feb 15, 2019 at 2:51 AM Brian Starkey wrote:
>
> Hi John,
>
> On Thu, Feb 14, 2019 at 09:38:29AM -0800, John Stultz wrote:
> >
> [snip]
>
> > Some thoughts, as this ABI break has the potential to be pretty painful.
> >
> > 1) Unfortunately
quot; and that people rely on this interface now.
> >> Well, "code outside of the kernel tree" relies on this, which is not ok,
> >> but the "soon" people keep insisting on it...
> >>
> >> Odds are I should just delete all of ION, as there h
perror("[-] open /dev/ion");
> > return 1;
> > }
> >
> > while (1) {
> > printf("iter %lu\n", i);
> > ioctl(fd, ION_IOC_ALLOC, &data);
> > i++;
>
On Wed, Jul 24, 2019 at 1:18 PM John Stultz wrote:
>
> On Wed, Jul 24, 2019 at 12:36 PM Laura Abbott wrote:
> >
> > On 7/17/19 12:31 PM, Alexander Popov wrote:
> > > Hello!
> > >
> > > The syzkaller [1] has a trouble with fuzzing the Linux
On Tue, Dec 12, 2017 at 10:25 PM, kbuild test robot
wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> staging-linus
> head: d98e6dbf42f73101128885a1e0ae672cd92b2e1a
> commit: d98e6dbf42f73101128885a1e0ae672cd92b2e1a [3/3] staging: ion: Fix
> ion_cma_heap all
On Wed, Feb 22, 2017 at 4:01 AM, Michal Hocko wrote:
> From: Michal Hocko
>
> Lowmemory killer is sitting in the staging tree since 2008 without any
> serious interest for fixing issues brought up by the MM folks. The main
> objection is that the implementation is basically broken by design:
>
On Tue, Apr 14, 2020 at 7:28 AM Greg Kroah-Hartman
wrote:
>
> On Tue, Apr 14, 2020 at 04:18:47PM +0200, Ørjan Eide wrote:
> > Only sync the sg-list of an Ion dma-buf attachment when the attachment
> > is actually mapped on the device.
> >
> > dma-bufs may be synced at any time. It can be reached f
On Tue, Apr 14, 2020 at 9:11 AM Ørjan Eide wrote:
>
> On Tue, Apr 14, 2020 at 04:28:10PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 14, 2020 at 04:18:47PM +0200, �rjan Eide wrote:
> > > Only sync the sg-list of an Ion dma-buf attachment when the attachment
> > > is actually mapped on the dev
On Mon, Apr 20, 2020 at 1:22 AM Christian Brauner
wrote:
> On Thu, Apr 16, 2020 at 12:25:08PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 14, 2020 at 09:41:31PM -0700, John Stultz wrote:
> > > But I do think we can mark it as deprecated and let folks know that
> >
On 02/16/2014 04:00 PM, Tomas Winkler wrote:
> Looks like phys_addr_t's are fully plumbed in the kernel.
This needs a better commit description.
Also you should include Colin and the rest of the Android kernel folks
(cc'ed in this mail) so they can review and hopefully provide acks.
thanks
-john
On 04/16/2014 07:39 AM, Joe Perches wrote:
> On Wed, 2014-04-16 at 23:27 +0900, Seunghun Lee wrote:
>> This patch fix checkpatch.pl warnings and errors.
> []
>> diff --git a/drivers/staging/android/uapi/binder.h
>> b/drivers/staging/android/uapi/binder.h
> []
>> @@ -169,7 +169,7 @@ struct binder_p
On Mon, May 8, 2017 at 1:43 PM, Dmitry Torokhov
wrote:
> If binder_get_thread() fails to give us a thread data, we should avoid
> dereferencing a NULL pointer and return POLLERR instead.
>
> Signed-off-by: Dmitry Torokhov
Pulling Todd Kjos in on this too.
-john
> ---
> drivers/android/binder.c
On Thu, Jun 1, 2017 at 5:26 PM, Yan, Zheng wrote:
> On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann wrote:
>> On Thu, Jun 1, 2017 at 11:56 AM, Yan, Zheng wrote:
>>> On Sat, Apr 8, 2017 at 8:57 AM, Deepa Dinamani
>>> wrote:
>>
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index
On Wed, Jan 4, 2017 at 9:24 AM, Vitaly Kuznetsov wrote:
> do_settimeofday() is deprecated, use do_settimeofday64() instead.
>
> Signed-off-by: Vitaly Kuznetsov
Looks sane.
Acked-by: John Stultz
thanks
-john
___
devel mailin
On Wed, Jan 4, 2017 at 9:24 AM, Vitaly Kuznetsov wrote:
> While do_adjtimex() is available to userspace via adjtimex syscall it is
> not available to modules which may want to implement in-kernel 'NTP
> clients'. Hyper-V hv_utils is going to be the first one.
>
> Signed-off-by: Vitaly Kuznetsov
>
On Wed, Jan 4, 2017 at 9:24 AM, Vitaly Kuznetsov wrote:
> If we happen to receive interrupts during hv_set_host_time() execution
> our adjustments may get inaccurate. Make the whole function atomic.
> Unfortunately, we can's call do_settimeofday64() with interrupts
> disabled as some cross-CPU wor
On Wed, Jan 4, 2017 at 9:24 AM, Vitaly Kuznetsov wrote:
> With TimeSync version 4 protocol support we started updating system time
> continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
> there is a time sample from the host which triggers do_settimeofday[64]().
> While the t
On Thu, Jan 15, 2015 at 9:03 AM, Michal Hocko wrote:
> On Mon 12-01-15 21:49:14, Chintan Pandya wrote:
>> The global shrinker will invoke lowmem_shrink in a loop.
>> The loop will be run (total_scan_pages/batch_size) times.
>> The default batch_size will be 128 which will make
>> shrinker invoking
On Fri, Feb 27, 2015 at 8:30 AM, Andrey Ryabinin wrote:
> binder_update_page_range() initializes only addr and size
> fields in 'struct vm_struct tmp_area;' and passes it to
> map_vm_area().
>
> Before 71394fe50146 ("mm: vmalloc: add flag preventing guard hole allocation")
> this was because map_v
PAGE_SIZE, PAGE_KERNEL, page);
> + flush_cache_vmap((unsigned long)page_addr,
> + (unsigned long)page_addr + PAGE_SIZE);
> + if (ret != 1) {
> pr_err
On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote:
> The binder allocator assumes that the thread that
> called binder_open will never die for the lifetime of
> that proc. That thread is normally the group_leader,
> however it may not be. Use the group_leader instead
> of current.
>
> Signed-off-b
On Mon, Jul 24, 2017 at 2:00 PM, John Stultz wrote:
> On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote:
>> The binder allocator assumes that the thread that
>> called binder_open will never die for the lifetime of
>> that proc. That thread is normally the group_leader,
>
On Mon, Jul 24, 2017 at 2:23 PM, Greg Kroah-Hartman
wrote:
> On Mon, Jul 24, 2017 at 02:00:45PM -0700, John Stultz wrote:
>> On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote:
>> > The binder allocator assumes that the thread that
>> > called binder_open will ne
up_leader)
> return -EINVAL;
>
> if ((vma->vm_end - vma->vm_start) > SZ_4M)
Tested-by: John Stultz
As Amit already confirmed, this resolves the wifi and bluetooth
regression I was seeing with Android using 4.13-rc2.
Though I've not seen it show up i
On Tue, Aug 8, 2017 at 11:08 AM, Greg KH wrote:
> On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote:
>> On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote:
>> > Commit c4ea41ba195d ("binder: use group leader instead of open thread")'
>> > w
On Tue, Aug 8, 2017 at 11:08 AM, Greg KH wrote:
> On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote:
>> On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote:
>> > Commit c4ea41ba195d ("binder: use group leader instead of open thread")'
>> > w
On Tue, Aug 22, 2017 at 7:34 PM, Jisheng Zhang wrote:
> On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote:
>
>> On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote:
>> > As noted in commit d0bdff0db809 ("staging: Fix build issues with new
>> > binder API"), we can add back the choice for
On Tue, Aug 22, 2017 at 7:56 PM, John Stultz wrote:
> On Tue, Aug 22, 2017 at 7:34 PM, Jisheng Zhang wrote:
>> On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote:
>>
>>> On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote:
>>> > As noted in commit d0bd
On Tue, Aug 22, 2017 at 8:01 PM, Jisheng Zhang wrote:
> On Tue, 22 Aug 2017 19:57:04 -0700 John Stultz wrote:
>
>> On Tue, Aug 22, 2017 at 7:56 PM, John Stultz wrote:
>> > On Tue, Aug 22, 2017 at 7:34 PM, Jisheng Zhang wrote:
>> >> On Tue, 22 Aug
On Tue, May 27, 2014 at 11:52 AM, Greg Kroah-Hartman
wrote:
> On Mon, May 26, 2014 at 07:04:53PM +0900, Heesub Shin wrote:
>> For aesthetics and readability, rename goto labels, remove
>> useless code lines, and clarify function return type.
>>
>> Signed-off-by: Heesub Shin
>> ---
>> drivers/sta
saw no changes in the
results on x86_64, i386(compat), and arm. So looks ok there.
Would still be good to have Colin's ack, but here's my qualified
tested-by line...
(Basic Unit)Tested-by: John Stultz
thanks
-john
___
devel mailing
On Thu, Oct 16, 2014 at 5:47 AM, Greg Kroah-Hartman
wrote:
> From: Greg Kroah-Hartman
>
> The Android binder code has been "stable" for many years now. No matter
Well, ignoring the ABI break that landed in the last year. :)
> what comes in the future, we are going to have to support this API,
On Thu, Oct 16, 2014 at 4:12 PM, Greg Kroah-Hartman
wrote:
> On Thu, Oct 16, 2014 at 10:09:04AM -0700, John Stultz wrote:
>> On Thu, Oct 16, 2014 at 5:47 AM, Greg Kroah-Hartman
>> wrote:
>> > From: Greg Kroah-Hartman
>> >
>> > The Android binder code
t;> To: Thomas Shao
>> Cc: gre...@linuxfoundation.org; LKML; de...@linuxdriverproject.org;
>> o...@aepfle.de; a...@canonical.com; jasow...@redhat.com; KY Srinivasan;
>> John Stultz; Richard Cochran
>> Subject: Re: [PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for
>> do_adjtimex()
&
On Fri, Jul 3, 2020 at 12:03 AM Greg Kroah-Hartman
wrote:
> On Tue, Apr 21, 2020 at 10:05:44AM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 20, 2020 at 01:03:39PM -0700, John Stultz wrote:
> > > The dmabuf heaps have been in an official kernel now for all of three
> >
On Tue, Aug 18, 2020 at 9:26 AM Robin Murphy wrote:
> On 2020-08-18 16:29, Mauro Carvalho Chehab wrote:
> > Em Tue, 18 Aug 2020 15:47:55 +0100
> > Basically, the DT binding has this, for IOMMU:
> >
> >
> > smmu_lpae {
> > compatible = "hisilicon,smmu-lpae";
> > };
> >
> >
On Wed, Aug 19, 2020 at 8:31 AM Laurent Pinchart
wrote:
> On Wed, Aug 19, 2020 at 05:21:20PM +0200, Sam Ravnborg wrote:
> > On Wed, Aug 19, 2020 at 01:45:28PM +0200, Mauro Carvalho Chehab wrote:
> > > This patch series port the out-of-tree driver for Hikey 970 (which
> > > should also support Hike
driver and
> a few other patches (including a hack to fix a Kernel 5.8
> regression at WiFi ) at:
>
>
> https://gitlab.freedesktop.org/mchehab_kernel/hikey-970/-/commits/master
>
>
> Chen Feng (1):
> staging: hikey9xx: Add hisilicon DRM driver for hikey960/970
>
>
On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab
wrote:
> So, IMO, the best is to keep it on staging for a while, until those
> remaining bugs gets solved.
>
> I added this series, together with the regulator driver and
> a few other patches (including a hack to fix a Kernel 5.8
> regression
On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab
wrote:
> @@ -376,7 +355,7 @@ static int kirin_drm_platform_resume(struct
> platform_device *pdev)
> }
>
> static const struct of_device_id kirin_drm_dt_ids[] = {
> - { .compatible = "hisilicon,hi3660-dpe",
> + { .compatible = "hi
On Wed, Aug 19, 2020 at 2:36 PM John Stultz wrote:
>
> On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab
> wrote:
> > So, IMO, the best is to keep it on staging for a while, until those
> > remaining bugs gets solved.
> >
> > I added this series, together wi
On Wed, Aug 19, 2020 at 7:01 PM John Stultz wrote:
>
> On Wed, Aug 19, 2020 at 2:36 PM John Stultz wrote:
> >
> > On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab
> > wrote:
> > > So, IMO, the best is to keep it on staging for a while, until those
On Thu, Aug 20, 2020 at 1:23 AM Mauro Carvalho Chehab
wrote:
>
> (added c/c Rob Herring)
>
> Em Wed, 19 Aug 2020 18:53:06 -0700
> John Stultz escreveu:
>
> > On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab
> > wrote:
> > > @@ -376,7 +355,7 @@ stat
On Thu, Aug 27, 2020 at 10:17 AM Greg Kroah-Hartman
wrote:
> On Thu, Aug 27, 2020 at 10:31:41PM +0530, Amit Pundir wrote:
> > I don't know what is the right thing to do here. I just want to
> > highlight that AOSP's audio (codec2) HAL depends on the ION system
> > heap and it will break AOSP for p
On Fri, Aug 28, 2020 at 1:05 AM Greg Kroah-Hartman
wrote:
>
> On Thu, Aug 27, 2020 at 11:54:12AM -0700, John Stultz wrote:
> > On Thu, Aug 27, 2020 at 10:17 AM Greg Kroah-Hartman
> > wrote:
> > > On Thu, Aug 27, 2020 at 10:31:41PM +0530, Amit Pundir wrote:
> > &
52 matches
Mail list logo
