Displaying 5 results from an estimated 5 matches for "accpted".
Did you mean:
accepted
2023 Apr 03
1
[PATCH 0/1] posted interrtups support for mlx5
On 4/3/2023 12:20 PM, Eli Cohen wrote:
> Hi,
>
> the single patch in this series adds support for posted interrupts in
> mlx5.
>
> It depends on the patch series already accpted can be seen here:
> https://patchwork.kernel.org/project/netdevbpf/patch/20230324231341.29808-1-saeed at kernel.org/
>
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
> tags/mlx5-updates-2023-03-20
>
> Eli Cohen (1):
> vdpa/mlx5: Support interrupt...
2023 Apr 03
1
[PATCH 0/1] posted interrtups support for mlx5
On Mon, Apr 03, 2023 at 01:00:16PM -0400, Parav Pandit wrote:
>
>
> On 4/3/2023 12:20 PM, Eli Cohen wrote:
> > Hi,
> >
> > the single patch in this series adds support for posted interrupts in
> > mlx5.
> >
> > It depends on the patch series already accpted can be seen here:
> > https://patchwork.kernel.org/project/netdevbpf/patch/20230324231341.29808-1-saeed at kernel.org/
> >
> > git pull git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
> > tags/mlx5-updates-2023-03-20
> >
> > Eli Cohen (1):
> &...
2005 Oct 03
1
Direct Dial In - second try
Hi all,
I have an asterisk-server (cvs-head from august) connected to a
carrier's switch (DMS/Euroisdn) via a te410p, and I am having problems
with DDI (standard 'official pstn' number plus extra digits for
'internal' use)
Basically, when the entire number (including the extra digits) is
dialled via a redial or a programmed key, I see the entire called party
number (including
2007 Mar 28
1
auth server refusing connections intermittently
Running Dovecot 1.0-rc27 on Solaris 10..
We have been noticing intermittent messages of this sort and wondered if
this indicates whether we need to add more dovecot-auth worker processes:
Mar 28 03:15:41 myhost dovecot: pop3-login: Can't connect to auth server at default: Connection refused
Mar 28 08:10:20 myhost dovecot: imap-login: Can't connect to auth server at default: Connection
[Bug 2386] New: TERM env variable is always accepted by sshd, regardless the empty AcceptEnv setting
2015 Apr 17
12
[Bug 2386] New: TERM env variable is always accepted by sshd, regardless the empty AcceptEnv setting
https://bugzilla.mindrot.org/show_bug.cgi?id=2386
Bug ID: 2386
Summary: TERM env variable is always accepted by sshd,
regardless the empty AcceptEnv setting
Product: Portable OpenSSH
Version: 6.8p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5