From: Jason Gunthorpe <jgg@ziepe.ca>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
alex.williamson@redhat.com, joro@8bytes.org
Cc: tools@linux.kernel.org
Subject: Re: b4 and lore are mangling from lines in patches
Date: Fri, 27 May 2022 11:20:01 -0300 [thread overview]
Message-ID: <20220527142001.GF2960187@ziepe.ca> (raw)
In-Reply-To: <20220527141524.awu2qhsduqx5kfyf@meerkat.local>
On Fri, May 27, 2022 at 10:15:24AM -0400, Konstantin Ryabitsev wrote:
> On Fri, May 27, 2022 at 11:09:50AM -0300, Jason Gunthorpe wrote:
> > Hi Konstantin,
> >
> > I noticed this:
> >
> > $ b4.sh am https://lore.kernel.org/linux-iommu/20220527070307.2359150-1-liuke94@huawei.com
> > $ grep ^From 20220527_iommu_drivers_iommu_directly_use_ida_alloc_free.mbx
> > From git@z Thu Jan 1 00:00:00 1970
> > From: keliu via iommu <iommu@lists.linux-foundation.org>
> > ^^^^^^^^^^^^
> >
> > And when this is git AM'd the from line is mangled.
> >
> > I see this is leaking into the main repo now:
> >
> > commit 9ed1d7f510336e283c0bb2d20fd771e9d8fa085b
> > Author: Vasant Hegde via iommu <iommu@lists.linux-foundation.org>
> > Date: Mon Mar 14 12:32:26 2022 +0530
> >
> > iommu/amd: Remove redundant check
> >
> > smatch static checker warning:
> > drivers/iommu/amd/init.c:1989 amd_iommu_init_pci()
> > warn: duplicate check 'ret' (previous on line 1978)
> >
> > Can something be done?
>
> This is done by the iommu list, not by lore or b4 -- someone turned on "send
> emails from the list address," which is a terrible setting for lists that
> receive patches.
>
> You will need to complain to that list's admins, found at the bottom of
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
Ah given the linuxfoundation.org I had guessed that is you. Let's add
Alex and Joerg.
Jason
next prev parent reply other threads:[~2022-05-27 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 14:09 b4 and lore are mangling from lines in patches Jason Gunthorpe
2022-05-27 14:15 ` Konstantin Ryabitsev
2022-05-27 14:20 ` Jason Gunthorpe [this message]
2022-05-27 14:30 ` Konstantin Ryabitsev
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=20220527142001.GF2960187@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=joro@8bytes.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox