[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABXOdTcjr6zw9sceC-i_Za3uOaOVmKGFaJsyMxhLUPEhtKn_Jg@mail.gmail.com>
Date: Wed, 17 Apr 2019 15:23:52 -0700
From: Guenter Roeck <groeck@...gle.com>
To: Raul Rangel <rrangel@...omium.org>
Cc: Alan Stern <stern@...land.harvard.edu>, linux-usb@...r.kernel.org,
Guenter Roeck <groeck@...omium.org>,
Oliver Neukum <oneukum@...e.com>,
Daniel Kurtz <djkurtz@...omium.org>, zwisler@...omium.org,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Dmitry Torokhov <dtor@...omium.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>
Subject: Re: [PATCH v3] usb/hcd: Send a uevent signaling that the host
controller had died
On Wed, Apr 17, 2019 at 3:11 PM Raul Rangel <rrangel@...omium.org> wrote:
>
> On Wed, Apr 17, 2019 at 04:39:23PM -0400, Alan Stern wrote:
> >
> > This sounds like a golden opportunity! Submit a separate patch making
> > the parameter to kobject_uevent_env be const (actually const char *
> > const []), then submit this patch on top of that one.
> So there are other parts of the code base that dynamically create their
> array values. So by making the function take const, it breaks :(
Confused. The calling code can still be non-const. I don't see the
parameter modified in kobject_uevent_env(), so declaring it const
should be possible. Can you give an example of code that no longer
works ?
Thanks,
Guenter
> >
> > Alan Stern
> >
Powered by blists - more mailing lists