On Thu, 18 Jul 2019 at 12:10, Laurent Vivier wrote:
> Do you think we should defer the whole patch after 4.1 release?
> But then the build of 4.1 will be broken with 5.2+ kernel
I think this is worth putting into 4.1; but we should
look at maybe tidying up the loose ends for 4.2.
thanks
-- PMM
Le 18/07/2019 à 13:00, Peter Maydell a écrit :
> On Thu, 18 Jul 2019 at 11:40, Laurent Vivier wrote:
>> It comes from linux-user/syscall.c:
>>
>> 6328 /* automatic consistency check if same arch */
>> 6329 #if (defined(__i386__) && defined(TARGET_I386) &&
>> defined(TARGET_ABI32)) || \
On Thu, 18 Jul 2019 at 11:40, Laurent Vivier wrote:
> It comes from linux-user/syscall.c:
>
> 6328 /* automatic consistency check if same arch */
> 6329 #if (defined(__i386__) && defined(TARGET_I386) &&
> defined(TARGET_ABI32)) || \
> 6330 (defined(__x86_64__) && defined(TARGET_X86
Le 18/07/2019 à 12:20, Peter Maydell a écrit :
> On Wed, 17 Jul 2019 at 15:55, Laurent Vivier wrote:
>>
>> The following changes since commit a1a4d49f60d2b899620ee2be4ebb991c4a90a026:
>>
>> Merge remote-tracking branch
>> 'remotes/philmd-gitlab/tags/pflash-next-20190716' into staging (2019-07-1
On Wed, 17 Jul 2019 at 15:55, Laurent Vivier wrote:
>
> The following changes since commit a1a4d49f60d2b899620ee2be4ebb991c4a90a026:
>
> Merge remote-tracking branch
> 'remotes/philmd-gitlab/tags/pflash-next-20190716' into staging (2019-07-16
> 17:02:44 +0100)
>
> are available in the Git repo
The following changes since commit a1a4d49f60d2b899620ee2be4ebb991c4a90a026:
Merge remote-tracking branch
'remotes/philmd-gitlab/tags/pflash-next-20190716' into staging (2019-07-16
17:02:44 +0100)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-for-
