From: Vanessa Page <Vebpe@outlook.com>
To: Yifei Liu <yifeliu@cs.stonybrook.edu>
Cc: "ezk@cs.stonybrook.edu" <ezk@cs.stonybrook.edu>,
"madkar@cs.stonybrook.edu" <madkar@cs.stonybrook.edu>,
David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Kyeong Yoo <kyeong.yoo@alliedtelesis.co.nz>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jffs2: correct logic when creating a hole in jffs2_write_begin
Date: Mon, 25 Jul 2022 22:07:17 +0000 [thread overview]
Message-ID: <MN2PR17MB3375CA88F933233FC8126784B8959@MN2PR17MB3375.namprd17.prod.outlook.com> (raw)
In-Reply-To: <MN2PR17MB33751E0A2DFD72AA5E774DF5B8959@MN2PR17MB3375.namprd17.prod.outlook.com>
Koop😂😂😑😑😑😎😄😄😴😴👀👀💁🙈🙈🙈🙈💁👀👀😑💁😁😳😎😴😑👀😑😄🤣🤣😀😃😑😴😄🤥🤫😥😰🥵🥵😡😡🤬🤯😭😭😟😟🥳🤩🥸🥸🥸🙁😩🥺☹️😣😔😔😔😖😣😢😡🥶😰😰😥😥😶🌫️🤬🤬🤬🤯😶🌫️🥶😰😰🤫🤫😓🤯🤯🤯
Ooiggvklpoure🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤯🤯🤯🤯🤯🤯🤯🤯🤯🤫😓🤬🤯🤯🤬🤬🙁😒😍😒😒😎🥸🤩🥳😟😖🥺😩😩🤩🥳🥳😟😖😣🙁😩☹️😟😫😤😭🤬🤩🤩🥸😎🙁😩😡😵😪😧🤥🤥😯😵🤮😬🤥😓🤗🤗😶😲🤤🤐🤒🤕😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫🤑😼😽☠️💀💀👻👻👻👹👹👺👽👽💀💀👻💀💀💀☠️☠️☠️☠️
Sent from my iPhone
> On Jul 25, 2022, at 5:37 PM, Vanessa Page <Vebpe@outlook.com> wrote:
>
> Koop😂😂😑😑😑😎😄😄😴😴👀👀💁🙈🙈🙈🙈💁👀👀😑💁😁😳😎😴😑👀😑😄🤣🤣😀😃😑😴😄🤥🤫😥😰🥵🥵😡😡🤬🤯😭😭😟😟🥳🤩🥸🥸🥸🙁😩🥺☹️😣😔😔😔😖😣😢😡🥶😰😰😥😥😶🌫️🤬🤬🤬🤯😶🌫️🥶😰😰🤫🤫😓🤯🤯🤯
> Ooiggvklpoure🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤯🤯🤯🤯🤯🤯🤯🤯🤯🤫😓🤬🤯🤯🤬🤬🙁😒😍😒😒😎🥸🤩🥳😟😖🥺😩😩🤩🥳🥳😟😖😣🙁😩☹️😟😫😤😭🤬🤩🤩🥸😎🙁😩😡😵😪😧🤥🤥😯😵🤮😬🤥😓🤗🤗😶😲🤤🤐🤒🤕😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫😵💫🤑😼😽☠️💀💀👻👻👻👹👹👺👽👽💀💀👻💀💀💀☠️☠️☠️☠️
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-25 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 4:58 [PATCH] jffs2: correct logic when creating a hole in jffs2_write_begin Yifei Liu
2022-07-25 5:03 ` Vanessa Page
2022-07-25 21:34 ` Vanessa Page
2022-07-25 22:07 ` Vanessa Page [this message]
2022-07-25 22:08 ` Vanessa Page
2022-07-25 22:08 ` Vanessa Page
2022-07-26 0:11 ` Vanessa Page
2022-08-03 15:53 Yifei Liu
2022-08-21 18:21 ` Joakim Tjernlund
2022-08-22 6:25 ` Richard Weinberger
2022-09-04 19:39 ` Yifei Liu
2022-09-21 21:30 ` Yifei Liu
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=MN2PR17MB3375CA88F933233FC8126784B8959@MN2PR17MB3375.namprd17.prod.outlook.com \
--to=vebpe@outlook.com \
--cc=dwmw2@infradead.org \
--cc=ezk@cs.stonybrook.edu \
--cc=kyeong.yoo@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=madkar@cs.stonybrook.edu \
--cc=richard@nod.at \
--cc=willy@infradead.org \
--cc=yifeliu@cs.stonybrook.edu \
/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).