From: David Howells
Date: Sat, 03 Oct 2020 22:24:55 +0100
> David Miller wrote:
>
>> > Since the fixes in the set need to go after the patches in net-next,
>> > should I
>> > resubmit just those for net-next, or sit on them till -rc1?
>>
>> My 'net' tree is always open for bug fixes, and
David Miller wrote:
> > Since the fixes in the set need to go after the patches in net-next, should
> > I
> > resubmit just those for net-next, or sit on them till -rc1?
>
> My 'net' tree is always open for bug fixes, and that's where bug fixes
> belong. Not 'net-next'.
"Need to go after the
From: David Howells
Date: Sat, 03 Oct 2020 21:01:49 +0100
> Since the fixes in the set need to go after the patches in net-next, should I
> resubmit just those for net-next, or sit on them till -rc1?
My 'net' tree is always open for bug fixes, and that's where bug fixes
belong. Not 'net-next'.
David Miller wrote:
> > The patches are tagged here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> > rxrpc-next-20201010
>
> No, they aren't.
oops. I transposed the last two digits. I really need to make my script
check the cover message.
> Also, you
From: David Howells
Date: Thu, 01 Oct 2020 15:56:43 +0100
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-next-20201010
No, they aren't.
git pull --no-ff
Here are some fixes for problems encountered whilst writing the RxGK
security class (this will allow AF_RXRPC to use GSSAPI-negotiated tokens
and better crypto). The RxGK security class is not included in this
patchset.
Firstly, there's a keyrings patch to provide the original key description,
6 matches
Mail list logo
