On Mon, Mar 18, 2013 at 9:54 PM, Lin Feng <linfeng@xxxxxxxxxxxxxx> wrote:
> Also replace deprecated printk(KERN_ERR...) with pr_err() as suggested
> by Yinghai, attaching the function name to provide plenty info.
>
> Cc: Yinghai Lu <yinghai@xxxxxxxxxx>
> Signed-off-by: Lin Feng <linfeng@xxxxxxxxxxxxxx>
> ---
> kernel/range.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/range.c b/kernel/range.c
> index 9b8ae2d..071b0ab 100644
> --- a/kernel/range.c
> +++ b/kernel/range.c
> @@ -97,7 +97,8 @@ void subtract_range(struct range *range, int az, u64 start, u64 end)
> range[i].end = range[j].end;
> range[i].start = end;
> } else {
> - printk(KERN_ERR "run of slot in ranges\n");
> + pr_err("%s: run out of slot in ranges\n",
> + __func__);
> }
> range[j].end = start;
> continue;
So now the user might see:
subtract_range: run out of slot in ranges
What is the user supposed to do when he sees that? If he happens to
mention it on LKML, what are we going to do about it? If he attaches
the complete dmesg log, is there enough information to do something?
IMHO, that message is still totally useless.
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
