All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: dedekind1@gmail.com
Cc: Michal Marek <mmarek@suse.cz>,
	jirislaby@gmail.com, linux-kernel@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-mtd@lists.infradead.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ubifs: remove __DATE__ and __TIME__
Date: Fri, 24 Aug 2012 13:51:02 +0200	[thread overview]
Message-ID: <50376AA6.7030303@suse.cz> (raw)
In-Reply-To: <1345809271.2848.294.camel@sauron.fi.intel.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/24/2012 01:54 PM, Artem Bityutskiy wrote:
> On Thu, 2012-08-09 at 19:43 +0200, Jiri Slaby wrote:
>> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c index
>> e354832..67af316 100644 --- a/fs/ubifs/super.c +++
>> b/fs/ubifs/super.c @@ -1431,7 +1431,6 @@ static int
>> mount_ubifs(struct ubifs_info *c) ubifs_msg("reserved for root:
>> %llu bytes (%llu KiB)", c->report_rp_size, c->report_rp_size >>
>> 10);
>> 
>> -	dbg_msg("compiled on:         " __DATE__ " at " __TIME__); 
>> dbg_msg("min. I/O unit size:  %d bytes", c->min_io_size); 
>> dbg_msg("max. write size:     %d bytes", c->max_write_size); 
>> dbg_msg("LEB size:            %d bytes (%d KiB)",
> 
> Pushed to linux-ubifs.git, thanks! Does it make sense to hurry up
> and send this to 3.6? Or it can be merged to 3.7 normally?

No need to rush. We have the patch in a local queue anyway.

thanks,
- -- 
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQN2qmAAoJEL0lsQQGtHBJi/EP/AxRThCd3Kbp2QS0cWlR2d81
AlYi+/TWC8P3NOjfoW3dZibn23DsZ45Dgs0MR9V1AvaKAZ81MIVE7dTQKJxalgen
R8bugSb8j9YssnuSmQaqmGgsvDXzW3VCLaGgwSVlOJ1sTJgG0A7r9/vNf1aPLG5J
oDthCQswltnyl7iRuYMLB3G1mtP+ml2rW9GyKhQfR9/380gPDsfx5PuCwjqvS3we
zn81GS54RTe0C8kROUuyIuLGN+NVPoGXQVp3IIww7cN6G/xb7WDm5sle0VNYYCiC
VQCXfApJWkOaORqKRfBHMLqfgkcaegT+uQA0ELon0T5GTfLrTGHnmijYKLbYhVK9
suUdLMOSrk5Pcu8KYmT3ti7FP+kTJE9+lJAqdCpedSBEzn88TGn+5gY9APG+Nsy2
9YkvwAelnzdRlf0AO5RXfCUua6wk/UNSNrZJDex1fflYCjBXdlneeV7akDBVqGW8
9Vklwmp5PeBtWt2kh7U9cyxDRiC55df8DKG1I/TGZ7YdtL6O+mtFegVMkc5NA2rp
DXFgYDnhthaqfGDXLHIiGTS+B7twmsVI1kwXEY/Tsga0JS7WQu6rgmbn88JJFwI4
PS7VT0EQ4ZiAH2olXu9fpFbJrI+s7ksWw5pC/4ri15wAHVZd8i5dZkhbX60XM7ns
Xd3BJrukZbugw0iiMVBv
=7Zm3
-----END PGP SIGNATURE-----

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jslaby@suse.cz>
To: dedekind1@gmail.com
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, jirislaby@gmail.com,
	linux-kernel@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-mtd@lists.infradead.org, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] ubifs: remove __DATE__ and __TIME__
Date: Fri, 24 Aug 2012 13:51:02 +0200	[thread overview]
Message-ID: <50376AA6.7030303@suse.cz> (raw)
In-Reply-To: <1345809271.2848.294.camel@sauron.fi.intel.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/24/2012 01:54 PM, Artem Bityutskiy wrote:
> On Thu, 2012-08-09 at 19:43 +0200, Jiri Slaby wrote:
>> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c index
>> e354832..67af316 100644 --- a/fs/ubifs/super.c +++
>> b/fs/ubifs/super.c @@ -1431,7 +1431,6 @@ static int
>> mount_ubifs(struct ubifs_info *c) ubifs_msg("reserved for root:
>> %llu bytes (%llu KiB)", c->report_rp_size, c->report_rp_size >>
>> 10);
>> 
>> -	dbg_msg("compiled on:         " __DATE__ " at " __TIME__); 
>> dbg_msg("min. I/O unit size:  %d bytes", c->min_io_size); 
>> dbg_msg("max. write size:     %d bytes", c->max_write_size); 
>> dbg_msg("LEB size:            %d bytes (%d KiB)",
> 
> Pushed to linux-ubifs.git, thanks! Does it make sense to hurry up
> and send this to 3.6? Or it can be merged to 3.7 normally?

No need to rush. We have the patch in a local queue anyway.

thanks,
- -- 
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQN2qmAAoJEL0lsQQGtHBJi/EP/AxRThCd3Kbp2QS0cWlR2d81
AlYi+/TWC8P3NOjfoW3dZibn23DsZ45Dgs0MR9V1AvaKAZ81MIVE7dTQKJxalgen
R8bugSb8j9YssnuSmQaqmGgsvDXzW3VCLaGgwSVlOJ1sTJgG0A7r9/vNf1aPLG5J
oDthCQswltnyl7iRuYMLB3G1mtP+ml2rW9GyKhQfR9/380gPDsfx5PuCwjqvS3we
zn81GS54RTe0C8kROUuyIuLGN+NVPoGXQVp3IIww7cN6G/xb7WDm5sle0VNYYCiC
VQCXfApJWkOaORqKRfBHMLqfgkcaegT+uQA0ELon0T5GTfLrTGHnmijYKLbYhVK9
suUdLMOSrk5Pcu8KYmT3ti7FP+kTJE9+lJAqdCpedSBEzn88TGn+5gY9APG+Nsy2
9YkvwAelnzdRlf0AO5RXfCUua6wk/UNSNrZJDex1fflYCjBXdlneeV7akDBVqGW8
9Vklwmp5PeBtWt2kh7U9cyxDRiC55df8DKG1I/TGZ7YdtL6O+mtFegVMkc5NA2rp
DXFgYDnhthaqfGDXLHIiGTS+B7twmsVI1kwXEY/Tsga0JS7WQu6rgmbn88JJFwI4
PS7VT0EQ4ZiAH2olXu9fpFbJrI+s7ksWw5pC/4ri15wAHVZd8i5dZkhbX60XM7ns
Xd3BJrukZbugw0iiMVBv
=7Zm3
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-08-24 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 17:43 [PATCH] ubifs: remove __DATE__ and __TIME__ Jiri Slaby
2012-08-09 17:43 ` Jiri Slaby
2012-08-24 11:54 ` Artem Bityutskiy
2012-08-24 11:54   ` Artem Bityutskiy
2012-08-24 11:51   ` Jiri Slaby [this message]
2012-08-24 11:51     ` Jiri Slaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50376AA6.7030303@suse.cz \
    --to=jslaby@suse.cz \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mmarek@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.