On Fri, 01 Jun 2018 16:42:36 +0800 Ian Kent wrote:
> The resulting "autofs-create-autofs-kconfig-and-makefile.patch" should
> now look like
Got it, thanks ;)
On Fri, 01 Jun 2018 16:42:36 +0800 Ian Kent wrote:
> The resulting "autofs-create-autofs-kconfig-and-makefile.patch" should
> now look like
Got it, thanks ;)
On Fri, 2018-06-01 at 09:35 +0800, Ian Kent wrote:
> On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote:
> > On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
> >
> > > > I actually had an alternative approach that I tried out successfully
> > > > but discarded as being too different from
On Fri, 2018-06-01 at 09:35 +0800, Ian Kent wrote:
> On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote:
> > On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
> >
> > > > I actually had an alternative approach that I tried out successfully
> > > > but discarded as being too different from
On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote:
> On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
>
> > > I actually had an alternative approach that I tried out successfully
> > > but discarded as being too different from the original code. Just for
> > > reference, this one would
On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote:
> On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
>
> > > I actually had an alternative approach that I tried out successfully
> > > but discarded as being too different from the original code. Just for
> > > reference, this one would
On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
> > I actually had an alternative approach that I tried out successfully
> > but discarded as being too different from the original code. Just for
> > reference, this one would work as well, and allow both to be
> > compiled together. The
On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
> > I actually had an alternative approach that I tried out successfully
> > but discarded as being too different from the original code. Just for
> > reference, this one would work as well, and allow both to be
> > compiled together. The
On Wed, 2018-05-30 at 10:41 +0200, Arnd Bergmann wrote:
> On Wed, May 30, 2018 at 2:48 AM, Ian Kent wrote:
> > On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
> > > The autofs4 implementation is just a redirect to autofs now, but that
> > > also means we can't have both built into the
On Wed, 2018-05-30 at 10:41 +0200, Arnd Bergmann wrote:
> On Wed, May 30, 2018 at 2:48 AM, Ian Kent wrote:
> > On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
> > > The autofs4 implementation is just a redirect to autofs now, but that
> > > also means we can't have both built into the
On Wed, May 30, 2018 at 2:48 AM, Ian Kent wrote:
> On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
>> The autofs4 implementation is just a redirect to autofs now, but that
>> also means we can't have both built into the same kernel:
>>
>> fs/autofs/inode.o: In function `autofs_new_ino':
On Wed, May 30, 2018 at 2:48 AM, Ian Kent wrote:
> On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
>> The autofs4 implementation is just a redirect to autofs now, but that
>> also means we can't have both built into the same kernel:
>>
>> fs/autofs/inode.o: In function `autofs_new_ino':
On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
> The autofs4 implementation is just a redirect to autofs now, but that
> also means we can't have both built into the same kernel:
>
> fs/autofs/inode.o: In function `autofs_new_ino':
> inode.c:(.text+0x1b8): multiple definition of
On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
> The autofs4 implementation is just a redirect to autofs now, but that
> also means we can't have both built into the same kernel:
>
> fs/autofs/inode.o: In function `autofs_new_ino':
> inode.c:(.text+0x1b8): multiple definition of
The autofs4 implementation is just a redirect to autofs now, but that
also means we can't have both built into the same kernel:
fs/autofs/inode.o: In function `autofs_new_ino':
inode.c:(.text+0x1b8): multiple definition of `autofs_new_ino'
fs/autofs/inode.o:inode.c:(.text+0x1b8): first defined
The autofs4 implementation is just a redirect to autofs now, but that
also means we can't have both built into the same kernel:
fs/autofs/inode.o: In function `autofs_new_ino':
inode.c:(.text+0x1b8): multiple definition of `autofs_new_ino'
fs/autofs/inode.o:inode.c:(.text+0x1b8): first defined
16 matches
Mail list logo
