From: Greg KH <gregkh@linuxfoundation.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v3] USB: serial: ftdi_sio: Convert to use dev_groups
Date: Fri, 2 Sep 2022 16:52:52 +0200 [thread overview]
Message-ID: <YxIYxDQ/vLi4Eq38@kroah.com> (raw)
In-Reply-To: <20220902143346.4120012-1-jiasheng@iscas.ac.cn>
On Fri, Sep 02, 2022 at 10:33:46PM +0800, Jiasheng Jiang wrote:
> On Fri, Sep 02, 2022 at 05:56:13PM +0800, Greg KH wrote:
> >> drivers/usb/serial/ftdi_sio.c | 101 +++++++++++++++++-----------------
> >> 1 file changed, 51 insertions(+), 50 deletions(-)
> >>
> >> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> >> index d5a3986dfee7..479c3a5caaf8 100644
> >> --- a/drivers/usb/serial/ftdi_sio.c
> >> +++ b/drivers/usb/serial/ftdi_sio.c
> >> @@ -1107,11 +1107,40 @@ static u32 ftdi_232bm_baud_base_to_divisor(int baud, int base);
> >> static u32 ftdi_232bm_baud_to_divisor(int baud);
> >> static u32 ftdi_2232h_baud_base_to_divisor(int baud, int base);
> >> static u32 ftdi_2232h_baud_to_divisor(int baud);
> >> +static umode_t ftdi_sio_attr_is_visible(struct kobject *kobj,
> >> + struct attribute *attr, int idx);
> >> +static ssize_t latency_timer_store(struct device *dev,
> >> + struct device_attribute *attr,
> >> + const char *valbuf, size_t count);
> >> +static ssize_t event_char_store(struct device *dev,
> >> + struct device_attribute *attr, const char *valbuf, size_t count);
> >> +static ssize_t latency_timer_show(struct device *dev,
> >> + struct device_attribute *attr, char *buf);
> >> +
> >
> > Please work with the code so that you do not have to pre-define these
> > functions. It should be possible. Worst case, you pre-define the
> > structure for the driver, that should be it.
>
> Without pre-definition of the functions, compilation errors will occur,
> such as 'ftdi_sio_attr_is_visible' undeclared here.
> I have no idea why they are not necessary.
If you move the code around that asks for those functions, you will not
need to define them.
> > And again, have you tested this change?
>
> Every time I change the code, I recomplie it and check whether there are
> errors.
> Are there any other tests I need to do?
Yes, boot with the device and make sure that the sysfs files are still
there. You do have access to one of these devices, right? They are
very very common.
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-02 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 14:33 Jiasheng Jiang
2022-09-02 14:52 ` Greg KH [this message]
2022-09-05 10:01 Jiasheng Jiang
2022-09-13 12:48 ` Johan Hovold
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=YxIYxDQ/vLi4Eq38@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jiasheng@iscas.ac.cn \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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
all inboxes | Powered by JetHome®