From: Miquel Raynal <miquel.raynal@bootlin.com>
To: dregan@mail.com
Cc: bcm-kernel-feedback-list@broadcom.com,
linux-mtd@lists.infradead.org, f.fainelli@gmail.com,
rafal@milecki.pl, joel.peshkin@broadcom.com,
computersforpeace@gmail.com, dan.beygelman@broadcom.com,
william.zhang@broadcom.com, frieder.schrempf@kontron.de,
linux-kernel@vger.kernel.org, vigneshr@ti.com, richard@nod.at,
bbrezillon@kernel.org, kdasu.kdev@gmail.com,
JaimeLiao <jaimeliao.tw@gmail.com>,
Arseniy Krasnov <AVKrasnov@sberdevices.ru>,
Adam Borowski <kilobyte@angband.pl>
Subject: Re: [PATCH v2 1/4] mtd: rawnand: Add destructive operation
Date: Fri, 13 Oct 2023 10:48:09 +0200 [thread overview]
Message-ID: <20231013104809.15821b9f@xps-13> (raw)
In-Reply-To: <trinity-902f8ae6-26e3-484b-ba2d-00946a63333a-1697132171458@3c-app-mailcom-lxa13>
Hello,
dregan@mail.com wrote on Thu, 12 Oct 2023 19:36:11 +0200:
> Hi Miquel,
>
> > Sent: Thursday, October 12, 2023 at 12:06 AM
> > From: "Miquel Raynal" <miquel.raynal@bootlin.com>
> > To: dregan@mail.com
> > Cc: bcm-kernel-feedback-list@broadcom.com, linux-mtd@lists.infradead.org, f.fainelli@gmail.com, rafal@milecki.pl, joel.peshkin@broadcom.com, computersforpeace@gmail.com, dan.beygelman@broadcom.com, william.zhang@broadcom.com, frieder.schrempf@kontron.de, linux-kernel@vger.kernel.org, vigneshr@ti.com, richard@nod.at, bbrezillon@kernel.org, kdasu.kdev@gmail.com, "JaimeLiao" <jaimeliao.tw@gmail.com>, "Arseniy Krasnov" <AVKrasnov@sberdevices.ru>, "Adam Borowski" <kilobyte@angband.pl>
> > Subject: Re: [PATCH v2 1/4] mtd: rawnand: Add destructive operation
> >
> > Hello,
> >
> > dregan@mail.com wrote on Thu, 12 Oct 2023 02:40:35 +0200:
> >
> > The author should be Boris as well (git commit --amend --author=...)
>
> I will attempt to change the author but git seems to be
> somewhat limited in what I can accomplish when it comes to
> changing emails, sending in the name of someone else etc.
>
> >
> > > Erase and program operations need the write protect (wp) pin to be
> > > de-asserted to take effect. Add the concept of destructive
> > > operation and pass the information to exec_op() so controllers know
> > > when they should de-assert this pin without having to decode
> > > the command opcode.
> > >
> > > Created by Boris Brezillon.
> >
> > This can go away.
>
> Will remove.
>
> >
> > >
> > > https://github.com/bbrezillon/linux/commit/e612e1f2c69a33ac5f2c91d13669f0f172d58717
> >
> > This as well.
>
> Will also remove.
>
> >
> > > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> >
> > Please use Boris' kernel.org e-mail for the authorship and SoB
>
> I don't know what Boris' kernel.org email address?
> Is it @bootlin? Collabora still shows up as email when
> I do the list of maintainers. I did some searching
> but couldn't really find anything conclusive.
It's in .mailmap: bbrezillon@kernel.org
> > > Signed-off-by: David Regan <dregan@mail.com>
>
> Do I still keep this SOB or should I change it to something else?
You need both SoB: his then yours.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-10-13 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 0:40 [PATCH v2 1/4] mtd: rawnand: Add destructive operation dregan
2023-10-12 7:06 ` Miquel Raynal
2023-10-12 17:36 ` dregan
2023-10-13 8:48 ` Miquel Raynal [this message]
2023-10-17 6:19 ` dregan
2023-10-17 7:47 ` Miquel Raynal
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=20231013104809.15821b9f@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=AVKrasnov@sberdevices.ru \
--cc=bbrezillon@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=dan.beygelman@broadcom.com \
--cc=dregan@mail.com \
--cc=f.fainelli@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=jaimeliao.tw@gmail.com \
--cc=joel.peshkin@broadcom.com \
--cc=kdasu.kdev@gmail.com \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=william.zhang@broadcom.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