On Thu, Oct 1, 2015 at 1:44 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > From: David Howells <dhowells@xxxxxxxxxx> > > We'll want to reuse this same code later in order to > read two separate types of file contents. This generalizes > fw_read_file() for reading a file rebrands it as fw_read_file(). Er, maybe that should read "...fw_read_file_contents() for reading a file and rebrands it as fw_read_file()." ? > This caller lets us pegs arbitrary data onto the target > buffer and size if the file is found. This sentence is somewhat confusing. The data isn't arbitrary. It is what the caller wants you to read from path. What is arbitrary, at least in the context of this function, is the path passed to it. Maybe rewrite this as: "The new function allows us to read file contents from arbitrary paths and return the data and size of the files read." > While at it this cleans up the exit paths on fw_read_file(). > > Signed-off-by: David Howells <dhowells@xxxxxxxxxx> > Signed-off-by: Luis R. Rodriguez <mcgrof@xxxxxxxx> The code changes themselves look fine. josh -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
