Em Sun, Feb 10, 2008 at 01:18:18AM +0100, Jan Engelhardt escreveu:
>
> On Feb 9 2008 21:54, Arnaldo Carvalho de Melo wrote:
> >> To drop strings that are only shown once anyway, such as:
> >>
> >> static int __init ebtables_init(void)
> >> {
> >> int ret;
> >>
> >>
On Feb 9 2008 21:54, Arnaldo Carvalho de Melo wrote:
>> To drop strings that are only shown once anyway, such as:
>>
>> static int __init ebtables_init(void)
>> {
>> int ret;
>>
>> mutex_lock(_mutex);
>> list_add(_standard_target.list, _targets);
>>
Em Sat, Feb 09, 2008 at 11:08:45PM +0100, Jan Engelhardt escreveu:
>
> On Feb 4 2008 19:07, Sam Ravnborg wrote:
> >> The attached patch allows something along the lines:
> >>
> >> int __init some_function(void)
> >> {
> >> [...]
> >> pr_init(KERN_WARNING "failure %s in %s\n",
On Feb 4 2008 19:07, Sam Ravnborg wrote:
>> The attached patch allows something along the lines:
>>
>> int __init some_function(void)
>> {
>> [...]
>> pr_init(KERN_WARNING "failure %s in %s\n", ...);
>> [...]
>> }
>>
>> Another idea I had was to make printk a macro that
On Feb 4 2008 19:07, Sam Ravnborg wrote:
The attached patch allows something along the lines:
int __init some_function(void)
{
[...]
pr_init(KERN_WARNING failure %s in %s\n, ...);
[...]
}
Another idea I had was to make printk a macro that figures out the
Em Sat, Feb 09, 2008 at 11:08:45PM +0100, Jan Engelhardt escreveu:
On Feb 4 2008 19:07, Sam Ravnborg wrote:
The attached patch allows something along the lines:
int __init some_function(void)
{
[...]
pr_init(KERN_WARNING failure %s in %s\n, ...);
[...]
}
On Feb 9 2008 21:54, Arnaldo Carvalho de Melo wrote:
To drop strings that are only shown once anyway, such as:
static int __init ebtables_init(void)
{
int ret;
mutex_lock(ebt_mutex);
list_add(ebt_standard_target.list, ebt_targets);
Em Sun, Feb 10, 2008 at 01:18:18AM +0100, Jan Engelhardt escreveu:
On Feb 9 2008 21:54, Arnaldo Carvalho de Melo wrote:
To drop strings that are only shown once anyway, such as:
static int __init ebtables_init(void)
{
int ret;
mutex_lock(ebt_mutex);
Hi Sam,
Sam Ravnborg <[EMAIL PROTECTED]> writes:
> On Mon, Feb 04, 2008 at 04:48:34PM +0100, Johannes Weiner wrote:
>> Hi,
>>
>> current approaches to have printk format strings in the corresponding
>> data section to the function they appear in look like the following (at
>> least what I have
On Mon, Feb 04, 2008 at 04:48:34PM +0100, Johannes Weiner wrote:
> Hi,
>
> current approaches to have printk format strings in the corresponding
> data section to the function they appear in look like the following (at
> least what I have seen so far):
>
> int __init some_function(void)
> {
>
Hi,
current approaches to have printk format strings in the corresponding
data section to the function they appear in look like the following (at
least what I have seen so far):
int __init some_function(void)
{
static char errmsg[] __initdata = "failure %s in %s\n";
[...]
On Mon, Feb 04, 2008 at 04:48:34PM +0100, Johannes Weiner wrote:
Hi,
current approaches to have printk format strings in the corresponding
data section to the function they appear in look like the following (at
least what I have seen so far):
int __init some_function(void)
{
Hi,
current approaches to have printk format strings in the corresponding
data section to the function they appear in look like the following (at
least what I have seen so far):
int __init some_function(void)
{
static char errmsg[] __initdata = failure %s in %s\n;
[...]
Hi Sam,
Sam Ravnborg [EMAIL PROTECTED] writes:
On Mon, Feb 04, 2008 at 04:48:34PM +0100, Johannes Weiner wrote:
Hi,
current approaches to have printk format strings in the corresponding
data section to the function they appear in look like the following (at
least what I have seen so far):
14 matches
Mail list logo
