similar to: [PATCH stable-only] virtio-net: fix build on m68k and sparc64

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

On Wed, Jan 15, 2014 at 9:46 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: >> On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > As a result of backporting a bugfix, virtio_net started passing void * >> > to page_address, assuming that it will get

On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > As a result of backporting a bugfix, virtio_net started passing void * > to page_address, assuming that it will get silently converted to struct > page *. But this does not happen on architectures where page_address is > a macro, the result is build failure as the macro tries to dereference >

On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote: > On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > virtio 1.0 makes all memory structures LE, so > > we need APIs to conditionally do a byteswap on BE > > architectures. > > > > To make it easier to check code statically, > > add virtio specific types

On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote: > On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > virtio 1.0 makes all memory structures LE, so > > we need APIs to conditionally do a byteswap on BE > > architectures. > > > > To make it easier to check code statically, > > add virtio specific types

Hi Jason, On Thu, Apr 9, 2020 at 6:04 AM Linux Kernel Mailing List <linux-kernel at vger.kernel.org> wrote: > Commit: 20c384f1ea1a0bc7320bc445c72dd02d2970d594 > Parent: 5a6b4cc5b7a1892a8d7f63d6cbac6e0ae2a9d031 > Refname: refs/heads/master > Web: https://git.kernel.org/torvalds/c/20c384f1ea1a0bc7320bc445c72dd02d2970d594 > Author: Jason Wang <jasowang

Hi Jason, On Thu, Apr 9, 2020 at 6:04 AM Linux Kernel Mailing List <linux-kernel at vger.kernel.org> wrote: > Commit: 20c384f1ea1a0bc7320bc445c72dd02d2970d594 > Parent: 5a6b4cc5b7a1892a8d7f63d6cbac6e0ae2a9d031 > Refname: refs/heads/master > Web: https://git.kernel.org/torvalds/c/20c384f1ea1a0bc7320bc445c72dd02d2970d594 > Author: Jason Wang <jasowang

Hi Michael, On Tue, Dec 3, 2019 at 9:21 PM Michael S. Tsirkin <mst at redhat.com> wrote: > This allows incrementing the correct timeout statistic without any mess. > Down the road, devices can learn to reset just the specific queue. > > The patch was generated with the following script: [...] > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > ---

On Fri, 30 Nov 2018 14:12:19 -0800 Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com> wrote: > As a maintainer myself (and based on somewhat disturbed feedback from > other maintainers) I can only make the conclusion that nobody knows what > the responsibility part here means. > > I would interpret, if I read it like at lawyer at least, that even for > existing code you

On Wed, Oct 7, 2015 at 1:23 PM, Arnd Bergmann <arnd at arndb.de> wrote: > On Wednesday 07 October 2015 13:04:06 Arnd Bergmann wrote: >> On Wednesday 07 October 2015 11:45:02 Russell King - ARM Linux wrote: >> > On Wed, Oct 07, 2015 at 12:41:21PM +0200, Arnd Bergmann wrote: >> > > The virtgpu driver prints the last_seq variable using the %ld or >> > >

On Wed, Oct 7, 2015 at 1:23 PM, Arnd Bergmann <arnd at arndb.de> wrote: > On Wednesday 07 October 2015 13:04:06 Arnd Bergmann wrote: >> On Wednesday 07 October 2015 11:45:02 Russell King - ARM Linux wrote: >> > On Wed, Oct 07, 2015 at 12:41:21PM +0200, Arnd Bergmann wrote: >> > > The virtgpu driver prints the last_seq variable using the %ld or >> > >

set_dma_ops isn't available on all architectures: make ARCH=um ... drivers/vdpa/vdpa_sim/vdpa_sim.c: In function 'vdpasim_create': >> drivers/vdpa/vdpa_sim/vdpa_sim.c:324:2: error: implicit declaration of function 'set_dma_ops'; did you mean 'set_groups'? +[-Werror=implicit-function-declaration] set_dma_ops(dev, &vdpasim_dma_ops);

set_dma_ops isn't available on all architectures: make ARCH=um ... drivers/vdpa/vdpa_sim/vdpa_sim.c: In function 'vdpasim_create': >> drivers/vdpa/vdpa_sim/vdpa_sim.c:324:2: error: implicit declaration of function 'set_dma_ops'; did you mean 'set_groups'? +[-Werror=implicit-function-declaration] set_dma_ops(dev, &vdpasim_dma_ops);

On Tue, 21 Jan 2025 at 11:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > Hi Dmitry, > > On Tue, Jan 7, 2025 at 12:31?PM Dmitry Baryshkov > <dmitry.baryshkov at linaro.org> wrote: > > On Sat, 14 Dec 2024 15:37:04 +0200, Dmitry Baryshkov wrote: > > > While working on the generic mode_valid() implementation for the HDMI > > > Connector

On Thu, Jan 16, 2025 at 11:03?AM Tomi Valkeinen <tomi.valkeinen at ideasonboard.com> wrote: > On 16/01/2025 10:09, Thomas Zimmermann wrote: > > Am 15.01.25 um 15:20 schrieb Tomi Valkeinen: > > [...] > >> > >> My point is that we have the current UAPI, and we have userspace using > >> it, but we don't have clear rules what the ioctl does with

On Fri, 15 Nov 2013 04:53:18 +0000 Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > .entry.text is a code area which is used for interrupt/syscall > entries, and there are many sensitive codes. > Thus, it is better to prohibit probing on all of such codes > instead of a part of that. > Since some symbols are already registered on kprobe blacklist, > this also

On Fri, 15 Nov 2013 04:53:18 +0000 Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > .entry.text is a code area which is used for interrupt/syscall > entries, and there are many sensitive codes. > Thus, it is better to prohibit probing on all of such codes > instead of a part of that. > Since some symbols are already registered on kprobe blacklist, > this also

Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit?: > On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: >> >> Hi Krzysztof, >> >> On Wed, Jan 8, 2020 at 9:07 AM Geert Uytterhoeven <geert at linux-m68k.org> wrote: >>> On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: >>>>

On Sat, 14 Dec 2024 15:37:04 +0200, Dmitry Baryshkov wrote: > While working on the generic mode_valid() implementation for the HDMI > Connector framework I noticed that unlike other DRM objects > drm_connector accepts non-const pointer to struct drm_display_mode, > while obviously mode_valid() isn't expected to modify the argument. > > Mass-change the DRM framework code to