qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
	Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
	Manish Mishra <manish.mishra@nutanix.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 1/5] io: Add support for MSG_PEEK for socket channel
Date: Thu, 15 Dec 2022 12:35:26 -0500	[thread overview]
Message-ID: <Y5ta3jGHhN0nrIf6@x1n> (raw)
In-Reply-To: <Y5rrmRyhRjEiHtAe@redhat.com>

On Thu, Dec 15, 2022 at 09:40:41AM +0000, Daniel P. Berrangé wrote:
> On Wed, Dec 14, 2022 at 04:30:48PM -0500, Peter Xu wrote:
> > On Wed, Dec 14, 2022 at 09:14:09AM +0000, Daniel P. Berrangé wrote:
> > > On Tue, Dec 13, 2022 at 04:38:46PM -0500, Peter Xu wrote:
> > > > From: "manish.mishra" <manish.mishra@nutanix.com>
> > > > 
> > > > MSG_PEEK reads from the peek of channel, The data is treated as
> > > > unread and the next read shall still return this data. This
> > > > support is currently added only for socket class. Extra parameter
> > > > 'flags' is added to io_readv calls to pass extra read flags like
> > > > MSG_PEEK.
> > > > 
> > > > Reviewed-by: Daniel P. Berrang?? <berrange@redhat.co
> > > > Suggested-by: Daniel P. Berrang?? <berrange@redhat.com
> > > 
> > > The last letter of my name has been mangled - whatever tools used
> > > to pull in manish's patches seem to not be UTF-8 clean.
> > > 
> > > Also the email addr isn't terminated, but that was pre-existing
> > > in manish's previous posting.
> > 
> > I'll fix at least the latter in my next post, sorry.
> > 
> > For the 1st one - I am still looking at what went wrong.
> > 
> > Here from the web interfaces it all looks good (besides the wrong
> > ending..), e.g. on lore or patchew:
> > 
> > https://lore.kernel.org/all/20221213213850.1481858-2-peterx@redhat.com/
> > https://patchew.org/QEMU/20221213213850.1481858-1-peterx@redhat.com/20221213213850.1481858-2-peterx@redhat.com/
> > 
> > It also looks good with e.g. Gmail webclient.
> > 
> > Then I digged into the email headers and I found that comparing to Manish's
> > original message, the patches I posted has one more line of "Content-type":
> > 
> >   Content-Type: text/plain; charset="utf-8"
> >   Content-type: text/plain
> >   https://patchew.org/QEMU/20221213213850.1481858-2-peterx@redhat.com/mbox
> > 
> > While Manish's patch only has one line:
> > 
> >   Content-Type: text/plain; charset="utf-8"
> >   https://patchew.org/QEMU/20221123172735.25181-2-manish.mishra@nutanix.com/mbox
> 
> Don't trust what is shown by patchew, as that's been through many
> hops.
> 
> The copy I receieved came directly to me via CC, so didn't hit mailman,
> nor patchew, and that *only* has  "Content-type: text/plain".  So the
> extra Content-type line with utf8 must have been added either by
> mailman or patchew.
> 
> So it probably looks like a config problem in the tool you use to send
> the patches originally.

Ouch... for misterious reasons I had one line in .gitconfig:

177 [format]
178         headers = "Content-type: text/plain"

And that'll also affect git-publish too...  I have it dropped now.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2022-12-15 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 21:38 [PATCH 0/5] migration: Fix disorder of channel creations Peter Xu
2022-12-13 21:38 ` [PATCH 1/5] io: Add support for MSG_PEEK for socket channel Peter Xu
2022-12-14  9:14   ` Daniel P. Berrangé
2022-12-14 21:30     ` Peter Xu
2022-12-15  9:40       ` Daniel P. Berrangé
2022-12-15 17:35         ` Peter Xu [this message]
2022-12-16 10:40           ` manish.mishra
2022-12-16 14:30             ` Peter Xu
2022-12-13 21:38 ` [PATCH 2/5] migration: check magic value for deciding the mapping of channels Peter Xu
2022-12-14  9:15   ` Daniel P. Berrangé
2022-12-13 21:38 ` [PATCH 3/5] migration: Rework multi-channel checks on URI Peter Xu
2022-12-13 21:38 ` [PATCH 4/5] migration: Add a semaphore to count PONGs Peter Xu
2022-12-13 21:38 ` [PATCH 5/5] migration: Postpone postcopy preempt channel to be after main Peter Xu

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=Y5ta3jGHhN0nrIf6@x1n \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lsoaresp@redhat.com \
    --cc=manish.mishra@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).