search for: sudipm

...error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE Can you please give me any idea about what the problem might be and how it can be solved. You can see the build log at: https://travis-ci.org/sudipm-mukherjee/parport/jobs/80365425 regards sudip

...error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE Can you please give me any idea about what the problem might be and how it can be solved. You can see the build log at: https://travis-ci.org/sudipm-mukherjee/parport/jobs/80365425 regards sudip

...erted to atomic. And > tbh, it's probably faster if you just submit it to dri-devel, assuming you > have time to work on it. For small drivers we tend to be fairly quick in > getting them into good enough shape. I have received the driver from Teddy and pushed it to https://github.com/sudipm-mukherjee/parport/tree/drm_smi for your first look into it. It is not even building with next-20171130 and has lots of build warnings. I will have to do a lot of work on it before I can even submit it to dri-devel. Time will be the problem, as this is not part of my day job. > > Staging is...

...erted to atomic. And > tbh, it's probably faster if you just submit it to dri-devel, assuming you > have time to work on it. For small drivers we tend to be fairly quick in > getting them into good enough shape. I have received the driver from Teddy and pushed it to https://github.com/sudipm-mukherjee/parport/tree/drm_smi for your first look into it. It is not even building with next-20171130 and has lots of build warnings. I will have to do a lot of work on it before I can even submit it to dri-devel. Time will be the problem, as this is not part of my day job. > > Staging is...

On 30 November 2017 at 23:49, Sudip Mukherjee <sudipm.mukherjee at gmail.com> wrote: > Hi Daniel, > > On Wed, Nov 29, 2017 at 10:56:34AM +0100, Daniel Vetter wrote: >> On Tue, Nov 28, 2017 at 12:30:30PM +0000, Sudip Mukherjee wrote: >> > On Tue, Nov 28, 2017 at 12:32:38PM +0100, Greg KH wrote: >> > > On Tue, Nov...

...ssert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__ > *vq->avail > VRING_AVAIL_ALIGN_SIZE > > Can you please give me any idea about what the problem might be and how > it can be solved. > > You can see the build log at: > https://travis-ci.org/sudipm-mukherjee/parport/jobs/80365425 > > regards > sudip Yes - I think I saw this already. I think the openrisc cross-compiler is broken. VRING_AVAIL_ALIGN_SIZE is 2 *vq->avail is: struct vring_avail { __virtio16 flags; __virtio16 idx; __virtio16 ring[]; }; And...

...rnel.org > Cc: virtualization at lists.linux-foundation.org > Cc: netdev at vger.kernel.org > Cc: linux-kernel at vger.kernel.org > Cc: "Eric W. Biederman" <ebiederm at xmission.com> > Cc: Andrew Morton <akpm at linux-foundation.org> > Cc: Sudip Mukherjee <sudipm.mukherjee at gmail.com> > Cc: "Luis R. Rodriguez" <mcgrof at kernel.org> > Cc: Dominik Brodowski <linux at dominikbrodowski.net> > Signed-off-by: guomin chen <gchen.guomin at gmail.com> > --- > drivers/vhost/vhost.c | 1 + > kernel/exit.c...

...tbh, it's probably faster if you just submit it to dri-devel, assuming you > > have time to work on it. For small drivers we tend to be fairly quick in > > getting them into good enough shape. > > I have received the driver from Teddy and pushed it to > https://github.com/sudipm-mukherjee/parport/tree/drm_smi for your first > look into it. It is not even building with next-20171130 and has lots of > build warnings. I will have to do a lot of work on it before I can even > submit it to dri-devel. > > Time will be the problem, as this is not part of my day jo...

...;dlemoal at kernel.org> Cc: Jean Delvare <jdelvare at suse.com> Cc: Harry Wentland <harry.wentland at amd.com> Cc: Jani Nikula <jani.nikula at linux.intel.com> Cc: Sergey Shtylyov <s.shtylyov at omp.ru> Cc: Jakub Kicinski <kuba at kernel.org> Cc: Sudip Mukherjee <sudipm.mukherjee at gmail.com> Cc: Andrew Jeffery <andrew at codeconstruct.com.au> Cc: "Manoj N. Kumar" <manoj at linux.ibm.com> Cc: "Martin K. Petersen" <martin.petersen at oracle.com> Cc: Alexei Starovoitov <ast at kernel.org> Cc: Steven Rostedt <rostedt...

On Tue, Nov 28, 2017 at 12:32:38PM +0100, Greg KH wrote: > On Tue, Nov 28, 2017 at 11:22:17AM +0100, Daniel Vetter wrote: > > On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > > > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > > > Almost all

On Tue, Nov 28, 2017 at 12:32:38PM +0100, Greg KH wrote: > On Tue, Nov 28, 2017 at 11:22:17AM +0100, Daniel Vetter wrote: > > On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > > > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > > > Almost all

On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > Almost all drivers using remove_conflicting_framebuffers() wrap it with > > the same code. Extract common part from PCI drivers into separate > > remove_conflicting_pci_framebuffers(). > > > > Signed-off-by: Micha? Miros?aw

In the for loop we are allocating the memory for rail everytime but in some cases we use "continue" and in those cases the memory already allocated for rail is leaked and we again allocate new memory for it. Lets free the memory before continuing with the loop. Signed-off-by: Sudip Mukherjee <sudip.mukherjee at codethink.co.uk> ---