On Mon, 2019-08-12 at 09:15 -0700, Deepa Dinamani wrote:
> On Mon, Aug 12, 2019 at 9:09 AM Deepa Dinamani wrote:
> > On Mon, Aug 12, 2019 at 7:11 AM Arnd Bergmann wrote:
> > > On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
> > > wrote:
> > > > On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani
On Mon, Aug 12, 2019 at 9:09 AM Deepa Dinamani wrote:
>
> On Mon, Aug 12, 2019 at 7:11 AM Arnd Bergmann wrote:
> >
> > On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
> > wrote:
> > > On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> > > > On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> >
On Mon, Aug 12, 2019 at 7:11 AM Arnd Bergmann wrote:
>
> On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
> wrote:
> > On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> > > On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> > > wrote:
> > > > On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani
On Mon, Aug 12, 2019 at 3:25 PM Ben Hutchings
wrote:
> On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> > On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> > wrote:
> > > On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> > > > The warning reuses the uptime max of 30 years used by
On Sat, 2019-08-10 at 13:44 -0700, Deepa Dinamani wrote:
> On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
> wrote:
> > On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> > > The warning reuses the uptime max of 30 years used by the
> > > setitimeofday().
> > >
> > > Note that the warning
> This doesn't seem like a helpful way to log the time. Maybe use
> time64_to_tm() to convert to "broken down" time and then print it with
> "%ptR"... but that wants struct rtc_time. If you apply the attached
> patch, however, you should then be able to print struct tm with
> "%ptT".
OK. Will
On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
wrote:
>
> On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> > The warning reuses the uptime max of 30 years used by the
> > setitimeofday().
> >
> > Note that the warning is only added for new filesystem mounts
> > through the mount syscall.
On Mon, Aug 5, 2019 at 4:12 PM Ben Hutchings
wrote:
>
> On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> > The warning reuses the uptime max of 30 years used by the
> > setitimeofday().
> >
> > Note that the warning is only added for new filesystem mounts
> > through the mount syscall.
On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> The warning reuses the uptime max of 30 years used by the
> setitimeofday().
>
> Note that the warning is only added for new filesystem mounts
> through the mount syscall. Automounts do not have the same warning.
[...]
Another thing -
On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote:
> The warning reuses the uptime max of 30 years used by the
> setitimeofday().
>
> Note that the warning is only added for new filesystem mounts
> through the mount syscall. Automounts do not have the same warning.
>
> Signed-off-by: Deepa
The warning reuses the uptime max of 30 years used by the
setitimeofday().
Note that the warning is only added for new filesystem mounts
through the mount syscall. Automounts do not have the same warning.
Signed-off-by: Deepa Dinamani
---
fs/namespace.c | 11 +++
1 file changed, 11
11 matches
Mail list logo
