All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 v0.10.0 is available
Date: Tue, 20 Sep 2022 12:10:46 +0300	[thread overview]
Message-ID: <YymDlmJG8fNhvHSY@unreal> (raw)
In-Reply-To: <20220916181319.okfskienqh6kfeor@meerkat.local>

Hi,

I got the following splat when tried ty functionality:

➜  kernel git:(wip/leon-for-next) ~/src/b4/b4.sh ty -aS --dry-run
Auto-thankanating commits in wip/leon-for-next
Found 2 of your commits since 1.week
Calculating patch hashes, may take a moment...
  Located: [PATCH for-next 0/2] irdma for-next updates 9-7-2022
---
Generating 1 thank-you letters
  Sending: Re: [PATCH for-next 0/2] irdma for-next updates 9-7-2022
    --- DRYRUN: message follows ---
    | From: Leon Romanovsky <leon@kernel.org>
    | To: Shiraz Saleem <shiraz.saleem@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>
    | Cc: linux-rdma@vger.kernel.org
    | In-Reply-To: <20220907191324.1173-1-shiraz.saleem@intel.com>
    | References: <20220907191324.1173-1-shiraz.saleem@intel.com>
    | Subject: Re: [PATCH for-next 0/2] irdma for-next updates 9-7-2022
    | Message-Id: <166366381168.86952.7578029482213151514.b4-ty@kernel.org>
    | Date: Tue, 20 Sep 2022 11:50:11 +0300
    | MIME-Version: 1.0
    | Content-Type: text/plain; charset="utf-8"
    | Content-Transfer-Encoding: 8bit
    | X-Mailer: b4 0.11.0-dev-8af31
    |
    | On Wed, 7 Sep 2022 14:13:22 -0500, Shiraz Saleem wrote:
    | > This series adds udata inlen/outlen validation for the verb API's
    | > and fixes up completion error code reporting to ulp's.
    | >
    | > Shiraz Saleem (1):
    | >   RDMA/irdma: Validate udata inlen and outlen
    | >
    | > Sindhu-Devale (1):
    | >   RDMA/irdma: Align AE id codes to correct flush code and event
    | >
    | > [...]
    |
    | Applied, thanks!
    |
    | [1/2] RDMA/irdma: Align AE id codes to correct flush code and event
    |       commit: b6da0e79c495ba730223608f2791bc02c9af38b6
    | [2/2] RDMA/irdma: Validate udata inlen and outlen
    |       commit: b3cce21f46fe228dc5cc81c4b93ba25e3d873079
    |
    | Best regards,
    | --
    | Leon Romanovsky <leon@kernel.org>
    --- DRYRUN: message ends ---
Dry run, preserving tracked series.
---
DRYRUN: generated 1 thank-you letters
Traceback (most recent call last):
  File "/home/leonro/src/b4/b4/command.py", line 358, in <module>
    cmd()
  File "/home/leonro/src/b4/b4/command.py", line 341, in cmd
    cmdargs.func(cmdargs)
  File "/home/leonro/src/b4/b4/command.py", line 106, in cmd_ty
    b4.ty.main(cmdargs)
  File "/home/leonro/src/b4/b4/ty.py", line 674, in main
    auto_thankanator(cmdargs)
  File "/home/leonro/src/b4/b4/ty.py", line 378, in auto_thankanator
    send_messages(applied, wantbranch, cmdargs)
  File "/home/leonro/src/b4/b4/ty.py", line 469, in send_messages
    smtp.quit()
AttributeError: 'list' object has no attribute 'quit'

---------------------
My sendemail section:

   26 [sendemail]     
   27         smtpserver = /usr/local/bin/msmtp-enqueue.sh
   28         suppresscc = self
   29         chainReplyTo = false
   30         confirm = always
   31         from = Leon Romanovsky <leon@kernel.org>
   32         envelopeSender = Leon Romanovsky <leon@kernel.org>
   33         signingkey = leon@kernel.org
   34         composeencoding = utf-8
   35         # Rely on git-format-patch to generate message-id
   36         thread = false

Thanks

  reply	other threads:[~2022-09-20  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 18:13 b4 v0.10.0 is available Konstantin Ryabitsev
2022-09-20  9:10 ` Leon Romanovsky [this message]
2022-09-20 14:48   ` Konstantin Ryabitsev
2022-09-20 17:10     ` Leon Romanovsky
2022-09-20 18:15       ` Konstantin Ryabitsev
2022-09-20 18:33         ` Leon Romanovsky
2022-09-20 18:59           ` Konstantin Ryabitsev
2022-09-21  7:37             ` Leon Romanovsky

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=YymDlmJG8fNhvHSY@unreal \
    --to=leon@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.kernel.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 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.