From: Bart Van Assche <bvanassche@acm.org>
To: jin young choi <ychoijy@gmail.com>, Avri Altman <Avri.Altman@wdc.com>
Cc: "j-young.choi@samsung.com" <j-young.choi@samsung.com>,
ALIM AKHTAR <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
Daejun Park <daejun7.park@samsung.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: ufs: wb: Add Manual Flush sysfs and cleanup toggle functions
Date: Sat, 23 Apr 2022 14:38:46 -0700 [thread overview]
Message-ID: <0f061fc0-d7ee-aa48-278b-4ca7dc3ce53f@acm.org> (raw)
In-Reply-To: <CAM36TBtsU0k1e+8-_Ew4ve3SJ0yExUFwPAYnmQy_-AXUHGoeZw@mail.gmail.com>
On 4/23/22 07:24, jin young choi wrote:
>>> +static DEVICE_ATTR_RW(wb_flush_on);
>> Maybe wb_flush_enable ?
>>
> 'wb_on' sysfs already existed. So I named it in the same format (_on)
> I'll change both. (_on -> _enable)
sysfs attributes constitute an ABI. Breaking the user space ABI is not
allowed. Hence, renaming existing sysfs attributes is not an option.
Thanks,
Bart.
next prev parent reply other threads:[~2022-04-23 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220422120240epcms2p24bdcb416becf76b417f7c39006aa40f2@epcms2p1>
2022-04-22 12:14 ` Jinyoung CHOI
2022-04-22 13:46 ` Avri Altman
2022-04-23 14:24 ` jin young choi
2022-04-23 21:38 ` Bart Van Assche [this message]
2022-04-25 10:59 ` Jinyoung Choi
2022-04-22 17:25 ` Bart Van Assche
2022-04-23 18:40 ` jin young choi
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=0f061fc0-d7ee-aa48-278b-4ca7dc3ce53f@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=cang@codeaurora.org \
--cc=daejun7.park@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ychoijy@gmail.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
all inboxes | Powered by JetHome®