virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, farman@linux.ibm.com,
	Janosch Frank <frankja@linux.ibm.com>,
	gor@linux.ibm.com, hca@linux.ibm.com, cohuck@redhat.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	virtualization@lists.linux-foundation.org, pasic@linux.ibm.com,
	kvm@vger.kernel.org, Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH AUTOSEL 6.2 05/16] s390/virtio: sort out physical vs virtual pointers usage
Date: Tue, 14 Mar 2023 13:26:32 -0400	[thread overview]
Message-ID: <ZBCuSCIRrtdQQTeM@sashalap> (raw)
In-Reply-To: <167809840006.10483.605220541481258700@t14-nrb.local>

On Mon, Mar 06, 2023 at 11:26:40AM +0100, Nico Boehr wrote:
>Hi Sasha, s390 maintainers,
>
>Quoting Sasha Levin (2023-03-05 14:51:56)
>> From: Alexander Gordeev <agordeev@linux.ibm.com>
>>
>> [ Upstream commit 5fc5b94a273655128159186c87662105db8afeb5 ]
>>
>> This does not fix a real bug, since virtual addresses
>> are currently indentical to physical ones.
>
>not sure if it is appropriate to pick for stable, since it does not fix a bug currently.
>
>Alexander, Janosch, your opinion?

I'll drop it, thanks!

-- 
Thanks,
Sasha
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

      parent reply	other threads:[~2023-03-14 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230305135207.1793266-1-sashal@kernel.org>
2023-03-05 13:51 ` [PATCH AUTOSEL 6.2 05/16] s390/virtio: sort out physical vs virtual pointers usage Sasha Levin
     [not found]   ` <167809840006.10483.605220541481258700@t14-nrb.local>
2023-03-14 17:26     ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZBCuSCIRrtdQQTeM@sashalap \
    --to=sashal@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).