On Wed, 2022-05-25 at 08:32 +0200, Gerd Hoffmann wrote:
> On Tue, May 24, 2022 at 01:49:41PM +0200, Dario Faggioli wrote:
> > Hello! Sorry for bringing up an old thread, but I'd have a question
> > about this series.
> >
> > As far as I can see, the patches were fine, and they were Acked,
> > but
On Tue, May 24, 2022 at 01:49:41PM +0200, Dario Faggioli wrote:
> Hello! Sorry for bringing up an old thread, but I'd have a question
> about this series.
>
> As far as I can see, the patches were fine, and they were Acked, but
> then the series was never committed... Is this correct?
>
> If yes,
Hello! Sorry for bringing up an old thread, but I'd have a question
about this series.
As far as I can see, the patches were fine, and they were Acked, but
then the series was never committed... Is this correct?
If yes, can it be committed (I'm up for rebasing and resending, if it's
necessary)? I
On Tue, Sep 28, 2021 at 05:46:26PM -0300, Jose R. Ziviani wrote:
> This patchset introduces the modinfo_kconfig aiming for a fine-tune
> control of module loading by simply checking Kconfig options during the
> compile time, then generates one modinfo--softmmu.c per target.
>
> The main reason of
This patchset introduces the modinfo_kconfig aiming for a fine-tune
control of module loading by simply checking Kconfig options during the
compile time, then generates one modinfo--softmmu.c per target.
The main reason of this change is to fix problems like:
$ ./qemu-system-s390x -nodefaults -dis
