On Wed, Dec 04, 2013 at 09:35:29AM +0800, Baoquan He wrote:
> On 12/02/13 at 10:44am, Vivek Goyal wrote:
> > On Fri, Nov 29, 2013 at 11:10:48AM +0800, Baoquan He wrote:
> >
> > [..]
> > > > +void *arch_kexec_kernel_image_load(struct kimage *image, char *kernel,
> > > > + unsigned long kernel_len, char *initrd,
> > > > + unsigned long initrd_len, char *cmdline,
> > > > + unsigned long cmdline_len)
> > > > +{
> > > > + int idx = image->file_handler_idx;
> > > > +
> > > > + if (idx < 0)
> > > > + return ERR_PTR(-ENOEXEC);
> > > > +
> > > > + return kexec_file_type[idx].load(image, kernel, kernel_len,
> > > > initrd,
> > > > + initrd_len, cmdline,
> > > > cmdline_len);
> > > > +}
> > > > +
> > > > +int arch_image_file_post_load_cleanup(struct kimage *image)
> > > > +{
> > >
> > > Hi Vivek,
> > >
> > > This function is defined as one of arch specific fucntion set, why don't
> > > we name it in a unified prefix as others.
> >
> > I am using "arch_" prefix. What else to use?
>
> I mean in this function series, other functions have name like
> arch_kexec_kernel_image_xxx, why this function is lonely, and is named
> as arch_kimage_xxx. And here what does the 'k' mean in "kimage", kexec
> image or kernel image, I am confused.
kimage is name is structure which is containing all the data relevant
to loading of file.
I guess I can use arch_kimage_file_post_load_cleanup().
Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
