[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJzde05B0Ag1e7Lpbg5hKK+2SYj0JYLKLkMQNoag3MBXKWUd6g@mail.gmail.com>
Date: Tue, 20 Dec 2022 11:32:12 -0600
From: Allen Webb <allenwebb@...gle.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "linux-modules@...r.kernel.org" <linux-modules@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Luis Chamberlain <mcgrof@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v9 07/10] modpost: Add -b option for emitting built-in aliases
On Tue, Dec 20, 2022 at 12:43 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> On Mon, Dec 19, 2022 at 02:46:15PM -0600, Allen Webb wrote:
> > This adds an unimplemented command line flag for writing the built-in
> > aliases to a file.
>
> If it is unimplemented, why add it?
This is a fairly self contained change even though the code that
populates mod->modalias_buf is in the next patch. I could flatten the
two commits, but I was trying to keep this to a single logical change.
There is somewhat of a chicken and egg problem here. If the other
patch comes first it will be dead code, if this comes first it is
pretty much dead code.
>
> And this needs a lot more description as to why you are changing this
> here, as well as documentation for the flag you added, right?
I might be missing something, but I don't see an obvious place where
the other command line parameters for modpost are documented, so I
will add a comment inside the case statement unless you have a better
idea.
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists