From: Pavel Begunkov <email@example.com> To: Olivier Langlois <firstname.lastname@example.org>, Jens Axboe <email@example.com>, Steven Rostedt <firstname.lastname@example.org>, Ingo Molnar <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition Date: Wed, 16 Jun 2021 14:53:55 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 6/16/21 2:33 PM, Olivier Langlois wrote: > On Tue, 2021-06-15 at 15:50 -0600, Jens Axboe wrote: >> On 6/15/21 3:48 AM, Pavel Begunkov wrote: >>> On 5/31/21 7:54 AM, Olivier Langlois wrote: >>>> Fix tabulation to make nice columns >>> >>> Reviewed-by: Pavel Begunkov <firstname.lastname@example.org> >> >> I don't have any of the original 1-3 patches, and don't see them on the >> list either. I'd love to apply for 5.14, but... >> >> Olivier, are you getting any errors sending these out?Usually I'd >> expect >> them in my inbox as well outside of the list, but they don't seem to >> have >> arrived there either. >> >> In any case, please resend. As Pavel mentioned, a cover letter is >> always >> a good idea for a series of more than one patch. >> > I do not get any errors but I have noticed too that my emails weren't > accepted by the lists. > > They will accept replies in already existing threads but they won't let > me create new ones. ie: accepting my patches. > > I'll learn how create a cover email and I will resend the series of > patches later today. "--cover-letter" to "git format-patch" will create a cover template to fill in. Depends on patches, but can be a small description of the series. Regarding resending, Jens already took/applied them today, see a reply to 1/3. You can find them queued at https://git.kernel.dk/cgit/linux-block/log/?h=for-5.14/io_uring > one thing that I can tell, it is that Pavel and you are always > recipients along with the lists for my patches... So you should have a > private copy somewhere in your mailbox... > > The other day, I even got this: > -------- Forwarded Message -------- > From: Mail Delivery System <Mailer-Daemon@cloud48395.mywhc.ca> > To: email@example.com > Subject: Mail delivery failed: returning message to sender > Date: Thu, 10 Jun 2021 11:38:51 -0400 > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) > failed: > > firstname.lastname@example.org > host vger.kernel.org [220.127.116.11] > SMTP error from remote mail server after end of data: > 550 5.7.1 Content-Policy accept-into-freezer-1 msg: > Bayes Statistical Bogofilter considers this message SPAM. BF:<S > 0.9924> In case you disagree, send the ENTIRE message plus this error > message to <email@example.com> ; S230153AbhFJPkq > firstname.lastname@example.org > host vger.kernel.org [18.104.22.168] > SMTP error from remote mail server after end of data: > 550 5.7.1 Content-Policy accept-into-freezer-1 msg: > Bayes Statistical Bogofilter considers this message SPAM. BF:<S > 0.9924> In case you disagree, send the ENTIRE message plus this error > message to <email@example.com> ; S230153AbhFJPkq > > There is definitely something that the list software doesn't like in my > emails but I don't know what... > > I did send an email to firstname.lastname@example.org to tell them about > the problem but I didn't hear back anything from the postmaster... (My > email probably went to the SPAM folder as well!) > -- Pavel Begunkov
prev parent reply other threads:[~2021-06-16 13:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <60be7e31.1c69fb81.a8bfb.2e54SMTPIN_ADDED_MISSING@mx.google.com> 2021-06-15 9:48 ` Pavel Begunkov 2021-06-15 21:50 ` Jens Axboe 2021-06-15 23:35 ` Steven Rostedt 2021-06-16 12:49 ` Jens Axboe 2021-06-16 19:00 ` Olivier Langlois 2021-06-16 19:02 ` Jens Axboe 2021-06-16 21:30 ` Olivier Langlois 2021-06-16 21:33 ` Jens Axboe 2021-06-20 19:15 ` Olivier Langlois 2021-06-20 20:13 ` Pavel Begunkov 2021-06-16 13:33 ` Olivier Langlois 2021-06-16 13:43 ` Steven Rostedt 2021-06-16 13:53 ` Pavel Begunkov [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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.