On 03/12/19 15:28, Kevin Wolf wrote:
>> * It's possible to argue against this and personally I'm not that
>> convinced by stubs for this scenario. But io_uring.o should be
>> consistent with how things work today with linux-aio.o. If you feel
>> strongly against having stubs then the linux-aio.o
Am 03.12.2019 um 12:16 hat Stefan Hajnoczi geschrieben:
> On Mon, Nov 11, 2019 at 12:13:47PM +0100, Kevin Wolf wrote:
> > Am 25.10.2019 um 18:04 hat Stefan Hajnoczi geschrieben:
> > > From: Aarushi Mehta
> > >
> > > Signed-off-by: Aarushi Mehta
> > > Signed-off-by: Stefan Hajnoczi
> >
> > This
On Mon, Nov 11, 2019 at 12:13:47PM +0100, Kevin Wolf wrote:
> Am 25.10.2019 um 18:04 hat Stefan Hajnoczi geschrieben:
> > From: Aarushi Mehta
> >
> > Signed-off-by: Aarushi Mehta
> > Signed-off-by: Stefan Hajnoczi
>
> This commit message needs to answer at least where these stubs are
> actuall
On Mon, Nov 11, 2019 at 12:13:47PM +0100, Kevin Wolf wrote:
> Am 25.10.2019 um 18:04 hat Stefan Hajnoczi geschrieben:
> > From: Aarushi Mehta
> >
> > Signed-off-by: Aarushi Mehta
> > Signed-off-by: Stefan Hajnoczi
>
> This commit message needs to answer at least where these stubs are
> actuall
Am 25.10.2019 um 18:04 hat Stefan Hajnoczi geschrieben:
> From: Aarushi Mehta
>
> Signed-off-by: Aarushi Mehta
> Signed-off-by: Stefan Hajnoczi
This commit message needs to answer at least where these stubs are
actually used. Aren't all callers protected with #ifdef
CONFIG_LINUX_IO_URING? (And
From: Aarushi Mehta
Signed-off-by: Aarushi Mehta
Signed-off-by: Stefan Hajnoczi
---
MAINTAINERS | 1 +
stubs/Makefile.objs | 1 +
stubs/io_uring.c| 32
3 files changed, 34 insertions(+)
create mode 100644 stubs/io_uring.c
diff --git a/MAINTAINER
