| To: | jamal <hadi@xxxxxxxxxx> |
|---|---|
| Subject: | Re: PATCH: rtnetlink explicit flags setting |
| From: | Thomas Graf <tgraf@xxxxxxx> |
| Date: | Fri, 27 May 2005 16:13:20 +0200 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <1117202331.6383.39.camel@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <1117197157.6688.24.camel@xxxxxxxxxxxxxxxxxxxxx> <20050527125010.GO15391@xxxxxxxxxxxxxx> <1117202331.6383.39.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
* jamal <1117202331.6383.39.camel@xxxxxxxxxxxxxxxxxxxxx> 2005-05-27 09:58 > On Fri, 2005-27-05 at 14:50 +0200, Thomas Graf wrote: > > > > > > -#define NLMSG_PUT(skb, pid, seq, type, len) \ > > +#define NLMSG_NEW(skb, pid, seq, type, len, flags) \ > > How about introducing NLMSG_NEW and leave NLMSG_PUT where it is? > This way we could do incremental updates. If there are not too many of > those NLMSG_PUT around, then it shouldnt be an issue. That is what the patch does but the diff looks a bit irritating. 1) Introduce NLMSG_NEW to take flags 2) Make NLMSG_PUT call NLMSG_NEW with flags==0 3) Change __nlmsg_put to take flags argument > The first change would be definetely on top of the current patch i sent > which is well deserved. > Lets have Dave swallow my patch then either you or i could make those > changes. Sounds reasonable? Sure. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] baycom_epp.c: Fix compilation with gcc-4.1.0-20050522, Alexey Dobriyan |
|---|---|
| Next by Date: | [PATCHSET] dsmark fixes & cleanups, Thomas Graf |
| Previous by Thread: | Re: PATCH: rtnetlink explicit flags setting, jamal |
| Next by Thread: | Re: PATCH: rtnetlink explicit flags setting, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |